M MrPepka Sysnative Staff, BSOD Kernel Dump Senior Analyst Staff member Joined Feb 17, 2019 Posts 534 Jan 24, 2020 #22 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)
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)
C CoinCoin Windows Specialist Joined Jan 19, 2020 Posts 32 Jan 24, 2020 #23 Anyway, RDR2 doesn't work with DX11, rigth ?
C ColdFusion769 Member Joined Jan 21, 2020 Posts 22 Jan 24, 2020 #24 It doesn't if I remember, yet I use Vulkan anyway. Regardless I had no trouble with it for a whole month before problems occured
It doesn't if I remember, yet I use Vulkan anyway. Regardless I had no trouble with it for a whole month before problems occured
C ColdFusion769 Member Joined Jan 21, 2020 Posts 22 Jan 24, 2020 #25 I'm not getting dump files whilst using driver verifier
M MrPepka Sysnative Staff, BSOD Kernel Dump Senior Analyst Staff member Joined Feb 17, 2019 Posts 534 Jan 24, 2020 #26 Disable Driver Verifier and test your GPU with FurMark - FurMark Display Card Stress Test
C ColdFusion769 Member Joined Jan 21, 2020 Posts 22 Jan 24, 2020 #27 I ran FurMark and it maintained a constant temp of 72 Celsius at the 10 minute mark. Is there anything specific to look for here?
I ran FurMark and it maintained a constant temp of 72 Celsius at the 10 minute mark. Is there anything specific to look for here?
M MrPepka Sysnative Staff, BSOD Kernel Dump Senior Analyst Staff member Joined Feb 17, 2019 Posts 534 Jan 24, 2020 #28 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)
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)
C ColdFusion769 Member Joined Jan 21, 2020 Posts 22 Jan 24, 2020 #29 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.
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.
M MrPepka Sysnative Staff, BSOD Kernel Dump Senior Analyst Staff member Joined Feb 17, 2019 Posts 534 Jan 24, 2020 #30 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
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
C ColdFusion769 Member Joined Jan 21, 2020 Posts 22 Jan 25, 2020 #31 Driver verifier isn't helping, as it isn't providing dump files after crashes
M MrPepka Sysnative Staff, BSOD Kernel Dump Senior Analyst Staff member Joined Feb 17, 2019 Posts 534 Jan 25, 2020 #32 Well, check with a different graphics card because maybe the one you have is something wrong
C ColdFusion769 Member Joined Jan 21, 2020 Posts 22 Jan 26, 2020 #33 It still seems to be a driver/software issue as opposed to a hardware issue. My GPU works perfectly fine everywhere else
It still seems to be a driver/software issue as opposed to a hardware issue. My GPU works perfectly fine everywhere else
M MrPepka Sysnative Staff, BSOD Kernel Dump Senior Analyst Staff member Joined Feb 17, 2019 Posts 534 Jan 27, 2020 #34 I also thought that this could be a problem with the power supply. Have you checked on another?
C CoinCoin Windows Specialist Joined Jan 19, 2020 Posts 32 Jan 27, 2020 #35 MrPepka said: I also thought that this could be a problem with the power supply. Have you checked on another? Click to expand... oooooh ColdFusion769 said: 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 Click to expand... @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: Jan 27, 2020
MrPepka said: I also thought that this could be a problem with the power supply. Have you checked on another? Click to expand... oooooh ColdFusion769 said: 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 Click to expand... @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 ?
C CoinCoin Windows Specialist Joined Jan 19, 2020 Posts 32 Jan 27, 2020 #36 -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.
-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.
cluberti Senior Member Staff member Joined Mar 2, 2012 Posts 443 Location Redmond Jan 27, 2020 #37 ColdFusion769 said: No, there isn't one Click to expand... 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).
ColdFusion769 said: No, there isn't one Click to expand... 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).
A azajali43 New member Joined Jan 28, 2020 Posts 2 Jan 28, 2020 #38 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.
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.
C CoinCoin Windows Specialist Joined Jan 19, 2020 Posts 32 Jan 29, 2020 #39 cluberti said: 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). Click to expand... Oh, I made him doing this, sorry for that !
cluberti said: 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). Click to expand... Oh, I made him doing this, sorry for that !
C ColdFusion769 Member Joined Jan 21, 2020 Posts 22 Feb 1, 2020 #40 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 SysnativeFileCollectionApp.zip 3.4 MB · Views: 3
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.