BSOD - ntoskrnl.exe constantly at fault?

Perovich · 04 Nov 2011

Forgive me, for I'm completely and technologically illiterate, but I purchased new computer parts, have installed the OS and appropriate up-to-date drivers for everything and am now being plagued by BSODS. Such as:
-DRIVER_IRQL_NOT_LESS_OR_EQUAL
-SYSTEM_SERVICE_EXCEPTION
-PAGE_FAULT_IN_NONPAGED_AREA
-KMODE_EXCEPTION_NOT_HANDLED

You get the point. Anyways, all of these seem to have an error with the "ntoskrnl.exe" file (Found that out using BlueScreenView). I have passed memtest86, Windows Memory Diagnostics, Video Memory Stress Tests and the chkdsk /f /r commands in the Command Prompt.

System specs:
Windows 7 Home Premium64-bit (Purchased OEM, installed myself)
G.Skill 4096Mb (2x2GB) RAM
1Tb Seagate Barracuda Internal HDD - 7200, 6Gb/sec
Asus P8H61M-LE/CSM 1155 Intel Motherboard
Asus GTX 550Ti 192-bit Graphics Card (1Gb onboard RAM)
Antec Earthwatts 500W Continuous Power PSU 80+Bronze
Intel Core i3-2100 3.1GHz

Thanks guys!

Minidump files:

jcgriff2 · 04 Nov 2011

Hi -

ntoskrnl.exe = Windows NT Kernel. It is listed by default and is most definitely not the cause.

The dumps indicate memory, video and one points to possible HDD failure.

These old Asus drivers may be part of the problem; I suggest updating them -

Code:

ATKDispLowFilter.sys Tue May 13 23:03:13 2008 (482A5671)
asusgsb.sys          Thu Sep 27 09:14:50 2007 (46FBACCA)
EIO64.sys            Tue Jul 21 22:34:42 2009 (4A667AC2)

http://sysnative.com/0x1/DriverReference.html#EIO64.sys
http://sysnative.com/0x1/DriverReference.html#ATKDispLowFilter.sys
http://sysnative.com/0x1/DriverReference.html#asusgsb.sys

Run HDD diags - http://www.techsupportforum.com/2828431-post7.html

Run memtest86+ - http://www.techsupportforum.com/2863029-post5.html

Test video - Video Card - Stress Test with Furmark

Regards. . .

jcgriff2

`

BSOD SUMMARY

Code:


Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\110311-14414-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Nov  4 02:14:11.266 2011 (GMT-4)
System Uptime: 0 days 0:03:11.577
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
Bugcheck code 0000003B
Arguments 00000000`c000001d fffffa80`07f7c660 fffff880`0606cbc0 00000000`00000000
BiosVersion = 0503
BiosReleaseDate = 07/18/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3100
CurrentSpeed: 3092
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\110311-14180-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Nov  3 05:04:18.434 2011 (GMT-4)
System Uptime: 0 days 5:12:30.371
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+4e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+4e
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`02d52ee2 fffff880`088e2e80 00000000`00000000
BiosVersion = 0503
BiosReleaseDate = 07/18/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3100
CurrentSpeed: 3092
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\110111-19437-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Nov  1 03:37:22.696 2011 (GMT-4)
System Uptime: 0 days 0:18:35.007
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+447c6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+447c6
Bugcheck code 00000050
Arguments fffff6fb`cca00232 00000000`00000000 fffff800`02ff6602 00000000`00000002
BiosVersion = 0503
BiosReleaseDate = 07/18/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3100
CurrentSpeed: 3092
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\103111-18688-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Nov  1 00:47:33.106 2011 (GMT-4)
System Uptime: 0 days 0:00:53.418
Probably caused by : ndis.sys ( ndis!ndisMWakeUpDpcX+148 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_ndis!ndisMWakeUpDpcX+148
Bugcheck code 0000000A
Arguments 00000000`00000008 00000000`00000002 00000000`00000001 fffff800`02e89a26
BiosVersion = 0503
BiosReleaseDate = 07/18/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3100
CurrentSpeed: 3092
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\103011-29967-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Oct 30 22:38:44.850 2011 (GMT-4)
System Uptime: 0 days 0:30:47.145
Probably caused by : ntkrnlmp.exe ( nt!IopInterlockedDecrementUlong+3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Launcher.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!IopInterlockedDecrementUlong+3
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02ef5983 fffff880`087a6a10 00000000`00000000
BiosVersion = 0503
BiosReleaseDate = 07/18/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3100
CurrentSpeed: 3193
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\103011-20404-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Oct 30 20:12:55.953 2011 (GMT-4)
System Uptime: 0 days 0:16:33.828
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+179 )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteFcb+179
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0337e538 fffff880`0337dd90 fffff800`02f0c77b
BiosVersion = 0503
BiosReleaseDate = 07/18/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3100
CurrentSpeed: 3193
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\103011-25630-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Oct 30 19:46:27.552 2011 (GMT-4)
System Uptime: 0 days 0:02:42.816
Probably caused by : win32k.sys ( win32k!NtGdiBitBltInternal+d76 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  LogonUI.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!NtGdiBitBltInternal+d76
Bugcheck code 00000050
Arguments ffffffff`ffffff8c 00000000`00000001 fffff800`02fb35ab 00000000`00000000
BiosVersion = 0503
BiosReleaseDate = 07/18/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3100
CurrentSpeed: 3193
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

by jcgriff2     
             
         J. C. Griffith, Microsoft MVP   
             
           https://mvp.support.microsoft.com/profile/Griffith   


           www.sysnative.com
             
           www.jcgriff2.com 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Perovich · 06 Nov 2011

I tested 8 passes with Memtest86, and found 0 errors.
The HDD diagnostics test came back flawless as well.
Furmark ran flawlessly, too. GPU ran at around 70*C the entire time, so overheating wasn't an issue.

If those drivers are the issue, where might I go to download the appropriate, current versions? I can't seem to find them anywhere.

**cluberti** · 06 Nov 2011

Note that the error codes for the 3B failures are:
c000001b - STATUS_ILLEGAL_INSTRUCTION
c0000005 - STATUS_ACCESS_VIOLATION

The others, while the status codes change, are similar in failure to these two error codes. It would actually seem to be a driver issue, given the data points you've provided. Time to do a nice clean sweep of drivers on the system and upgrade any and all that are outdated to the latest released driver versions for Windows 7, and let us know if the problem continues (or doesn't

).

Perovich · 06 Nov 2011

DriverScanner is telling me these two drivers are out of date:
Intel(R) 6 Series/C200 Series Chipset Family 2 port Serial ATA Storage Controller - 1C08
Intel(R) 6 Series/C200 Series Chipset Family 4 port Serial ATA Storage Controller - 1C00

It's telling me versions 9.2.0.1014 are the most recent and 9.2.0.1011 is what's installed... any idea how I'd go about getting these drivers through Intel?

And how can get the drivers to the above three that JCGriff listed?
-asusgsb.sys
-EIO64.sys
-ATKDispLowFilter.sys

Thanks again.

**cluberti** · 06 Nov 2011

The Intel updates, at least, are easy to do:
Intel® Driver Update Utility

As to the others:
asusgsb.sys - ASUS Virtual Video Capture Device Driver
EIO64.sys - ASUS Kernel Mode Driver for NT
ATKDispLowFilter.sys - ASUSTeK Display Lower Filter

All of these can be updated from the support site for your ASUS motherboard.

"Build a man a fire, and he is warm for a day. Set a man on fire, and he is warm for the rest of his life."

Perovich · 06 Nov 2011

Alright, after spending some time updating drivers and researching all these Asus drivers... I found that I could just uninstall Asus GamerOSD and Asus SmartDoctor... according to other Asus users, that should solve a majority of these BSODs.

However, I did receive a few more tonight, and was wondering if you could tell me if they were caused by the same drivers? If I get anymore, I'll be sure to post them (that way I'll know if it was the Asus drivers after all). Thanks!

**cluberti** · 06 Nov 2011

It still appears to be some sort of driver issue, but unfortunately minidumps just aren't going to give up the goods. You're going to have to configure your machine for a kernel dump and get another crash dump (it'll be much bigger, will need to be zipped up, and uploaded to a filesharing site once you do).

Perovich · 06 Nov 2011

After hours, I finally got it to crash again. I'm not entirely sure I'm doing this correctly, but here's the link to what (I think) is the MEMORY.dmp folder that was created.

MEMORY.zip

Perovich · 12 Nov 2011

Alright, after a little digging, and some posting over on the Tech Support Forums, I'd figured I'd try and double my luck at getting this resolved by posting here as well.

Here's the collective minidumps, Memory Dump, PERFMON HTML file, and Windows7_Vista_jcgriff2 folder:
MEMORY.zip