Question Constant BSOD (Windows 10) after new GPU installed and still now old GPU is being used

[Firefly_t1000]

I'm having constant BSOD after going back to my old GPU - here's some background.

Specs are:
Ryzen 5 3600
MSI B450 Tomahawk
16GB DDR4 3200mhz HyperX Predator
500GB Crucial MX500 SSD
Gigabyte GTX 960 4GB Windforce
EVGA 500w PSU

I bought a new GPU last week (MSI Radeon RX 5600 XT Mech OC), I had what seems to be very common issues with AMD cards at the moment - black screen when playing games and a blue screen or two. I tried several fixes I found online including uninstalling all Nvidia drivers using display driver uninstaller and updating motherboard BIOS, none of them helped. Just before I made the decision to return the GPU I got BSOD a couple of times with different stop codes. I put my old GPU in and the blue screens continued. I removed the old AMD drivers, by uninstalling the AMD software and using DDU and I installed the Nvidia drivers but this didn't help. After, again, trying a few fixes I decided to do a clean install of Windows 10. Unfortunately this hasn't helped and the blue screens continue, tried lots of different fixes and nothing seems to help.

Even after resetting Windows I still get a variety of codes including:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
PAGE_FAULT_IN_NONPAGES_AREA
KERNEL_AUTO_BOOST_LOCK_AQUISITION_WITH_RAISED_IRQL
KERNEL_SECURITY_CHECK_FAILURE
APC_INDEX_MISMATCH
KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION

Blue screen doesn't seem to happen at any specific time, just when I do anything, usually within a minute of booting. Safe mode seems to be fine.

Would really appreciate any advice you can give me.

 

[Colif]

KERNEL_AUTO_BOOST_LOCK_AQUISITION_WITH_RAISED_IRQL - i have seen this caused by LAN drivers.
KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION - this is a new one... can't say I seen this before.


Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

after reset? Have you updated drivers on motherboard? Have you run MSI Dragon Centre as I believe it updates drivers for you - https://www.msi.com/Motherboard/support/B450-TOMAHAWK#down-driver&Win10 64

 

[Firefly_t1000]

KERNEL_AUTO_BOOST_LOCK_AQUISITION_WITH_RAISED_IRQL - i have seen this caused by LAN drivers.
KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION - this is a new one... can't say I seen this before.


Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

after reset? Have you updated drivers on motherboard? Have you run MSI Dragon Centre as I believe it updates drivers for you - https://www.msi.com/Motherboard/support/B450-TOMAHAWK#down-driver&Win10 64

Thanks for the reply, here are the files, I included the last two from today:
https://www.dropbox.com/sh/bo1l70hsfcjcdix/AABk2Co7lzm6e3dEMVeYGrY9a?dl=0

Yes, I did update the motherboard drivers after reinstalling windows.

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://dreamiestleaftailedgecko.htmlpasta.com/

File information:	040820-6484-01.dmp (Apr 8 2020 - 10:28:03)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 05 Sec(s)

File information:	040820-6468-01.dmp (Apr 8 2020 - 10:25:22)
Bugcheck:	DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Probably caused by:	memory_corruption (Process: VSSVC.exe)
Uptime:	0 Day(s), 0 Hour(s), 13 Min(s), and 49 Sec(s)

Possible Motherboard page: https://www.msi.com/Motherboard/B450-TOMAHAWK
You have the latest BIOS already installed, version 1.D.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Firefly_t1000]

Thanks for the reply, here are the files, I included the last two from today:
https://www.dropbox.com/sh/bo1l70hsfcjcdix/AABk2Co7lzm6e3dEMVeYGrY9a?dl=0

Yes, I did update the motherboard drivers after reinstalling windows.

I should mention this is after I put the 5600xt back in the system to see if that helps (it doesn’t).

 

[gardenman]

When did you start using Verifier? It's turned on. It's job is to stress drivers out until they crash.

 

[Colif]

Driver Verifer - its always turned on, It just doesn't often appear in errors.Volume shadow copy crashed? that is the process that is otherwise known as System restore...

wonder what would cause that...
motherboard website has realtek audio drivers but actual system is showing AMD HD Audio, I am not sure if thats part of the GPU drivers. Or if it was installed by windows as some of these are defaults.
Newer LAN drivers on MSI website - https://www.msi.com/Motherboard/support/B450-TOMAHAWK#down-driver&Win10 64

All but one of the drivers running are from AMD.
The chipset drivers might be latest, the ones on MSI site are 1 month newer than whats installed, that is within range of being the same.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. (just to remove it as a possible cause as if i see weird errors like this, I should check ram)

 

[gardenman]

The reason I asked is because Driver Verifier usually doesn't have that many switches turned on. Compare "Extra 1" in his dumps to other dumps. There was also a VERIFIER bugcheck. Therefore I assume verifier is "on" when it's usually "off".

 

[Firefly_t1000]

The reason I asked is because Driver Verifier usually doesn't have that many switches turned on. Compare "Extra 1" in his dumps to other dumps. There was also a VERIFIER bugcheck. Therefore I assume verifier is "on" when it's usually "off".

I had actually turned on verifier shortly before.

 

[Firefly_t1000]

Driver Verifer - its always turned on, It just doesn't often appear in errors.Volume shadow copy crashed? that is the process that is otherwise known as System restore...

wonder what would cause that...
motherboard website has realtek audio drivers but actual system is showing AMD HD Audio, I am not sure if thats part of the GPU drivers. Or if it was installed by windows as some of these are defaults.
Newer LAN drivers on MSI website - https://www.msi.com/Motherboard/support/B450-TOMAHAWK#down-driver&Win10 64

All but one of the drivers running are from AMD.
The chipset drivers might be latest, the ones on MSI site are 1 month newer than whats installed, that is within range of being the same.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. (just to remove it as a possible cause as if i see weird errors like this, I should check ram)

I've installed the newer LAN drivers and chipset drivers, no help unfortunately.

I also ran memtest86 on each stick for 4 passes with 0 errors.

 

[Colif]

Please share any new dumps you get as more info the better.
Have you installed all the software for the hardware in PC? Just wondering if its a device that just doesn't have any drivers yet.

BSOD that survive installs normally signal that its hardware, not software.

I am not sure if this includes tests for ssd - https://www.crucial.com/support/storage-executive

 

[Firefly_t1000]

Please share any new dumps you get as more info the better.
Have you installed all the software for the hardware in PC? Just wondering if its a device that just doesn't have any drivers yet.

BSOD that survive installs normally signal that its hardware, not software.

I am not sure if this includes tests for ssd - https://www.crucial.com/support/storage-executive

After downloading the crucial software and getting new dumps I now can’t seem to restart into safe mode, restarting just goes to a black screen then eventually goes to the blue screen with stop code driver power state failure. Also, when I try to shut down it goes to black screen and then eventually just restarts. Not being able to boot into safe mode means it’s difficult to do anything as booting normally just leads to a blue screen after about a minute.

Managed to save the dump files from yesterday.

https://www.dropbox.com/sh/5oaaz90and76vvw/AACnKL9dH8JAsK484EJq46CXa?dl=0

 

[Colif]

did you install the crucial software or just download it? just curious if its involved or just a coincidence. the fact Driver verifer crashed volume shadow copy could maybe hint at it being ssd to blame.

its not the gpu
its not the ram
impossible to test motherboard
PSU can cause odd errors although they are not exactly easy to test
the paper clip method - https://forums.tomshardware.com/threads/what-is-the-paperclip-method-of-testing-a-psu.1336402/

or multimeter,
or in the BIOS to check the +3.3V, +5V, and +12V. - https://www.lifewire.com/power-supply-voltage-tolerances-2624583
can test CPU with Prime 95 bootable - https://www.infopackets.com/news/10113/how-fix-bootable-prime95-stress-test-hardware

Prime 95 guide - http://www.playtool.com/pages/prime95/prime95.html

download this on pc (Or another one) and see if you have enough time to run it on PC before you bsod. https://www.sysnative.com/forums/pages/bsodcollectionapp/
it will at least show me what WIndows error reporting is seeing each time.

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://zenithalmonth.htmlpasta.com/

File information:	041020-6203-01.dmp (Apr 10 2020 - 05:45:43)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 09 Sec(s)

File information:	041020-5859-01.dmp (Apr 10 2020 - 05:39:21)
Bugcheck:	KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL (192)
Probably caused by:	win32kbase.sys (Process: explorer.exe)
Uptime:	0 Day(s), 0 Hour(s), 01 Min(s), and 52 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

Wonders if saying GPU wasn't problem was over reaching. It could be it just creates different errors. I assume that ryzen doesn't have graphics cores (only as if it did we could run without a gpu).

the blank screens at startup should have been a clue.

The kernel auto boost lock acquisition with raised irq error appears to be GPU error. one of the commands run just before errors was using WIn 10 Graphics Device Interface.

Its not a normal error (even for ATI cards, I normally see another one). Its impossible to blame anyone apart from AMD for these errors though given its all you have running. And its difficult to tell which are installed by windows as it includes some by default

Mar 19 2015 amd_sata.sys AMD SATA Controller AHCI Device driver http://support.amd.com/
Mar 19 2015 amd_xata.sys AMD Stor Filter driver http://support.amd.com/
Mar 14 2016 amdgpio3.sys AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
May 17 2019 amdgpio2.sys AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
Jun 19 2019 amdpsp.sys Advanced Micro Devices, Inc http://support.amd.com/
Jul 24 2019 AMDPCIDev.sys Advanced Micro Devices PCI Device driver
Nov 15 2019 AtihdWT6.sys AMD High Definition Audio Function driver http://support.amd.com/
Nov 18 2019 rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
Apr 01 2020 atikmdag.sys ATI Radeon Kernel Mode driver
Apr 01 2020 atikmpag.sys ATI video card driver

I think you need to uninstall the AMD display drivers in windows since it won't load safe mode. See if it stops the BSOD after startup effect.

Or put the Nvidia card back in and see if that makes any difference. I know it didn't last time.
Changing GPU shouldn't cause BSOD, but it might have changed how the systems power draw was balanced and it might be something else is failing. When I upgraded from a 960 to a 980 (yeah, I know, massive) my screen randomly stopped loading desktop at startup. It was after troubleshooting including reinstalling win 10 , that I figured out cause was my speakers weren't responding at startup and delaying desktop. So just little changes can set off other parts that had worked perfectly fine (for 15 years)

or get pc repaired... If it was a perfect world and we were able to travel freely to a shop and ask them to figure out whats wrong.

 

[Firefly_t1000]

Wonders if saying GPU wasn't problem was over reaching. It could be it just creates different errors. I assume that ryzen doesn't have graphics cores (only as if it did we could run without a gpu).

the blank screens at startup should have been a clue.

The kernel auto boost lock acquisition with raised irq error appears to be GPU error. one of the commands run just before errors was using WIn 10 Graphics Device Interface.

Its not a normal error (even for ATI cards, I normally see another one). Its impossible to blame anyone apart from AMD for these errors though given its all you have running. And its difficult to tell which are installed by windows as it includes some by default

Mar 19 2015 amd_sata.sys AMD SATA Controller AHCI Device driver http://support.amd.com/
Mar 19 2015 amd_xata.sys AMD Stor Filter driver http://support.amd.com/
Mar 14 2016 amdgpio3.sys AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
May 17 2019 amdgpio2.sys AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
Jun 19 2019 amdpsp.sys Advanced Micro Devices, Inc http://support.amd.com/
Jul 24 2019 AMDPCIDev.sys Advanced Micro Devices PCI Device driver
Nov 15 2019 AtihdWT6.sys AMD High Definition Audio Function driver http://support.amd.com/
Nov 18 2019 rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
Apr 01 2020 atikmdag.sys ATI Radeon Kernel Mode driver
Apr 01 2020 atikmpag.sys ATI video card driver

I think you need to uninstall the AMD display drivers in windows since it won't load safe mode. See if it stops the BSOD after startup effect.

Or put the Nvidia card back in and see if that makes any difference. I know it didn't last time.
Changing GPU shouldn't cause BSOD, but it might have changed how the systems power draw was balanced and it might be something else is failing. When I upgraded from a 960 to a 980 (yeah, I know, massive) my screen randomly stopped loading desktop at startup. It was after troubleshooting including reinstalling win 10 , that I figured out cause was my speakers weren't responding at startup and delaying desktop. So just little changes can set off other parts that had worked perfectly fine (for 15 years)

or get pc repaired... If it was a perfect world and we were able to travel freely to a shop and ask them to figure out whats wrong.

In response to your last two messages.

Don't think the crucial software fully installed before the additional problems happened (not being able to boot into safe mode etc.), it was listed in the start menu but not in the list of installed programs. Also, not convinced it can be an SSD problem as i installed windows on my HDD and was still getting BSOD.

PSU - I checked the bios and 5v is 5.050 and 12v is 12.216 - there was no 3.3v at all under the PC Health Status section.

I ran the Marsenne Prime Test v28 and was still running after 24 hours with no crashes.

Took your advice and removed the 5600XT and put the 960 back in, removed AMD drivers and reinstalled the Nvidia drivers, the PC now seems to be improved and is now running for longer. The first time I started the PC I managed to install Origin and i ran Geforce Now for a while and tried to load a game, was in the queue for a while and then it blue screened. Have just restarted and done some browsing and typed this message without a blue screen (then I opened notepad and it blue screened). I now seem to be able to boot into safe mode.

After putting back in the 960 I installed Sysnative and ran it, here is the result - https://www.dropbox.com/sh/z500dg9fowrckmk/AABqy5ygQdfH5EYGAYIdU0eGa?dl=0

Let me know if you have any more thoughts but understand I may need to take it to a shop when this is all over.

 

[Firefly_t1000]

Last 3 dumps since changing back to the 960 - https://www.dropbox.com/sh/8aius4pfsyx3r22/AABbS6_41nTD3NFbZg27RtBda?dl=0

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://incorruptibis.htmlpasta.com/

Spoiler

File information:	041220-4156-01 - Copy.dmp (Apr 12 2020 - 11:34:21)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 13 Min(s), and 03 Sec(s)

File information:	041220-4187-01 - Copy.dmp (Apr 12 2020 - 12:02:51)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 27 Min(s), and 59 Sec(s)

File information:	041220-4640-01 - Copy.dmp (Apr 12 2020 - 12:19:27)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	ntkrnlmp.exe (Process: firefox.exe)
Uptime:	0 Day(s), 0 Hour(s), 10 Min(s), and 08 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.