BSOD on Windows 8 due to ntoskrnl.exe, DRIVER_POWER_STATE_FAILURE

Similar Questions

• Receive lots of BSOD due to ntoskrnl.exe, they stopped, but started again after a month

  I get lots of BSOD. I installed "WhoCrashed" and analyze the dump files. Here's what he said:

  Saturday, October 3, 14 17:29:30 GMT PM your computer crashed
  crash dump file: C:\Windows\Minidump\031014-15147-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B80)
  Bugcheck code: 0x4E (0 x 0x2007E, 0 x 2, 0 20075, 99)
  Error: PFN_LIST_CORRUPT
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that the page frame number (PFN) list is corrupted.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  I have this problem for a long time. I've updated the drivers, windows updates, no effect. But, for some reason, he did not seem since February. But Monday, I used MiniCygwin_GOptimize_v1.34.02 to compress files apk android. He uses a lot of CPU. And after that the BSOD began to reappear. I downloaded the Minidump file and Information System if someone wants to check.

  Let me know the reason for these BSOD and how can I solve this problem.

  Hello

  We have many bug different controls:

  PFN_LIST_CORRUPT (4th)

  This indicates that the page frame number (PFN) list is corrupted.

  This error is usually caused by a driver passing a list of descriptor of bad memory. For example, the pilot could call MmUnlockPages twice with the same list.

  MEMORY_MANAGEMENT (1A)

  This indicates that an error occurred serious memory management.

  Error checking 1A, {5003, fffff780c0000000, 6933, 64ba0002d266}

  -1 setting of the bug check is 5003 which lists free work is corrupt. It is probably a hardware error.

  We also have another 1st parameter:

  Error checking 1 a, {fffff6800005cf40, eab00001beb34867,403, fffff6fc00df59a0}

  - Parameter 1 of the bug check is 403 which indicates the page table and NFPs are out of sync. It is also probably a clerical error.

  ^^ Pointed out that both of the above can still be caused by a driver causing corruption, but it is generally unlikely.

  And another...

  Error checking 1A, {41284, 159a0e001, 104 d 57, fffff70001080000}

  -1 setting of the bug check is 41284 indicating a PTE or the fixed work list is corrupted.

  BAD_POOL_HEADER (19)

  This indicates that a pool header is corrupt.

  Error checking 19, {20, fffff8a00b91df40, fffff8a00b91e020, 50e040c}

  6: kd >! pool fffff8a00b91df40
  Pool page fffff8a00b91df40 region is unknown
  fffff8a00b91d000 size: 4 d 0 previous size: 0 Ntff (allocated)
  fffff8a00b91d4d0 size: 30 size: 4 d 0 PfFK (allocated)
  fffff8a00b91d500 size: 30 size: 30 PfFK (allocated)
  fffff8a00b91d530 size: 10 previous size: 30 (free) NtfE
  fffff8a00b91d540 size: 30 size: 10 Ntf0 (allocated)
  fffff8a00b91d570 size: size previous 10:30 (free) Nbmc
  fffff8a00b91d580 size: 40 previous size: 10 DxgK (allocated)
  fffff8a00b91d5c0 size: c0 size previous: AfdX (protected) process (allocated) 40: fffffa801098c7f0
  fffff8a00b91d680 size: 170 previous size: c0 MPsc (allocated)
  fffff8a00b91d7f0 size: size previous c0: 170 FIcs (allocated)
  fffff8a00b91d8b0 size: 40 size: c0 (allocated) NtFs
  fffff8a00b91d8f0 size: 30 size: 40 (allocated) PfFK
  fffff8a00b91d920 size: 30 size: 30 Ntf0 (allocated)
  fffff8a00b91d950 size: 150 size: 30 FMfn (allocated)
  fffff8a00b91daa0 size: size 160: 150 FMfn (allocated)
  fffff8a00b91dc00 size: 40 size: 160 (allocated) MmSm
  fffff8a00b91dc40 size: c0 size previous: 40 FIcs (allocated)
  fffff8a00b91dd00 size: 10 size: c0 sect (free)
  fffff8a00b91dd10 size: 170 previous size: 10 MPsc (allocated)
  fffff8a00b91de80 size: size previous c0: 170 (allocated) NtFs
  * fffff8a00b91df40 size: size previous e0: c0 (free) * FIcs
          PoolTag FIcs: Context of FileInfo FS-Filter binary stream: fileinfo.sys

  ^^ Block of pool who looked in the page pool belongs to the context of FileInfo FS-Filter flow. This is related to the file system.

  6: kd >! poolval fffff8a00b91df40
  Pool page fffff8a00b91df40 region is unknown

  Validation of the headers of pool the pool page: fffff8a00b91df40

  [Fffff8a00b91d000] page pool is __inVALID.

  System_service_exception (3B)

  This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  
  This error has been linked to the excessive use of expanded memory and resulting from user mode graphics drivers enjambment and passing data incorrect of the kernel code.

  2: kd > fffff960000a874f ln
  (fffff960'000 a 8720)   win32k! NextOwnedWindow + 0x2f |  (fffff960'000 a 8770) win32k! xxxRemoveDeleteMenuHelper

  ^^ The exception is produced in win32k! NextOwnedWindow.

  -----------------------

  Overall, this looks like the faulty RAM. It's not like there is a foul-smelling waters driver causing memory corruption here, but it is possible. The reason I mention this is because I see it in the crash dumps after dumping the! v

  OVERLAPPED_MODULE: Address overlap 'WinUsb' and 'ssudbus.sys'.

  ^^ WinUsb.sys - pilot class USB Windows system, it is a part of Windows. ssudbus.sys-

  SAMSUNG USB Composite Device Driver. Probably a part of Samsung Kies. Uninstall everything that you can find this topic.

  -----------------------

  Please run Memtest for NOT LESS than 8 ~ (several hours):

  Memtest86 +:

  Download Memtest86 + here:

  http://www.memtest.org/

  Which should I download?

  You can either download the ISO pre-built you want to burn to a CD and then boot from the CD, or you can download the automatic installer of the USB. What this will do is format your USB drive, make a boot device and then install the necessary files. Both do the same job, it's just you that you choose, or you have available (be it CD or USB).

  Note that some older generation motherboards do not support USB boot, your only option is CD (or floppy if you really wanted to).

  How Memtest works:

  Memtest86 writes a series of test patterns for most of the addresses of memory, reads the written data and compares it to find errors.

  The default pass is 9 different tests, varying in the modes of access and test data. A tenth test, bland, is selectable in the menu. He wrote all the memory with zeros, then sleeps 90 minutes before checking to see if the bits have changed (perhaps because of refresh problems). This is repeated with all those for a total time of 3 hours by pass.

  Many chipsets can report RAM speed and timings by SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclockee, Memtest86 can test that memory is free of error with these faster settings.

  Some hardware is able to report the status of the "PAT" (PAT: active or PAT: disabled). This is a reference to the Intel performance acceleration technology; There may be the BIOS settings that affect this aspect of memory synchronization.

  This information, if it is available for the program, can be displayed via a menu option.

  Other questions, they can most likely be answered by reading this excellent guide here:

  http://Forum.canardpc.com/threads/28864-FAQ-please-read-before-posting

  Kind regards

  Patrick

• XP reboot, trouble with windows system root 32/ntoskrnl.exe

  How do I reboot XP, when my keyboard seems to be does not work either. Replace the keyboard? Is a a working XP wireless work?

  Well, I looked up a1410a at hp, but they only had the a1410n model that I could see.  but the last letter in the model number may be due to only a minor difference between models.

  in any case, it is regrettable that hp.com makes it very difficult to find answers and you were essentially limited to the use of their system recovery / factory restore procedure.  However, this is not what need you.

  Instead, here is your bios access information:

  http://h10025.www1.HP.com/ewfrf/wc/document?DocName=bph07110&tmp_task=useCategory&LC=en&DLC=en&cc=us&lang=en&product=1841799

  again, once inside the bios menu, see if the keyboard helps you maneuver autour. try changing the date and time.   If you have some basic features of the kb, it is to say the arrow keys, number and letter work, then your kb is basically ok.

  to exit the bios, you can find options to close or end the session of the bios.  Choose the one that says, close and ignore the changes.  the bios will then close with all stats unchanged original.

  with respect to the model of your keyboard, it seems that you have a version of media multi with a ps2.

  the improvements offered by this keyboard requires a specialized hardware hp keyboard driver.  but this pilot and improvements are used by windows, when it runs.

  the pilot and the improvements are not needed during the boot process.

  either incidentally, adapter, to which I referred is a simple adapter that connects to the ps2 connector and converts it into a USB port.  It is relatively cheap and can be purchased at computer stores.

  http://www.bing.com/search?q=PS2%20To%20usb%20keyboard%20adapter&PQ=PS2%20To%20usb&SP=3&QS=as&SK=AS2&SC=8-10&form=BB07SS&PC=BB07

  However, instead of buying a plug adapter a specialty multi media keyboard, my suggestion is to buy a cheap keyboard plain / ordinary instead.

  a regular keyboard to replace your multi media Ko if it is defective.  the regular keyboard can also be used on other computers and laptops as a backup.

  Remember that ps2 keyboards and others comes with usb Sockets.   for now, you must Ko ps2 for use on your CV and if the box is delivered with a ps2 usb adapter, then, it is an added bonus.

• BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL with nvlddmkm.sys and ntoskrnl.exe

  Hey there,

  

  My computer has started planting since yesterday. I played a game for a while and it might or might not be related; Eitherway, it suddenly froze the system unexpectedly and I had to reset my pc. After that system started correctly. I ran the game again to see what's going on, and unfortunately, it crashed the system again; has had to reset hard once more. After that, I got a BSOD with DRIVER_IRQL_NOT_LESS_OR_EQUAL score to nvlddmkm.sys. I tried to reboot once more to see if it disappears and the system charged up to the floating logo of W7, but I only got a black screen afterwards, no login screen either. I wasn't able to boot the system normally more, forcing me to use safe mode. After checking terrils, I decided to uninstall completely nvidia drivers and that helped - loaded correctly and installed system software of windows default driver.

  Right now I'm in a situation where Windows seems to work stable unless I have try re-installing the drivers nvidia; In doing so, does not load results in a system and the BSOD screen again after W7 logo, no matter how many times I restart.

  My basic features are:

  Gigabyte P35-DS3R

  Intel Core 2 Quad Q6600 (2.40 ghz, oc'ed to stable 3.20 ghz)
  8 GB DDR2 RAM
  Gigabyte Geforce GTX460 1 GB of RAM

  Samsung 840 EVO 120 GB

  ST1000DM003-1SB10C 1 TB

  Silentium VERO L1 600W

  W7 Pro SP1 with all latest updates

  Here are the dumps (contains the dump of the first and the last being).

  So far what I've done - tried unplugging all devices (including my Sound Blaster Tactic 3D Sigma headset), uninstalled Avast antivirus, tried reinstalling drivers nvidia in two different ways (of unsuccessfully); clean the GPU/CPU/power supply. I'm slowly running out of ideas. To add, I never really had problems with my PC - it works all the time for 8-9 years with no issues whatsoever and I moved from c2d e6750 and GTS250 a year (or more) there are what I currently; never had any problems with these components, either. I always intend to Exchange my gpu for further testing, but since I do not have an integrated GPU and video signal passes through GTX460, I don't really know if there is a damaged graphics card (perhaps wrong, however).

  If anyone knows what is the origin of the problem and what can be done to avoid a full system reinstall, I would be really grateful for any help.

  Update:

  I swapped the GTX460 with my old GTS250 for test. Apparently, it seems that the GTX460 was damaged and all misleading BSOD was actually caused by defective behavior. Fix to 750ti in a while.

  Edit [21/05/2016]:

  I swapped to 750ti and all is well again. This case can be considered resolved.

• Blue screen on stop ntoskrnl.exe DRIVER_POWER_STATE_FAILURE

  My computer blue screened twice now having been to "Shutting down" screen for a few minutes.

  I downloaded the 2 .dmp files that I found using BlueScreenView onedrive here:

  http://1drv.Ms/1ElvK85

  Can someone tell me what is the cause, or how I might solve this problem?

  These accidents were related to the corruption of memory (probably caused by a driver).

  Run these two tests to check your memory and find which driver is causing the problem.  Launch auditor.  You need not run memtest again unless you want to.
  

  If you are overclocking anything reset by default before running these tests.
  In other words STOP! If you don't know what it means that you're probably not  
  
  
  
  
  1-Driver Verifier (for full instructions, see our wiki here)
  
  2-Memtest. (You can learn more about running memtest here)

  
  

• Windows 8 BSOD caused by ntoskrnl.exe

  Hello.

  I get a lot of the dreaded BSOD lately.
  From the beginning I thought that it's nvidia drivers. Update of those fixed everything except a BSOD I get.
  Now I get the same BSOD, and it is caused by ntoskrnl.exe and playback memory problems.
  I've been all around you are looking for assistance and use of memtest86 without result.
  The Msinfo32 and .dmp files are located here: DMP.zip 
  Anyone have any idea what may be causing this?
  I couldn't find the RAM that I use in the compatibility table for the motherboard. So that's what I think may cause the problem.
  Any help is greatly appreciated.
  Kind regards
  Arve

  Hi Arve,

  All attached files of the DMP are the bug check IRQL_NOT_LESS_OR_EQUAL (a) .

  This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.

  This bug check is issued if the memory paged (or invalid) is accessible when the IRQL is too high. The error that usually generates this bug check occurs after the installation of the faulty device driver or service system, BIOS.

  If we look at the call stack:
  
  STACK_TEXT:
  "fffff880 '0335caf0 fffff880' 06a4d817: fffff880 00000000' fffffa80 ' 00000008 fffffa80 ' 12fdbe10 00000005' 00001f80: nt! KeSetEvent + 0x2ad
  fffff880 '0335cb60 00000000 fffff880': fffffa80'00000008 fffffa80 '12fdbe10 00000005' 00001f80 fffffa80' 1458a6a0: MBfilt64+ 0 x 1817
  fffff880'0335cb68 fffffa80'00000008: fffffa80 '12fdbe10 00000005' 00001f80 fffffa80 '1458a6a0 fffff800' 9bc62d4c: 00000000' 0xfffff880
  fffff880 '0335cb70 fffffa80' 12fdbe10: 00000005' 00001f80 fffffa80'1458a6a0 fffff800 '9bc62d4c fffffa80' 1458a6a0: 0xfffffa80'00000008
  fffff880 '0335cb78 00000005' 00001f80: fffffa80 ' 1458a6a0 fffff800 '9bc62d4c fffffa80' 1458a6a0 fffffa80 ' 1458a6a0: 0xfffffa80'12fdbe10
  fffff880 '0335cb80 fffffa80' 1458a6a0: fffff800 ' 9bc62d4c fffffa80 '1458a6a0 fffffa80' 1458a6a0 fffffa80 ' 12fdbe10: 0 x 5 ' 00001f80
  fffff880 '0335cb88 fffff800' 9bc62d4c: fffffa80 ' 1458a6a0 fffffa80 '1458a6a0 fffffa80' 12fdbe10 fffff880 ' 02fc9f00: 0xfffffa80'1458a6a0
  fffff880 '0335cb90 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! ViPendingCompleteAfterWait + 0xc4

  Cannot load the image MBfilt64.sys, 0n2 error Win32
  WARNING: Unable to verify timestamp for MBfilt64.sys
  ERROR: Module load completed but symbols can be loaded for MBfilt64.sys
  Probably caused by: MBfilt64.sys (MBfilt64 + 1817)

  ^^
  Driver Realtek HiDefinition Audio (referred to as Creative Audio Driver file).

  If we run a lmvm on your:

  4: kd > lmvm MBfilt64
  start end module name
  fffff880 '06a4c000 fffff880' 06a5a000 MBfilt64 T (no symbol)
  Loaded symbol image file: MBfilt64.sys
  Image path: MBfilt64.sys
  Image name: MBfilt64.sys
  Timestamp: Thu Aug 30 23:40:32 2009 (4A7267B0)

  ^^, Yours is dated 2009 ~ The most recent is AFAIK as early as September 2013, via - Realtek site

  http://www.Realtek.com.tw/downloads/downloadsCheck.aspx?langid=1&PNid=24&PFID=24&level=4&Conn=3&DownTypeID=3&GETDOWN=false

  To update this driver as soon as POSSIBLE.

  -----------------------------------------------------------

  In addition, to provide peace of mind regarding your request of RAM. If you receive a card mother and they have a list of the RAM compatible in the manual, etc., this is called a QVL (qualified suppliers list). It is simply a list of RAM which has been tested internally and is PROVING to be quite compatible 100%. If the RAM is not on the list, it is not by all means, implies that the RAM will be inconsistent and cause problems. Actually today is very rare. Your RAM doesn't seem to be the issue at all in these accidents.

  Kind regards

  Patrick

• Qosmio F20-153 - ntoskrnl.exe file missing

  Hello

  I have an almost 5 year old toshiba Qosmio F20-153, which has developed an error with the Windows message root>\system32\ntoskrnl.exe file is missing.
  I wonder if it's fixable without completely re - install the complete operating system that I still have the Toshiba restore disk.

  Any help much appreciated.

  Hey Buddy,

  In my view, your only option is recovering the entire notebook. The Toshiba Recovery disk only contains an image of factory settings, which means that you can t install this single file of this disc.
  In addition it s a good idea to reinstall Windows from time to time. If your installation is already 5 years old, you should do this. You will be surprised with the speed of your laptop is after that. :)

  Use the recovery disk is quite simple: you must boot from that disk and follow the instructions on the screen. You do a few clicks only and that s it!

• Trojan.Dropper on ntoskrnl.exe - help please

  I did a scan with Norton and no problem has arisen, however I did a scan with Spyhunter3 and he found a Trojan.Dropper virus in the ntoskrnl.exe. How can I fix it?

  The path of the file he has identified is C:\WINDOWS\$hf_mig$\KB890859/SP2QFE/ntoskrnl.exe

  Things, I read, I can't just delete the file - the computer needs this exe file...?

  Not sure how it can be cleaned?

  Suggestions for a beginner would be appreciated.

  Thank you

  Hello

  I suspect a false positive.

  You can download it again and too install KB890859 here:

  http://www.Microsoft.com/downloads/details.aspx?FamilyId=F0683E2B-8E8F-474F-B8D8-46C4C33FCE99&displaylang=en

  Also add Prevx to your safety and your scan with Malwarebytes.

  Prevx - home - free small, fast and exceptional protection CLOUD, working with other security programs. It comes
  a scan only, VERY EFFICIENT, if it finds something to come back here or use Google to see how to remove.
  http://www.prevx.com/

  PCmag - Prevx - Editor's choice
  http://www.PCMag.com/Article2/0, 2817,2346862,00.asp

  Also get Malwarebytes - free - use as scanner only. If you ever suspect malware, and that would be unusual with
  Avast and Prevx running except a low occasional (not much), updated cookie and then run it as
  a scanner. I have a lot of scanners and they never find anything of note that I started to use this configuration.

  http://www.Malwarebytes.org/

  Rob - bicycle - Mark Twain said it is good.

• Windows 7 BSOD - ntoskrnl.exe (nt + 0x7F1C0)

  I have this problem since April, 2012

  HP support suggested that I should reinstall windows 7. I did some time at the beginning of August, but the problem persists.
  Help, please! Otherwise, I'll keep change the OS with a Microsoft OS No.
  Here are the dumps:
  (Local) information system
  computer name: RADU-PC
  Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  Windows dir: C:\Windows
  CPU: GenuineIntel Intel (r) Core i5 CPU M 520 @ 2.40 GHz Intel586, level: 6
  4 logical processors, active mask: 15
  RAM: 4145868800 total
  VM: 2147352576, free: 1943330816

  Crash Dump Analysis
  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Sat 29-Sep-12 12:56:36 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092912-34632-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003344E30, 0xFFFFF8800AEE8C70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Sat 29-Sep-12 12:56:36 GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: bcm42rly.sys (BCM42RLY + 0 x 1280)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003344E30, 0xFFFFF8800AEE8C70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\drivers\bcm42rly.sys
  product: Broadcom iLine10 (TM) PCI network card
  company: Broadcom Corporation
  Description: Broadcom iLine10 (TM) PCI network adapter Proxy Protocol Driver
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: bcm42rly.sys (Broadcom iLine10 (TM) PCI network adapter Proxy Protocol Driver, Broadcom Corporation).
  Google search: bcm42rly.sys Broadcom Corporation SYSTEM_SERVICE_EXCEPTION

  Sat 29-Sep-12 12:47:59 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092912-34772-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003347E30, 0xFFFFF8800BCDCC70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &

  
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Sat 29-Sep-12 12:39:07 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092912-35552-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000333CE30, 0xFFFFF88008D9CC70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Fri 28-Sept-12 07:30:24 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092812-35630-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003389E30, 0xFFFFF8800C0C5C70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Fri 28-Sept-12 07:20:56 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092812-58531-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003349E30, 0xFFFFF8800ACA9C70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Play 27 Sept - 12 22:01:30 GMT your computer crashed
  crash dump file: C:\Windows\Minidump\092712-21606-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x1A (0xFFFFFA8000532F50, 41790, 0 x 0 x 0, 0xFFFF)
  Error: MEMORY_MANAGEMENT
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an error occurred serious memory management.
  This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Play 27 Sept - 12 09:26:28 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092712-30108-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x19 (0 x 22, 0 x 20000000000000, 0x0, 0x0)
  Error: BAD_POOL_HEADER
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a pool header is corrupt.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  The sea 26-Sept-12 07:12:30 GMT your computer crashed
  crash dump file: C:\Windows\Minidump\092612-19734-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x5A88)
  Verification of error code: 0 x 24 (0xFFFFF8800996BAE8, 0xFFFFF8800996B340, 0x1904FB, 0xFFFFF88001231A74)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Mar 25 - Sep - 12 20:55:48 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092612-22354-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x7A (0xFFFFFFFFC0000005, 0xFFFFFA8004646060, 0x1, 0xFFFFF680000B1000)
  Error: KERNEL_DATA_INPAGE_ERROR
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: this bug check indicates that the data page of the kernel of the required paging file cannot be read into memory.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  The game 20-Sept-12 15:08:27 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092012-53929-01.dmp
  This was probably caused by the following module: win32k.sys (win32k + 0xC6A12)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000116A12, 0xFFFFF8800AC5B130, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\win32k.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: Multi-User Win32 Driver
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Wednesday, August 7, 12 10:29:53 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\080712-41917-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x71F00)
  Verification of error code: 0 x 50 (0x0, 0xFFFFF8000311445B, 0xFFFFF8A00B2DF000, 0 x 2)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that invalid system memory was referenced.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, August 7, 12 10:08:21 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\080712-53305-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x1A50F3)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002DBB0F3, 0xFFFFF880031A18B8, 0xFFFFF880031A1110)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  We need the DMP file because it contains the single record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.

  If you are overclocking STOP

  You may be able to get the DMP files without crashing by booting in SafeMode (F8) with networking.

  Please follow these instructions to collect data against crashes and upload them here, to your Skydrive or a service such as Rapidshare file sharing.

  http://www.SysNative.com/forums/showthread.php/68-blue-screen-of-death-%28BSOD%29-posting-instructions-Windows-8-7-amp-Vista?p=303&viewfull=1#post303

  http://SysNative.com/0x8/BSOD_Windows7_Vista_v2.64_jcgriff2_.exe

  To allow us to help you with symptoms BSOD on your computer, download the contents of your folder "\Windows\Minidump".

  The procedure:

  * Copy the contents of \Windows\Minidump to another location (temporary) somewhere on your machine.
  * Zip up the contents of this folder
  Please, upload to skydrive or a file sharing service and put a link to them in your next post.

  Go to start > search/run > cmd > msinfo32 and include it in the upload

  To ensure the minidumps are enabled:

  * Click Start, in the search box, type: sysdm.cpl, press ENTER.
  * On the Advanced tab, click Startup and recovery... Settings button.
  * Make sure that automatically restart is unchecked.
  * Under the writing debugging information header, select image partial memory (256 KB) in the list box drop-down (varies from 256kb).
  * Ensure to that small Dump Directory is listed as % systemroot%\Minidump.
  * OK your way out.
  * Reboot if changes have been made.

  http://www.SysNative.com/forums/showthread.php/325-BSODs-but-no-dump-files

  http://www.osronline.com/article.cfm?article=545

  Please also go to start > run > msinfo32 and record the results.  Send it with the DMP files, thank you.

• Windows BSOD KERNEL_DATA_INPAGE_ERROR 8; Ntoskrnl.exe + 7 has 040

  Hello world

  I had reinstall Windows 8 last month cause too many errors with the Windows 8 and I had still BOSD arrives with a new installation of Windows 8.

  The last that I have no will is this one:

  KERNEL_DATA_INPAGE_ERROR

  Ntoskrnl.exe + 7 has 040

  We arrive in surfing on the web and burning with IMGBURN. Many Disconnections occur when you use the dvd burner.

  The other at the moment that I solved is "atikmpag.sys" I read on the net that I need to update the file from a download of catalyst frensh.

  Here all DUMP files and the news of the computer:

  All files: https://skydrive.live.com/redir?resid=10F449F32E80D9B2! 390

  Thank you!

  8ternity

  They were related to the following

  KERNEL_DATA_INPAGE_ERROR (7A)
  The requested page of kernel data could not be read in.  Is usually caused by
  a bad block in the disk controller or paging file error.

  My gut feeling is that it is one of these drivers or your moy.  I would like to update the drivers and replace AVG with the built-in Defender

  000 fcl 26/09/2008 09:11:22
  ksaud.sys 2010-07-14 06:12:54
  ntk_PowerDVD_64.sys 03/08/2010 05:04:12
  PxHlpa64.sys 2011-10-17 10:29:34
  amdsbs.sys 21/02/2012 14:15:43

  AVG can be a cause of BSOD.

  http://www.Avg.com/us-en/utilities

  How to find drivers:
  -Google search for the name of the driver
  -compare Google results with what is installed on your system to determine on what device/program, it belongs to
  -Visit the web site of the manufacturer of the hardware or program to get the latest drivers (do not use Windows Update or Device Manager Update Driver function).
  s ' there is difficult to locate them, post back with questions, and someone will try and help you find the right program

  The most common drivers are listed on this page: driver reference

  http://www.carrona.org/dvrref.php

  http://SysNative.com/drivers/

  -Driver manufacturer links are on this page: http://www.carrona.org

• BSOD Windows 7 64 bit IRQL_NOT_LESS_OR_EQUAL 0x0000000A in ntoskrnl.exe + 74469

  I just got it, I had to launch a Malwaresbytes update and PrivaZer was launched and at the same time. This is the first time I see that the origin of the problem, generally, it is my software Bitdefender that do.

  General information

  Bug check code	0x0000000A
  Bug control chain	IRQL_NOT_LESS_OR_EQUAL

  1 listen	0xFFFFF88000961008
  2 listen	0 x 0000000000000002
  3 listen	0 x 0000000000000001

  4 listen	0xFFFFF80003674AE9
  Date of the crash	19/03/2015-05:37
  Architecture	x 64

  Major version	15
  Minor version	7601

  Number of processors	4
  Size dump file of the	256 KB

  Crash of the source

  Crash of the source	Hidclass.sys + 20006370F20
  Path	C:\Windows\system32\drivers\hidclass.sys

  Description	HID class library
  Version	6.1.7601.18199
  Company	Microsoft Corporation
  Size	75 KB

  Call stack

  Address of the stack	Ntoskrnl.exe + 74469
  Address of the stack	Ntoskrnl.exe + 23AE9
  Address of the stack	Hidclass.sys + 20006370F20
  Address of the stack	Ntoskrnl.exe + 377420

  Sorry it's in French but the locations are the same as in English.

  Hello

  References to Vista also apply to Windows 7.

  This is my generic how updates of appropriate driver:

  This utility, it is easy see which versions are loaded: run DriverView - set the VIEW to hide
  Microsoft drivers - update those without drain in their names. (Also update the BIOS and the weak)
  level chipset drivers on the site of the constructor/the system motherboard.)

  -Free - DriverView utility displays the list of all device drivers currently loaded on your system.
  For each driver in the list, additional useful information is displayed: load address of the driver,
  Description, version, product name, company that created the driver and more.
  http://www.NirSoft.NET/utils/DriverView.html

  For drivers, visit manufacturer of emergency system and of the manufacturer of the device that are the most common.
  Control Panel - device - Graphics Manager - note the brand and complete model
  your video card - double - tab of the driver - write version information. Now, click on update
  Driver (this can do nothing as MS is far behind the certification of drivers) - then right-click.
  Uninstall - REBOOT it will refresh the driver stack.

  Repeat this for network - card (NIC), Wifi network, sound, mouse, and keyboard if 3rd party
  with their own software and drivers and all other main drivers that you have.

  Now in the system manufacturer (Dell, HP, Toshiba as examples) site (in a restaurant), peripheral
  Site of the manufacturer (Realtek, Intel, Nvidia, ATI, for example) and get their latest versions. (Look for
  BIOS, Chipset and software updates on the site of the manufacturer of the system here.)

  Download - SAVE - go to where you put them - right click - RUN AD ADMIN - REBOOT after
  each installation.

  Always check in the Device Manager - drivers tab to be sure the version you actually install
  presents itself. This is because some restore drivers before the most recent is installed (sound card drivers
  in particular that) so to install a driver - reboot - check that it is installed and repeat as
  necessary.

  Repeat to the manufacturers - BTW in the DO NOT RUN THEIR SCANNER device - check
  manually by model.

  Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
  http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

  Installation and update of drivers to 7 (updated drivers manually using the methods above is)
  to ensure that the latest drivers from the manufacturer of system and device manufacturers are are preferably)
  http://www.SevenForums.com/tutorials/43216-installing-updating-drivers-7-a.html

  If you update the drivers manually, then it's a good idea to disable the facilities of driver under Windows
  Updates, this leaves ONE of Windows updates, but it will not install the drivers who will be generally
  be older and cause problems. If updates offers a new driver and then HIDE it (right click on it)
  and then go look for new ones manually if you wish.

  How to stop Windows 7 automatically install drivers
  http://support.Microsoft.com/kb/2500967

  ==========================================

  Tests of memory intercept all errors such as memory do not match (possible even for sticks
  seemingly identical) and when the faster memory is placed in system behind the slower memory.
  So it is best to Exchange also sticks in and out to check for those, even if all the tests of memory do not
  show a problem.

  To test the RAM here control - run 4 + hours or so.<-- best="">
  www.memtest.org

  For the Windows Memory Diagnostic tool.

  Start - type in the search-> memory box - find top - click - right Memory Diagnostics tool
  RUN AS ADMIN follow the instructions

  Windows Vista: How to scan / test your memory with Windows Vista memory or RAM
  Diagnostic tool
  http://www.shivaranjan.com/2007/11/01/Windows-Vista-how-to-scan-test-your-RAM-or-memory-with-Windows-Vista-memory-diagnostic-tool/

  How to run the diagnostic tool memory in Windows 7
  http://www.SevenForums.com/tutorials/715-memory-diagnostics-tool.html

  I hope this helps.

  Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

• Windows 8 unexpected Kernel Mode trap BSOD (ntoskrnl.exe)

  Hello, I got the blue screen that gives me the error code: UNEXPECTED_KERNEL_MODE_TRAP (ntoskrnl.exe). I have had this problem since I got my computer, but it happens that all the other day. I tested my RAM with memtest and everything was good. I also use on all drivers updated. I recently installed "WhoCrashed" hoping to get more information as to what was causing this error. Here's the report;

  Thursday, June 26, 2014 6:31:37 PM GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\062614-28703-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x153FA0)
  Bugcheck code: 0x7F (0 x 8, 0xFFFFF802935ABE70, 0xFFFFF80293592FF0, 0xFFFFF80291C5AB6E)
  Error: UNEXPECTED_KERNEL_MODE_TRAP
  file path: C:\WINDOWS\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: this bug check indicates that the Intel CPU generated a trap and the kernel could not catch this trap.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Any help will be much appreciated.

  Thank you

  Ryan

  Ryan

  The DMP was inconclusive pointing to memory.  My gut says it's Symantec.  I would like to do two things.  Run the driver verifier and remove Symantec and use the built in Defender.

  These accidents were related to the corruption of memory (probably caused by a driver).

  Please run these tests to check your memory and find which driver is causing the problem.

  
  

  If you're overclocking (pushing components beyond their design) return you to default at least until the crash is resolved. If you don't know what it is that you're probably not overclocking.

  
  

  Since then, it is more likely to be a pilot run everything first.

  1-Driver Verifier (for full instructions, see our wiki here)

  
  

  If the auditor does not have the issue we move to it.

  2-Memtest. (You can learn more about running memtest here)

  
  

  If you cannot start after you have enabled the auditor reboot in safe mode

  In Vista & victory (F8)

  When win 8 http://www.howtogeek.com/107511/how-to-boot-into-safe-mode-on-Windows-8-the-easy-way/

  
  

  Co-written by JMH3143

  .

• BSOD help (ntoskrnl.exe)

  I recently built a new computer for the first time and I am constantly a BSOD.  After consulting the minidump via the blue screen view files, it refers to the ntoskrnl.exe as the cause, but I suspect that maybe it's a corrupt driver (I could be wrong but).  Due to my lack of experience on this subject, however, I have no idea on how to identify the guilty and so need help.  As a result, I posted a link below containing the minidump files created by my computer and wish for some assistance on the interruption of information (any help would be greatly appreciated).

  http://www.mediafire.com/download/khtsg34cxn75t41/minidump.zip

  Thank you
  WildThing0079

  Great, thank you very much.

  We have various bug different controls:

  PFN_LIST_CORRUPT (4th)

  This indicates that the page frame number (PFN) list is corrupted.

  This error is usually caused by a driver passing a list of descriptor of bad memory. For example, the pilot could call MmUnlockPages twice with the same list. However, this bug control seems as frequently when there is a defective material, most often RAM or HARD disk.

  MEMORY_MANAGEMENT (1A)

  This indicates that an error occurred serious memory management.

  Error checking 1 a, {41287, 0, 0, 0}

  -1 setting of the bug check is 41287 indicating an illegal page fault occurred while now fixed synchronization of work.

  * Addition 41287, we have also the 1st parameter is 403 which indicates the table of page and NFPs are out of sync. It is probably a hardware error, although the device driver causing corruption is possible as well.

  PAGE_FAULT_IN_NONPAGED_AREA (50)

  This indicates that invalid system memory was referenced.

  Bug control 0 x 50 usually occurs after the installation of a faulty hardware or installation failure of material (usually associated with defective RAM, either main memory, L2 RAM or RAM video cache).

  Another common cause is a defective system service installation.

  Antivirus software can also cause this error, as a corrupted NTFS volume can do him.

  System_service_exception (3B)

  This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  
  This error has been linked to the excessive use of expanded memory and resulting from user mode graphics drivers enjambment and passing data incorrect of the kernel code.

  -----------------------

  1. AppleCharger.sys is listed and loaded, this is the driver GIGABYTE on / off Charge. See here for more information - http://www.gigabyte.us/MicroSite/185/on-off-charge.htm

  He is well known to cause BSOD, so please delete it as soon as POSSIBLE.

  2 even with gdrv.sys, which is the easy profit from Gigabyte - mobo utility power driver. Remove as soon as possible.

  3 remove and reinstall Kaspersky with temporary Microsoft Security Essentials for troubleshooting purposes:

  Kaspersky - remove http://support.Kaspersky.com/common/service.aspx?El=1464

  MSE - http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download 

  Kind regards

  Patrick

• BSOD - Server 2008 R2 - ntoskrnl.exe

  I had a problem recently with a BSOD that passes several times during the day. I newspapers DMP and used BlueScreenView to obtain some basic information (I know that it is also useful that it doesn't help) which seems to show that ntoskrnl.exe is at the origin of accidents. There are 6 Server, 1 is used by the LATTER and does not seem to have had this problem while the other 5 are part of a balanced load environment and have been seen this problem in some cases, 5 times a day. Here are the servers from RD.

  The servers were all working perfectly well until our company has purchased and installed a piece of software called screwdriver. This software seems to be the cause of accidents and I contacted their support in this regard. But while I'm waiting I think it is perhaps a good idea to ask if the DMP files might actually provide more information as to what specifically is causing accidents.

  For those who don't know, the screwdriver is a utility to help you with printing (printing from the Desktop server remotely to the workstation using the screwdriver driverless driver) and I wonder if there is a specific model of printer causing accidents or a driver side specific workstation or if its just one or a few users who cause accidents. Obviously BlueScreenView is not giving any information good but if the DMP file contains more information that might help I understand that it is worth looking into.

  The BSOD error is below:

  Signature of the problem:

  Problem event name: BlueScreen

  OS version: 6.1.7601.2.1.0.18.10

  Locale ID: 1033

  More information about the problem:

  BCCode: f4

  BCP1: 0000000000000003

  BCP2: FFFFFA801CCD9060

  BCP3: FFFFFA801CCD9340

  BCP4: FFFFF80001D85270

  OS version: 6_1_7601

  Service Pack: 1_0

  Product: 18_3

  Files helping to describe the problem:

  C:\Windows\Minidump\112414-48500-01.dmp

  C:\Users\***\AppData\Local\Temp\17\WER-2765148-0.SysData.XML

  Read our privacy statement online:

  http://go.Microsoft.com/fwlink/?LinkId=104288&clcid=0x0409

  If the online privacy statement is not available, please read our offline privacy statement:

  C:\Windows\system32\en-US\erofflps.txt

  Any help is appreciated.

  Thank you

  Ryan

  Ryan

  You should also put this on Technet and I will increase it there as well.

  http://social.technet.Microsoft.com/forums/en-us/home

  http://social.msdn.Microsoft.com/forums/en-us/home

• Random BSOD and I do not know why.__Unable to load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32

  I don't know why this is happening, but I'm getting random BSOD now and then. I tried to point out my system to see if it generates a BSOD, but multitasking 3d and photoshop programs and what's not stress, then when I least expect, BANG! BSOD.
  The last of them, that I had now was in the middle of the night with almost no programs running. The system had worked for some time (one or two days), but nothing was he pointing out at the same time.

  What I think happened was: our microwave shorted out and caused a fuse to blow. But it was on another grid in our House (I hope I make myself clear, because I'm not used to talk about stuff like this in English!) so it should not affect my computer. But at the same time my microwave said "Thank you for everything!" my computer would BSOD. The thing is that my modem, my switch, my router and my NAS is connected to the electric network and my short circuted of switch. And my computer is connected to the switch cable.
  This effect possible that excess tension (or something) has short circuted my switch and 'jumped' power to the switch and on the cable and sending there is a shock to my computer? Or am I just paranoid? Laughing out loud

  I know that the controllers are pushed to the limit of the memory and therefor tolerate very little when it comes to electricity. I ran MemTest4.00 14 passes but I came with nothing. But memtest that tests memory, not the controllers, right? I am watching a fried motherboard?

  I did a windb, but I don't understand what he says. Could someone please translate this for me and give me your opinion?
  In addition, when you run windb, it's tell me am I wrong symbols. -What this means, and where can I get the symbols he wants? And what symbols?

  Microsoft (R) Windows debug 6.12.0002.633 AMD64 Version
  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading dump file [C:\Windows\Minidump\Mini042910-01.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol search path is: * invalid *.
  ****************************************************************************
  * Loading of the symbol may be unreliable without a symbol search path.           *
  * Use .symfix to get the debugger to choose a symbol path.                   *
  * After adjusting your path to symbols, use .reload to refresh the locations of symbols. *
  ****************************************************************************
  Executable search path is:
  *********************************************************************
  * Symbols cannot be loaded because the path is not initialized. *
  *                                                                   *
  * The symbol path can be defined: *.
  * using the _NT_SYMBOL_PATH environment variable.                 *
  * with the help of the there when you start the debugger argument. *.
  * using the .sympath and .sympath + *.
  *********************************************************************
  Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
  WARNING: Unable to verify timestamp for ntoskrnl.exe
  ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
  Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack2) MP (4 procs) free x 64
  Product: WinNt, suite: TerminalServer SingleUserTS
  Computer name:
  Kernel base = 0xfffff800 '02c4c000 PsLoadedModuleList = 0xfffff800' 02e10dd0
  The debugging session: 23:43:16.368 Thursday, April 29, 2010 (UTC + 02:00)
  System Uptime: 3 days 5:21:50.657
  *********************************************************************
  * Symbols cannot be loaded because the path is not initialized. *
  *                                                                   *
  * The symbol path can be defined: *.
  * using the _NT_SYMBOL_PATH environment variable.                 *
  * with the help of the there when you start the debugger argument. *.
  * using the .sympath and .sympath + *.
  *********************************************************************
  Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
  WARNING: Unable to verify timestamp for ntoskrnl.exe
  ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
  Loading the kernel symbols
  ...............................................................
  ................................................................
  ................................................
  Loading user symbols
  Loading unloaded module list
  ......
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  Bugcheck A, {fffffa7fffffffea, 2, 0, fffff80002c5a95c}

  The kernel symbols are FALSE. Correct symbols to do the analysis.

  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, your symbol path *.
  should point to .pdb files have the type information complete.      ***
  ***                                                                   ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information.  The contact group that *.
  you provided with these symbols, if you need this command for *.
  work.                                                          ***
  ***                                                                   ***
  Type referenced: nt! _KPRCB *.
  ***                                                                   ***
  *************************************************************************
  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, your symbol path *.
  should point to .pdb files have the type information complete.      ***
  ***                                                                   ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information.  The contact group that *.
  you provided with these symbols, if you need this command for *.
  work.                                                          ***
  ***                                                                   ***
  Type referenced: nt! _KPRCB *.
  ***                                                                   ***
  *************************************************************************
  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, your symbol path *.
  should point to .pdb files have the type information complete.      ***
  ***                                                                   ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information.  The contact group that *.
  you provided with these symbols, if you need this command for *.
  work.                                                          ***
  ***                                                                   ***
  Type referenced: nt! _KPRCB *.
  ***                                                                   ***
  *************************************************************************
  Probably caused by: ntoskrnl.exe (nt + e95c)

  Follow-up: MachineOwner
  ---------

  0: kd >! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  IRQL_NOT_LESS_OR_EQUAL (a)
  An attempt was made to access an address pageable (or completely invalid) to a
  application interrupt level (IRQL) that is too high.  It is usually
  caused by drivers using a wrong address.
  If a kernel debugger is available, download the stack trace.
  Arguments:
  Arg1: fffffa7fffffffea, memory referenced
  Arg2: 0000000000000002, IRQL
  Arg3: 0000000000000000, bit field:
  bit 0: value 0 = read operation, 1 = write operation
  bit 3: value 0 = not an enforcement operation, 1 = performance operation (only on chips that support this level of State)
  Arg4: fffff80002c5a95c, address memory

  Debugging information:
  ------------------

  The kernel symbols are FALSE. Correct symbols to do the analysis.

  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, your symbol path *.
  should point to .pdb files have the type information complete.      ***
  ***                                                                   ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information.  The contact group that *.
  you provided with these symbols, if you need this command for *.
  work.                                                          ***
  ***                                                                   ***
  Type referenced: nt! _KPRCB *.
  ***                                                                   ***
  *************************************************************************
  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, your symbol path *.
  should point to .pdb files have the type information complete.      ***
  ***                                                                   ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information.  The contact group that *.
  you provided with these symbols, if you need this command for *.
  work.                                                          ***
  ***                                                                   ***
  Type referenced: nt! _KPRCB *.
  ***                                                                   ***
  *************************************************************************
  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, your symbol path *.
  should point to .pdb files have the type information complete.      ***
  ***                                                                   ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information.  The contact group that *.
  you provided with these symbols, if you need this command for *.
  work.                                                          ***
  ***                                                                   ***
  Type referenced: nt! _KPRCB *.
  ***                                                                   ***
  *************************************************************************

  ADDITIONAL_DEBUG_TEXT:
  Use '! findthebuild' command to search for the generation of target information.
  If the build information is available, run '! findthebuild s; .reload ' to set the symbol path and of loading symbols.

  MODULE_NAME: nt

  FAULTING_MODULE: fffff80002c4c000 nt

  DEBUG_FLR_IMAGE_TIMESTAMP: 4b7d238f

  READ_ADDRESS: could not get nt! MmSpecialPoolStart
  Unable to get nt! MmSpecialPoolEnd
  Unable to get nt! MmPoolCodeStart
  Unable to get nt! MmPoolCodeEnd
  fffffa7fffffffea

  CURRENT_IRQL: 0

  FAULTING_IP:
  NT + e95c
  fffff800'02c5a95c?              ???

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

  BUGCHECK_STR: 0XA

  LAST_CONTROL_TRANSFER: from fffff80002ca626e to fffff80002ca64d0

  STACK_TEXT:
  fffffa60 '01bde688 fffff800' 02ca626e: 00000000' 0000000 a fffffa7f ' ffffffea 00000000'00000002 00000000'00000000: nt + 0x5a4d0
  fffffa60 '01bde690 00000000' 0000000-a: fffffa7f 'ffffffea 00000000'00000002 00000000'00000000 fffff800' 02c5a95c: nt + 0x5a26e
  fffffa60 '01bde698 fffffa7f' ffffffea: 00000000'00000002 00000000'00000000 fffff800 '02c5a95c fffffa60' 04dbf8b0: 0xa
  fffffa60 '01bde6a0 00000000' 00000002: 00000000 00000000' fffff800 '02c5a95c fffffa60' 04dbf8b0 00000000' 00000000: 0xfffffa7f'ffffffea
  fffffa60'01bde6a8 00000000' 00000000: fffff800 '02c5a95c fffffa60' 04dbf8b0 00000000'00000000 00000000'00000000: 0 x 2

  STACK_COMMAND: .bugcheck; Ko

  FOLLOWUP_IP:
  NT + e95c
  fffff800'02c5a95c?              ???

  SYMBOL_NAME: nt + e95c

  FOLLOWUP_NAME: MachineOwner

  Nom_image: ntoskrnl.exe

  BUCKET_ID: WRONG_SYMBOLS

  Follow-up: MachineOwner
  ---------

  I'm grateful for any help I can get in that case.

  My system is: AMD 9950BE CPU, motherboard ASUS Crosshair II Formula, 4 x 2 giga OCZ 1066 mhz memory, Vista Ultimate 64 bit, ASUS 295GTX GPU

  Postal salvation,

  I think you're in luck. It chances are you are one of those rare cases where the BSOD may not be hardware related. In addition, it is actually pretty rare to have so many errors after a sfc... Wow. I think that alone has helped reduce the risk of an another BSOD and was good insurance against other problems.

  Do you have a chance to check the hard drive? Now, I would like to check the hard drive to see if there may be potential damage to the hard drive as well to help explain this number of errors (return to the material again).

  Here's how to new:

  http://Windows.Microsoft.com/en-us/Windows-Vista/check-your-hard-disk-for-errors

  I think that advice on the anti-virus scanning are also actually still relevant today. I have a scan of one of the two groups below as soon as you can and let us know the result if you can.

  virus/malware programs:

  Symantec:

  Works in Safe Mode and free:

  _ http://security.symantec.com/sscv6/WelcomePage.asp

  Trend Micro

  _ http://housecall.trendmicro.com/

  Ad-ware/spyware:

  Ad-aware

  http://www.lavasoftusa.com/

  Spybot Search and Destroy

  http://www.safer-networking.org/

  * It is an excellent versatile tool as it will both spyware and malware and has also a small footprint.

  See you soon,.

  Steve <> Microsoft Partner