[SOLVED] BSOD 0x1E (0, 0, 0) in 3 games, nowhere else. FIX: used AMD driver cleaning tool, then installed AMD drivers.

Disable Driver Verifier and re-enable again with the same settings but for verify choose only drivers for graphics card (atikmdag.sys and atikmpag.sys without DirectX drivers)
 
I meant loading the graphics card by testing it in such a way that it warms up properly. Although I don't know if that's a good lead
You can still run Driver Verifier with the same settings as before, but for verification set the drivers from AMD (atikmdag.sys and atikmpag.sys) and the driver from the kernel (ntoskrnl.exe)
 
When not using driver verifier, the crash logs in BlueScreenViewer show that notskrnl.exe is the only driver highlighted in red whereas previously the AMD drivers were also highlighted. I'm assuming that maybe that is the problem? Of course, that is just a stab in the dark from me, but it does stand out a bit.

EDIT: I meant to say that the AMD drivers were no longer highlighted AFTER I did a clean install of the latest AMD GPU drivers, so I am assuming that the update did fix that area. However it seems that notskrnl.exe is still an outlier.
 
ntoskrnl.exe is a driver from the kernel of the system so it is not guilty, but this test is about checking whether the graphics card drivers correctly refer to the kernel API because maybe there is a problem
 
Well, check with a different graphics card because maybe the one you have is something wrong
 
I also thought that this could be a problem with the power supply. Have you checked on another?
 
I also thought that this could be a problem with the power supply. Have you checked on another?
oooooh

Hardware:
Intel i7 2600K 4-core @3.40GHz (O/C to 4.00GHz)
AMD Radeon RX 580 8GB VRAM
(...)
I use a 500W PSU, don't recall the brand

@ColdFusion769, how long have you O/Ced the proc and had that card ?
That Radeon goes around 220W in gaming, and TDP of your proc is 95W. O/C + boost may put this one @150W.
Add fans for 30W, HDD for 20W, SDD for 10W, MB for 40W and at full charge, a few W here and there from USB stuff meaning you're charging your PSU @94% or more.
Which means if it's one year old or more, your power lines can give say 98% of it, and very unstable power lines.

In that case, the mobo usually safelly cuts HDD first, to poweroff HDD and secure reading heads.
==> here may be your LOCK file ressource. OS may say "Hey can't write on a poweroff disc".

Could you borrow a 750W PSU for tests ?

-edit- is there some kind of "PSU enter panic mode" windows event ? If so, do they occurs before those BSOD ?
 
Last edited:
-Alternate test-
Remove a few sticks of RAM, unplug the most USB stuff you can, remove O/C and play your games with the same settings.
 
No, there isn't one
That's because you've moved the paging file off of the \Windows volume previously in this thread - without setting a DedicatedDumpFile setting in the registry, Windows cannot rename pagefile.sys to memory.dmp during boot after a bugcheck if it isn't on the same volume as the \Windows directory, thus you get no dump file(s).
 
Blue screen error 0x0000001e, Occurs when you were playing the game. So, You would like to fix the error permanently. Since there are many causes of the 0x0000001e error, You can solve the problem by trying the fixes one by one like, Fix the faulty RAM, Solve drivers problem, Clear viruses or malware, Remove the antivirus program, System restore.
 
That's because you've moved the paging file off of the \Windows volume previously in this thread - without setting a DedicatedDumpFile setting in the registry, Windows cannot rename pagefile.sys to memory.dmp during boot after a bugcheck if it isn't on the same volume as the \Windows directory, thus you get no dump file(s).
Oh, I made him doing this, sorry for that !
 
Here is some more dump files, just in case anyone can narrow down any possible problems. As far as the power supply goes, it turns out that I have an 850W PSU. So any crashes can't be related to a lack of power, not to mention I have crashes even when the O/C has been disabled.

I even went and re-seated the components of my PC completely, just in case there was anything that wasn't properly connected and that didn't solve it.

I guess it must be a software/driver issue, but I have yet to come close to identifying it.
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top