Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: dxgkrnl.sys BSODs

13 Feb 2010   #21
diliantraikov

Windows 7 Ultimate 32 bit
 
 

No BSoDs yet but will the Safe Mode give the same results as if it was in normal mode? Doesn't safe mode only start some of the drivers and so the faulty driver won't start and I won't get a bsod?


My System SpecsSystem Spec
.
13 Feb 2010   #22
usasma
Microsoft MVP

 
 

Yes, you're probably correct. Please boot into normal mode and let it crash. That'll create a memory dump file and, hopefully, it'll tell us what driver is causing it.

FYI - the use of Driver Verifier isn't guaranteed to work here - there's just not enough evidence for it. So, in short, this is just a shot in the dark by me
My System SpecsSystem Spec
13 Feb 2010   #23
diliantraikov

Windows 7 Ultimate 32 bit
 
 

I told you, when I restart the computer it reaches the part with the Starting Windows screen and then it restarts and I have to either boot into safe mode or launch system repair. And no crash dumps are created...
My System SpecsSystem Spec
.

13 Feb 2010   #24
usasma
Microsoft MVP

 
 

Sorry, I must've misunderstood. Driver Verifier will stress the drivers that are loaded - so those that aren't loaded in Safe Mode won't get stressed. It's most likely that your system is crashing to a BSOD - but that the crash occurs before the BSOD recording stuff is fully loaded.

Turn off Driver Verifier (go into the interface and select "Delete existing settings")
That should allow you to get into normal mode.

Then, go through the same steps for Driver Verifier - except this time try only one 3rd party (non-Microsoft) driver at a time. Then reboot and see if it crashes. Do this for all 3rd party drivers (keep a list of the ones that cause crashes/issues) and we'll work on replacing all those programs/drivers. There's no need to do any of the one's that may start with "dump_" as they're created when the dump occurs.
My System SpecsSystem Spec
14 Feb 2010   #25
diliantraikov

Windows 7 Ultimate 32 bit
 
 

The computer restarts when ALL of the non-microsoft drivers are being tested. (amdxata,asacpi,kbfiltr,l1e62x86,mv61xx,rtnicxp.sys) It reaches the Starting Windows screen and restarts until I go into safe mode.
My System SpecsSystem Spec
14 Feb 2010   #26
usasma
Microsoft MVP

 
 

Does this happen when you test rtnicxp.sys all by itself (for example)?
Just trying to clarify here.

If that's the case, then I'd suspect that there's either hardware issues or Windows issues.

To rule out Windows issues will require a wipe of the hard drive and reinstallation of Win7.
My System SpecsSystem Spec
14 Feb 2010   #27
diliantraikov

Windows 7 Ultimate 32 bit
 
 

Well I installed this copy of windows like 4 days ago and I deleted all the files from all of my hard drives. Anyway I'm going to send it to the guy who build it this week so he will check it out. Is there any test that checks all the hardware for errors?
My System SpecsSystem Spec
14 Feb 2010   #28
usasma
Microsoft MVP

 
 

A bunch of different tests:

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)

*****
Additional tests for certain specific circumstances:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Quote:
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
Try this free stress test: Free Software - GIMPS
Quote:
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.
My System SpecsSystem Spec
15 Feb 2010   #29
diliantraikov

Windows 7 Ultimate 32 bit
 
 

I downloaded the SeaTools from Seagate's site and they didn't find any errors. I have ran memtest many times before with no errors. Panda Active Scan only found cookies. FurMark reaches a temperature of 55 degrees and there don't appear to be any problems. As for the stress test about 5 minutes after I ran it one of the workers stopped (appearing to have found an error) and about 2 mins later I got a BSoD followed by another one just as the computer restarted.
My System SpecsSystem Spec
15 Feb 2010   #30
diliantraikov

Windows 7 Ultimate 32 bit
 
 

Here is the results.txt after just 2 minutes of testing:
Code:
[Mon Feb 15 14:05:55 2010]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Mon Feb 15 15:02:05 2010]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
FATAL ERROR: Resulting sum was 5.13270191348347e+019, expected: 7987718869985206
Hardware failure detected, consult stress.txt file.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Maximum number of warnings exceeded.
My System SpecsSystem Spec
Reply

 dxgkrnl.sys BSODs




Thread Tools




Similar help and support threads
Thread Forum
Lock ups and BSODs dxgkrnl.sys NDProxy.SYS
Hi all, been getting lock ups and BSODs on win XP for a while and presumed it just needed reinstalling as it was several years old, however I took the oportunity to move to W7 (fresh install not upgrade) and I'm still having problems. It will either lock up or BSOD at random, it has happend...
BSOD Help and Support
Random BSODs: ntoskrnl, dxgkrnl, dxgmms1, nvlddmkm, BCCode 116
Hi Guys. I'd appreciate some help here. I've been getting BSODs for quite a while now and would like some help in finding a solution. Attached is my SF zip. Looking at the dmp files, it seems it's either ntoskrnl or (dxgkrnl, dxgmms1, nvlddmkm). I have no idea what this means.
BSOD Help and Support
directx BSODs - dxgmms1.sys and dxgkrnl.sys
I recently built myself a new computer, with the following specs: i5 3750k, asrock z77 extreme4, 8GB Gskill sniper low voltage (model F3-12800CL9D-8GBSR2, two sticks of 4GB). I have an OCZ SSD (which isnt being used for windows at all, so, the specs arent important) and a WD caviar black...
BSOD Help and Support
BSODs Atikmpag.sys / Atikmdag.sys / dxgkrnl.sys
Hello. I keep getting chrashes that either a) causes the screen to make the screen picture reset itself with the error message like "Display driver AMD driver stopped responding and has successfully recovered". B) causes my screen to go crazy with pixels and colours before chrashing into BSOD....
BSOD Help and Support
New Build BSODS:dxgkrnl
I just put together a new PC and am getting some strange BSOD's and errors involving dxgkrnl. If you need any more info please ask. Here are my dumps. Thanks for the help in advance.
BSOD Help and Support
Seemingly Random dxgkrnl.sys BSODs
Hello. After a few months of no problems thanks to some great people on this forum I'm having problems again. In the past few days I've had at least 4 blue screens. Remembering what someone recommended I uninstalled my video card drivers, used Driver Sweeper to get rid of any remnants, and...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 09:37.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App