Windows 7: "ntoskrnl.exe" BSOD

Neosporin · 05 Sep 2009

For the past few days now, I have been receiving blue screens (my computer would have restarted by the time I wake up).

Each time, the caused of the error reports has been "ntoskrnl.exe".

I've attached 4 dmp files to this post.

Any help is appreciated! Thanks.

dw96 · 05 Sep 2009

Firstly, I haven't had a BSOD problem(s) in a while, so forgive me if I say something stupid.
Second, I believe ntoskrnl.exe BSOD could be caused by boot.ini if it is erased or corrupted. Try booting into safe mode with command prompt and type in "chkdsk /f" without the quotation marks and wait a while. WARNING: This command erases/fixes any corrupted data on the HDD so some of your personal files may be erased. Then reboot normally. If the problem still occures, insert your Windows Seven CD/DVD and boot from it. Then repair your system.
That's all I can think of for now.

chev65 · 05 Sep 2009

Quote: Originally Posted by Neosporin

For the past few days now, I have been receiving blue screens (my computer would have restarted by the time I wake up).

Each time, the caused of the error reports has been "ntoskrnl.exe".

I've attached 4 dmp files to this post.

Any help is appreciated! Thanks.

Here is one clue on what the problem might be.
NTOSKRNL.EXE is missing or corrupt.

Microsoft way of fixing this problem.
http://support.microsoft.com/?kbid=314477

Utube fix for this problem also.
[ame="http://www.youtube.com/watch?v=j69K9H87j2s"]YouTube - How To Fix: Missing or Corrupt ntoskrnl.exe File[/ame]

Most of the fixes for this relate to Windows XP it seems.

Gazzasore · 05 Sep 2009

I had this very same problem a while back I tried everything that was thrown at me
but in the end
I just saved everything in safe mode and did a fresh install
then Wamo problem fixed

usasma · 05 Sep 2009

Test your memory using this free diagnostic: Bootable Memory Test Diagnostics - Vox

The first dump file contains a reference to your Avast antivirus protection. Please download a fresh copy, uninstall the current copy, then install the fresh copy.

Also, there's some older drivers on your system that are known to cause BSOD's. Here's a list of the old ones:

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005 
ElbyCDFL.sys Thu Dec 14 16:22:27 2006

Read this post for the ASACPI.sys driver: Asus ASACPI.sys driver for Win7
The Elby driver most likely belongs to CloneCD - please uninstall this program until we're finished fixing the BSOD's.

Here's a summary of the memory dumps:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep  4 11:16:27.449 2009 (GMT-4)
System Uptime: 0 days 0:20:52.119
BugCheck 19, {3, fffff8a00a371420, fffff8a007ffc2e0, fffff8a00a371420}
*** WARNING: Unable to verify timestamp for aswFsBlk.sys
*** ERROR: Module load completed but symbols could not be loaded for aswFsBlk.sys
Probably caused by : Pool_Corruption ( nt!ExFreePool+780 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wmplayer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep  4 10:54:24.685 2009 (GMT-4)
System Uptime: 0 days 8:09:52.355
BugCheck 19, {22, fffff8a00ade4000, 1, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+7338 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  TrustedInstall
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Sep  5 09:04:33.921 2009 (GMT-4)
System Uptime: 0 days 13:56:38.591
BugCheck 109, {a3a039d8958114f3, 0, 9f6561be01ee18aa, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Sep  5 09:19:52.455 2009 (GMT-4)
System Uptime: 0 days 0:03:03.001
BugCheck 1A, {41287, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42c75 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe

Neosporin · 06 Sep 2009

Quote: Originally Posted by usasma

Test your memory using this free diagnostic: Bootable Memory Test Diagnostics - Vox

The first dump file contains a reference to your Avast antivirus protection. Please download a fresh copy, uninstall the current copy, then install the fresh copy.

Also, there's some older drivers on your system that are known to cause BSOD's. Here's a list of the old ones:

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005 
ElbyCDFL.sys Thu Dec 14 16:22:27 2006

Read this post for the ASACPI.sys driver: Asus ASACPI.sys driver for Win7
The Elby driver most likely belongs to CloneCD - please uninstall this program until we're finished fixing the BSOD's.

Here's a summary of the memory dumps:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep  4 11:16:27.449 2009 (GMT-4)
System Uptime: 0 days 0:20:52.119
BugCheck 19, {3, fffff8a00a371420, fffff8a007ffc2e0, fffff8a00a371420}
*** WARNING: Unable to verify timestamp for aswFsBlk.sys
*** ERROR: Module load completed but symbols could not be loaded for aswFsBlk.sys
Probably caused by : Pool_Corruption ( nt!ExFreePool+780 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wmplayer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep  4 10:54:24.685 2009 (GMT-4)
System Uptime: 0 days 8:09:52.355
BugCheck 19, {22, fffff8a00ade4000, 1, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+7338 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  TrustedInstall
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Sep  5 09:04:33.921 2009 (GMT-4)
System Uptime: 0 days 13:56:38.591
BugCheck 109, {a3a039d8958114f3, 0, 9f6561be01ee18aa, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Sep  5 09:19:52.455 2009 (GMT-4)
System Uptime: 0 days 0:03:03.001
BugCheck 1A, {41287, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42c75 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe

Thanks for the in-depth reply.

I have swapped out my memory for different sticks and it seems to have stopped the BSODs. Just to be sure, I have reinstalled Avast and there have yet to be any crashes (knocks on wood).

The thread you linked me to regarding the ASACPI.sys driver also doesn't exist anymore :P

king44 · 06 Sep 2009

Try to fix the boot sector with the installation dvd (choose the repair startup option), if you are using dual boot on 2 different HDDs you may want to check the boot order.

It may help

usasma · 06 Sep 2009

Try this link: http://www.sevenforums.com/general-d...tml#post157051

Basically, go to the Asus support website and download the Windows 7 version of the Asus AISuite

Nasters · 21 Feb 2012

Hi gang,

Hope s1 can help me with my ntoskrnl.exe error problems. Im going solely by what "who crashed" has given answers for but i have attached a minidump as well. (Providing I am doing it right).

The following i was given via who crashed as i stated earlier..
I am not completely sure what happened here.. it has been off since October and been inside a closet. I get this error withing the first 10 minutes of booting... It has been a great pc up til this point.

On Tue 2/21/2012 2:36:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022012-16816-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x32492B)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF8647477C, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Thanks e1 who helps.. i edited to see if dump uploaded properly

writhziden · 21 Feb 2012

Please start your own thread with the above information. This will guarantee you get the help you need and it will help others with similar problems who stumble across your thread.

In the meantime, see Stop 0x124 - what it means and what to try for your crash.

Windows 7: "ntoskrnl.exe" BSOD

"ntoskrnl.exe" BSOD problems?