Anyone else experiencing issues with these combinations of equipment. I replaced my EVGA GTX 1050 in which I thought was causing the issue because it caused a BSOD in both of my machines. I got two cheap EVGA GT 710's to test and one of them still gives me BSOD on the B450 Gaming K4 (Ryzen 7 2700x) MB my AB350 Pro4 (Ryzen 5 1600x) doesn't give me a BSOD. Both have the exact type G.Skill Flare X memory 16 GB (2x8).

Hard to tell with the information provided. I assume this happens when boinc loads and Seti is running? Do you know if thermals are okay in the computer?

Besides that, I would also suggest downloading bluescreenview, which will give you a log of what error code triggered the bsod. Let us know what code appears and we may be able to help.

---

Seti@home classic: 1,456 results, 1.613 years CPU time

Blame the memory cards perhaps, because on older motherboards, those cards and any graphics cards are quite tightly linked because of the MB itself.

Therefore you need the correct type of memory cards, seating, and also the slot which it should fit into.

need more info.

what is the error code from the BSOD? the problem is likely not GPU related at all. could be system memory or some software problem. can literally be anything.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

What rating of power supply are you using and does it have a single or dual 12V rail?

Cheers.

Looks like a couple of AMD cpus on those ASRock MB's. And been crunching for a while, couple 300,000 total credits systems.
Also running NVIDIA driver 4.41 or so. Flaky drivers?

Tom

---

A proud member of the OFA (Old Farts Association).

seems to fail with every update I download from EVGA. Might be the drivers.

Seems to be a different code each time.

What rating of power supply are you using and does it have a single or dual 12V rail?

Cheers.

- 1 x 24 pin ATX Power Connector
- 1 x 8 pin 12V Power Connector

What rating of power supply are you using and does it have a single or dual 12V rail?

Cheers.

- 1 x 24 pin ATX Power Connector
- 1 x 8 pin 12V Power Connector

that's not what he's asking. every power supply has those connectors.

hes asking for:
1. the power rating of the power supply, 500W, 600W, etc.
2. the internal makeup of the 12V rail inside the power supply. Some PSUs have a single 12V rail, some have multiple.

if you know the brand and model number of the power supply we can just google the specs.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

Hard to tell with the information provided. I assume this happens when boinc loads and Seti is running? Do you know if thermals are okay in the computer?

Besides that, I would also suggest downloading bluescreenview, which will give you a log of what error code triggered the bsod. Let us know what code appears and we may be able to help.

I googled bluescreenview I get two different sites. Link please? Thanks!

What rating of power supply are you using and does it have a single or dual 12V rail?

Cheers.

- 1 x 24 pin ATX Power Connector
- 1 x 8 pin 12V Power Connector

He means the rated wattage. It should be on the PSU marking how many amps or watts each rail can provide.

Have you run memtest already? Memory is usually the top culprit for frequent BSOD issues besides inadequate PSU. Just grab a USB and flash it with https://www.memtest86.com/. Run the default test for a couple of hours. It won't hurt to rule out faulty memory first. Having the same model doesn't really mean much. Last time I had random BSOD it's just one stuck bit in memory and that kit worked well for a year or so before the issues happened.

---

- 1 x 24 pin ATX Power Connector
- 1 x 8 pin 12V Power Connector

That is not what I asked for by a long way and not helpful in any way. :-)

Your power supply will have a ratings label on the side (listing max load, the individual voltage rails and their spec's) and what is on that is what is required. ;-)

Cheers.

need more info.

what is the error code from the BSOD? the problem is likely not GPU related at all. could be system memory or some software problem. can literally be anything.

122119-7406-01.dmp 12/21/2019 8:37:46 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a fffffb8c`eb0c3c28 00000000`000000ff 00000000`00000000 fffff800`591c3202 ntoskrnl.exe ntoskrnl.exe+1c14e0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.535 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\Windows\Minidump\122119-7406-01.dmp 16 15 18362 857,572 12/21/2019 8:38:39 AM

121619-8906-01.dmp 12/16/2019 5:03:18 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff801`180215fe ffffffff`ffffffff 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+1c14e0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.535 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\Windows\Minidump\121619-8906-01.dmp 16 15 18362 851,284 12/16/2019 5:04:17 PM

120919-7921-01.dmp 12/9/2019 4:18:21 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff898`f402ac21 00000000`00000000 ffffffff`ffffffff win32kfull.sys win32kfull.sys+2ac21 Full/Desktop Win32k Kernel Driver Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.535 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\Windows\Minidump\120919-7921-01.dmp 16 15 18362 867,244 12/9/2019 4:19:36 PM

120919-7546-01.dmp 12/9/2019 11:29:37 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffff801`26ca54d0 00000000`00000002 00000000`00000008 fffff801`26ca54d0 ntoskrnl.exe ntoskrnl.exe+1c14e0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.535 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\Windows\Minidump\120919-7546-01.dmp 16 15 18362 889,020 12/9/2019 11:30:51 AM

120819-7453-01.dmp 12/8/2019 9:45:44 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff807`3f43c8a4 00000000`00000000 ffffffff`ffffffff ntoskrnl.exe ntoskrnl.exe+1c14e0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.535 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\Windows\Minidump\120819-7453-01.dmp 16 15 18362 1,027,188 12/8/2019 9:46:32 PM

What rating of power supply are you using and does it have a single or dual 12V rail?

Cheers.

- 1 x 24 pin ATX Power Connector
- 1 x 8 pin 12V Power Connector

that's not what he's asking. every power supply has those connectors.

hes asking for:
1. the power rating of the power supply, 500W, 600W, etc.
2. the internal makeup of the 12V rail inside the power supply. Some PSUs have a single 12V rail, some have multiple.

if you know the brand and model number of the power supply we can just google the specs.

Ultra X4 800 Watts I think.

What rating of power supply are you using and does it have a single or dual 12V rail?

Cheers.

- 1 x 24 pin ATX Power Connector
- 1 x 8 pin 12V Power Connector

He means the rated wattage. It should be on the PSU marking how many amps or watts each rail can provide.

Have you run memtest already? Memory is usually the top culprit for frequent BSOD issues besides inadequate PSU. Just grab a USB and flash it with https://www.memtest86.com/. Run the default test for a couple of hours. It won't hurt to rule out faulty memory first. Having the same model doesn't really mean much. Last time I had random BSOD it's just one stuck bit in memory and that kit worked well for a year or so before the issues happened.

Memtest Yes nothing wrong with the memory. Several times.

need more info.

what is the error code from the BSOD? the problem is likely not GPU related at all. could be system memory or some software problem. can literally be anything.

122119-7406-01.dmp 12/21/2019 8:37:46 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a fffffb8c`eb0c3c28 00000000`000000ff 00000000`00000000 fffff800`591c3202 ntoskrnl.exe ntoskrnl.exe+1c14e0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.535 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\Windows\Minidump\122119-7406-01.dmp 16 15 18362 857,572 12/21/2019 8:38:39 AM

121619-8906-01.dmp 12/16/2019 5:03:18 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff801`180215fe ffffffff`ffffffff 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+1c14e0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.535 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\Windows\Minidump\121619-8906-01.dmp 16 15 18362 851,284 12/16/2019 5:04:17 PM

120919-7921-01.dmp 12/9/2019 4:18:21 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff898`f402ac21 00000000`00000000 ffffffff`ffffffff win32kfull.sys win32kfull.sys+2ac21 Full/Desktop Win32k Kernel Driver Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.535 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\Windows\Minidump\120919-7921-01.dmp 16 15 18362 867,244 12/9/2019 4:19:36 PM

120919-7546-01.dmp 12/9/2019 11:29:37 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffff801`26ca54d0 00000000`00000002 00000000`00000008 fffff801`26ca54d0 ntoskrnl.exe ntoskrnl.exe+1c14e0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.535 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\Windows\Minidump\120919-7546-01.dmp 16 15 18362 889,020 12/9/2019 11:30:51 AM

120819-7453-01.dmp 12/8/2019 9:45:44 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff807`3f43c8a4 00000000`00000000 ffffffff`ffffffff ntoskrnl.exe ntoskrnl.exe+1c14e0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.535 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\Windows\Minidump\120819-7453-01.dmp 16 15 18362 1,027,188 12/8/2019 9:46:32 PM

my guess is OS corruption or bad hard drive.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

my guess is OS corruption or bad hard drive.

A dual (or multi) 12V rail power supply that is only being loaded on one 12V rail will also produce similar results if all that is being powered through the motherboard rail only (I've seen that happen all too often over the years and causing the same problems). ;-)

Cheers.

my guess is OS corruption or bad hard drive.

Such issue can be caused by bit flips as well, which means CPU, memory, MB or PSU undervolting are all still possible. I definitely had KMODE_EXCEPTION_NOT_HANDLED and IRQL_NOT_LESS_OR_EQUAL when my memory had a bit stuck and never had it after replacing that stick.

Since OP has Windows 10, analyzing dumps are really simple. Go to Windows Store and search "WinDbg Preview". Once installed, load your dump through File -> open dump file. It will download the correct symbols and do an initial analyze. Then in the command window, click that "run !analyze -v". It will show you whole bunch of detailed information.

If it's the fault of a specific driver, the .sys will always show up at the end of the report in module/image name consistently. I used this to find the faulty creative audio drivers previously that caused BSOD for me like once a day. If it's not always same image/module name, then you can try looking at the stack and registers to see if you can find any pattern, if you have enough dumps. That's kinda hard though.

Edited: Missed the part you've already run memtest. :-( Then your CPU/memory is likely fine. I pile on the other people that's suspecting your PSU is at fault. MB is also possible, but I honestly don't know how one can possibly verify that without another PSU. If your PSU ratings are similar and both are supposed to be able to handle the load, swapping PSU might give you some idea.

---

my guess is OS corruption or bad hard drive.

Such issue can be caused by bit flips as well, which means CPU, memory, MB or PSU undervolting are all still possible. I definitely had KMODE_EXCEPTION_NOT_HANDLED and IRQL_NOT_LESS_OR_EQUAL when my memory had a bit stuck and never had it after replacing that stick.

Since OP has Windows 10, analyzing dumps are really simple. Go to Windows Store and search "WinDbg Preview". Once installed, load your dump through File -> open dump file. It will download the correct symbols and do an initial analyze. Then in the command window, click that "run !analyze -v". It will show you whole bunch of detailed information.

If it's the fault of a specific driver, the .sys will always show up at the end of the report in module/image name consistently. I used this to find the faulty creative audio drivers previously that caused BSOD for me like once a day. If it's not always same image/module name, then you can try looking at the stack and registers to see if you can find any pattern, if you have enough dumps. That's kinda hard though.

Edited: Missed the part you've already run memtest. :-( Then your CPU/memory is likely fine. I pile on the other people that's suspecting your PSU is at fault. MB is also possible, but I honestly don't know how one can possibly verify that without another PSU. If your PSU ratings are similar and both are supposed to be able to handle the load, swapping PSU might give you some idea.

Only thing different in the two machines is the PSU so that sounds like a good assumption to me too. I will replace the PSU if I don't figure it out its doing it for any other reason. Thanks! I'll get the app today.