Windows 7: dxgkrnl.sys BSODs

diliantraikov · 21 Jan 2010

Hi guys,

I've been getting some bsods recently and I tried opening the crash dumps with Windows Debugging Tools following the tutorial in this forum. But when I open them I get "***** Kernel symbols are WRONG. Please fix symbols to do analysis."
I couldn't manage to fix them so I downloaded BlueScreenView and in 3 of the 5 bsods the problem is probably caused by dxgkrnl.sys.Can anyone have a look at the minidumps and tell me what I can do to remove these bsods.

Thanks in advance

My system spec:
OS: Windows 7 Ultimate 32-bit
Processor: Intel Core 2 Quad Q8200 2,33GHz
RAM: 4GB
Video Card: NVIDIA GeForce 9500 GT 1GB

zigzag3143 · 21 Jan 2010

Quote: Originally Posted by diliantraikov

Hi guys,

I've been getting some bsods recently and I tried opening the crash dumps with Windows Debugging Tools following the tutorial in this forum. But when I open them I get "***** Kernel symbols are WRONG. Please fix symbols to do analysis."
I couldn't manage to fix them so I downloaded BlueScreenView and in 3 of the 5 bsods the problem is probably caused by dxgkrnl.sys.Can anyone have a look at the minidumps and tell me what I can do to remove these bsods.

Thanks in advance

My system spec:
OS: Windows 7 Ultimate 32-bit
Processor: Intel Core 2 Quad Q8200 2,33GHz
RAM: 4GB
Video Card: NVIDIA GeForce 9500 GT 1GB

Hi and welcome. Well will technically correct your video driver was at least 'involved. there are many possible causes.
these are Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory

I also noticed one dmp was caused by driver verifier. You did turn that off, correct?

I would:
DL memtestx86 and run it for 5 passes

run a system file check
type cmd in search>right click and run as admin>sfc /scannow

If you are overclocking STOP

If the BSOD continue were can get more aggressive.

Ken J+

Code:

010910-18720-01.dmp    1/9/2010 8:49:16 PM    BAD_POOL_HEADER    0x00000019    0x00000003    0x85b02880    0x87386880    0x87386880    watchdog.sys    watchdog.sys+107e                    32-bit        C:\Users\K\Desktop\Minidump\010910-18720-01.dmp    4    15    7600    
010910-26878-01.dmp    1/9/2010 9:05:34 PM    DRIVER_VERIFIER_IOMANAGER_VIOLATION    0x000000c9    0x00000302    0x8328762d    0xada00f68    0x00000001    ntkrnlpa.exe    ntkrnlpa.exe+dccfc                    32-bit        C:\Users\K\Desktop\Minidump\010910-26878-01.dmp    4    15    7600    
011010-16239-01.dmp    1/10/2010 8:35:07 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc0000005    0x9312f93c    0x9a2cb73c    0x00000000    dxgkrnl.sys    dxgkrnl.sys+1c93c                    32-bit        C:\Users\K\Desktop\Minidump\011010-16239-01.dmp    4    15    7600    
011110-26410-01.dmp    1/11/2010 10:49:35 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc0000005    0x99bff346    0xa3796b74    0x00000000    win32k.sys    win32k.sys+af346                    32-bit        C:\Users\K\Desktop\Minidump\011110-26410-01.dmp    4    15    7600    
012110-25724-01.dmp    1/21/2010 12:20:53 AM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc0000005    0x93127c44    0xbd1d973c    0x00000000    dxgkrnl.sys    dxgkrnl.sys+1cc44                    32-bit        C:\Users\K\Desktop\Minidump\012110-25724-01.dmp    4    15    7600

diliantraikov · 21 Jan 2010

I ran memtest (1 pass only though) and it found no errors.
Driver Verifier is off.I don't remember ever turning it on...
I have ran the system check a few times and it says:

Code:

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log

but the next time I run it it shows the same message so I don't know if it really does anything.
I guess I'm not overlocking as I don't even know what this means...

usasma · 21 Jan 2010

Please run MemTest for the 5 passes that zigzag3143 asked for.
Often a system won't spit errors on the first pass.
If time is a problem, start it when you leave the system for the night - and let it run overnight.

diliantraikov · 23 Jan 2010

I ran the memtest overnight and it completed 11 passes with no errors... Before running it,however,I got 3 bsods for less than 2 hours... Here are the minidumps:

usasma · 23 Jan 2010

Try these free diagnostics:

Quote:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

It's gonna take a while for the memory dumps to run (due to the symbol problems).
Please let us know where you got your copy of Windows 7 from - as the version number is different than most, and it won't recognize the symbols.

usasma · 23 Jan 2010

The most likely fault is due to your video drivers. So if the video stress test passes, please update your video drivers.

Also, Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:

Quote:

How To Find Updated Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- some driver links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers:

Code:

adfs.SYS     Thu Aug 14 10:57:15 2008 - Adobe File System
ASACPI.sys   Thu Aug 12 22:52:52 2004 - Asus ATK0110 ACPI Utility (also in PCProbe and AISuite Utilities)
StarOpen.SYS Tue Jun 27 15:15:56 2006 - StarOpen or VideoNow Media Wizard or RPS Burn by Hasbro or AT&T or Verizon or Virgin Broadband.

Here's the summary of the BSOD's:

Code:

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Wed Jan 20 17:19:16.416 2010 (GMT-5)
System Uptime: 0 days 13:25:24.382
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 1000008E, {c0000005, 93127c44, bd1d973c, 0}
Probably caused by : dxgkrnl.sys ( dxgkrnl+1cc44 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Fri Jan 22 04:52:20.641 2010 (GMT-5)
System Uptime: 0 days 1:19:38.608
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck A, {ffffffe0, 2, 0, 830b81cc}
Probably caused by : ntkrnlpa.exe ( nt+9f1cc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Fri Jan 22 14:15:08.052 2010 (GMT-5)
System Uptime: 0 days 9:21:10.003
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000007E, {c0000005, 8c5c6abf, a6243788, a6243360}
Probably caused by : cng.sys ( cng!SHA512Final+13f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Fri Jan 22 14:25:38.771 2010 (GMT-5)
System Uptime: 0 days 0:04:00.737
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BugCheck D1, {d1323610, 2, 0, 928c893f}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+bf93f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Fri Jan 22 14:46:44.440 2010 (GMT-5)
System Uptime: 0 days 0:07:26.391
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 1000008E, {c0000005, 8313504d, a32ab954, 0}
Probably caused by : dxgkrnl.sys ( dxgkrnl+1c224 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

diliantraikov · 29 Jan 2010

Well, I ran and updated everything I could and for a couple of days there were no bsods. Today I got 3 for like 3 hours... I ran driver verifier and when I restarted the computer it wouldn't start until I ran Startup Repair.When I went to driver verifier my settings were deleted. So I guess it isn't a hardware issue. How can we see which driver didn't let windows start?

diliantraikov · 30 Jan 2010

OK, so I ran driver verifier/create standart settings/automatically select unsigned drivers and the only unsigned driver listed was staropen.sys. I then restarted the computer and again it wouldn't start. So I guess the problem is in this driver. Any ideas what I should do as I can't find anything in google.

usasma · 30 Jan 2010

This isn't necessarily the case - it may be that a signed driver is causing the BSOD. Driver Verifier settings have to be picked from the type of BSOD error that you have. For example, if you have pool corruption you want a setting that stresses the memory pool in order to see what driver causes the BSOD. If you don't stress the pool, there won't be an error revealed by the stressed driver.

Secondly, without the proper symbols, there won't be much point in analyzing the memory dump files.
Your version of Windows 7 doesn't have the appropriate symbols loaded into the Microsoft Symbol Server (nor on my system).

The dump files are running, but are very slow due to the missing symbols. I'll be back when they're done.

Windows 7: dxgkrnl.sys BSODs

dxgkrnl.sys BSODs problems?