Question Three System BSODs ?

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
Do a web search for 'psu calculator', you'll find several that will help you size the PSU. Most of them calculate the actual power required and then add a 20% overhead. I like to overspec my PSUs, they really are the most important component IMO, so I generally add another 20% minimum.
 
I take the wattage the calculator comes up with, which already has a 20% overhead built in, and then I add on at least another 20% and round up to the next model size. For example, if the calculator say 635W required then I add in another 20% (127W) making a total of 762W. For me, a 750W PSU isn't enough so I would go for an 850W PSU. That's actually what I did with my recent build.
 
In that Sysnative file it appears the the single RAM stick is in slot B2? Can you check that, the motherboard manual (page 10) indicates that a single stick should be in slot A2.
 
ubuysa said:
In that Sysnative file it appears the the single RAM stick is in slot B2? Can you check that, the motherboard manual (page 10) indicates that a single stick should be in slot A2.
Click to expand...
You mean DDR4_2? For the longest time, I've been using two RAM sticks on DDR4_3 and DDR4_1.
 
If it BSODs in Safe Mode then it's almost certainly a hardware problem.

You've tested RAM so I'd use Prime95 to stress test the CPU...
  1. Download Prime95 and a CPU temperature monitor (CoreTemp will do).
  2. Keep the temperature monitor running all the time you run Prime95. Your CPU will get hot!
  3. Run each of the three Prime95 tests (smallFFTs, largeFFTs, and Blend) one after the other for a minimum of 1 hour per test, 2 hours per test would be better.
  4. If Prime95 generates error messages, if the system crashes/freezes/BSODs, or if your CPU temp reaches 95°C (Tmax for your CPU), then stop Prime95 and let us know what happened.
Note that a properly cooled and stable CPU should be able to run all Prime95 tests pretty much indefinitely.

FYI: The small FFT test stresses the CPU more than RAM. The large FFT test stresses RAM more than the CPU. The Blend test is a mixture of the two.

I still think the PSU might be the cause....
 
  • Like
Reactions: DevanDrake99
ubuysa said:
If it BSODs in Safe Mode then it's almost certainly a hardware problem.

You've tested RAM so I'd use Prime95 to stress test the CPU...
  1. Download Prime95 and a CPU temperature monitor (CoreTemp will do).
  2. Keep the temperature monitor running all the time you run Prime95. Your CPU will get hot!
  3. Run each of the three Prime95 tests (smallFFTs, largeFFTs, and Blend) one after the other for a minimum of 1 hour per test, 2 hours per test would be better.
  4. If Prime95 generates error messages, if the system crashes/freezes/BSODs, or if your CPU temp reaches 95°C (Tmax for your CPU), then stop Prime95 and let us know what happened.
Note that a properly cooled and stable CPU should be able to run all Prime95 tests pretty much indefinitely.

FYI: The small FFT test stresses the CPU more than RAM. The large FFT test stresses RAM more than the CPU. The Blend test is a mixture of the two.

I still think the PSU might be the cause....
Click to expand...
I encountered a fatal error in one of the threads.

[Thu Dec 19 20:25:33 2024]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected running 80K FFT size, consult stress.txt file.
FATAL ERROR: Rounding was 6.368154947e+16, expected less than 0.4
Hardware failure detected running 80K FFT size, consult stress.txt file.
 
Did you ever get the PSU checked? We had reasons to suspect the PSU earlier and nothing we've seen since changes that. It would be a shame to replace the CPU and find it was the PSU all along....
 
I think I found the problem. After formatting the HDD previously used as a system drive as I had two system drives before according to my earliest Sysnative zip file, my PC stopped blue screening. I'm currently running my PC and idling outside of safe mode for over a day and 12 hours straight, and hasn't encountered a single blue screen.
 
DevanDrake99 said:
I think I found the problem. After formatting the HDD previously used as a system drive as I had two system drives before according to my earliest Sysnative zip file, my PC stopped blue screening. I'm currently running my PC and idling outside of safe mode for over a day and 12 hours straight, and hasn't encountered a single blue screen.
Click to expand...
Update. The system has been running for nearly 72 hours now, and no BSOD.
 
  • Like
Reactions: ubuysa
DevanDrake99 said:
Here are the new minidumps.

https://www.mediafire.com/file/xva7lkrdlya5lcc/121024-48343-01.dmp/file

https://www.mediafire.com/file/audlplvzj996b75/121024-70046-01.dmp/file

https://www.mediafire.com/file/jtyecxdegd5vzon/121224-57218-01.dmp/file

https://www.mediafire.com/file/shwvajvjlc1nrv5/121224-80781-01.dmp/file

https://www.mediafire.com/file/b378o23py11mwzj/121324-56000-01.dmp/file
Click to expand...
you have two copies of amdryzenmasterdriver.sys running from two different directories. Your system will be unstable until you remove one. (or both)
AMDRyzenMasterDriver Thu May 12 23:01:00 2022

AMDRyzenMasterDriver_fffff8031dcf0000 Tue Aug 1 00:37:54 2023

windows will load the second copy at a offset and will add a underscore and offset to the name.

you can download and run Microsoft autoruns64.exe to find and delete the second copy. delete the copy from may 12 2022
 
  • Like
Reactions: DevanDrake99
just looked at your most current minidump. Looked like windows was compressing some memory and got an access violation. tried to compress a invalid address (0)

You have some old drivers installed that would not know about memory compression and might modify compressed memory.
I would consider removing some of your old drivers.

might look at:
ovpn-dco.sys (invalid timestamp and build number)
PxHlpa64.sys Tue Apr 24 10:26:29 2012 old sonic solution driver
vbaudio_cable64_win7.sys Wed Aug 13 23:15:25 2014

-------
maybe the other bugchecks will show a direct corruption and name a driver. Will take a few minutes to check.

second bugcheck was also wof.sys trying to compress a invalid address. (0 and -1)
wof.sys is windows overlay filter driver used to run compress files directly.
------
third bugcheck also in wof.sys compression
--------------
the oldest bugcheck was the most interesting
0xc0000409 - The system detected an overrun of a stack-based buffer
some driver is corrupting your memory data structures. I would suspect just a bug where they free a memory address twice.
looks like some usb human interface device using intrl usb interface extensions

mindumps do not show hid devices, you would have to provide a kernel memory dump. I would be looking for old usb devices and update firmware of usb devices like mice, also any special usb device drivers related to your usb devices. for example usb drives sometimes have old drivers that get loaded from the drive and cause corruption.

change your memory dump to kernel and the memory.dmp will have the proper debug info included.

you could also enable verifier testing and your system will bugcheck when a driver does something wrong. it will force the system to bugcheck much faster at the time of corruption rather than later when corrupted data is cleaned up or deleted at system idle time. Be sure you know how to turn off verifier via going into safe mode and running
verifier /reset
sometimes with old driver you get a bugcheck during the boot process.
I would assume this is the root cause of all of the bugchecks.

note: looks like you have Microsoft generic usb drivers installed. Some system might require your custom mother board cpu chipset drivers to be installed. you might install
AMD Chipset Driver from your motherboard vendor to see if it helps.
you might remove HidGuardian. I use a usb splitter that has a on/off button for each device I want to use.
 
Last edited:
  • Like
Reactions: DevanDrake99
johnbl said:
just looked at your most current minidump. Looked like windows was compressing some memory and got an access violation. tried to compress a invalid address (0)

You have some old drivers installed that would not know about memory compression and might modify compressed memory.
I would consider removing some of your old drivers.

might look at:
ovpn-dco.sys (invalid timestamp and build number)
PxHlpa64.sys Tue Apr 24 10:26:29 2012 old sonic solution driver
vbaudio_cable64_win7.sys Wed Aug 13 23:15:25 2014

-------
maybe the other bugchecks will show a direct corruption and name a driver. Will take a few minutes to check.

second bugcheck was also wof.sys trying to compress a invalid address. (0 and -1)
wof.sys is windows overlay filter driver used to run compress files directly.
------
third bugcheck also in wof.sys compression
--------------
the oldest bugcheck was the most interesting
0xc0000409 - The system detected an overrun of a stack-based buffer
some driver is corrupting your memory data structures. I would suspect just a bug where they free a memory address twice.
looks like some usb human interface device using intrl usb interface extensions

mindumps do not show hid devices, you would have to provide a kernel memory dump. I would be looking for old usb devices and update firmware of usb devices like mice, also any special usb device drivers related to your usb devices. for example usb drives sometimes have old drivers that get loaded from the drive and cause corruption.

change your memory dump to kernel and the memory.dmp will have the proper debug info included.

you could also enable verifier testing and your system will bugcheck when a driver does something wrong. it will force the system to bugcheck much faster at the time of corruption rather than later when corrupted data is cleaned up or deleted at system idle time. Be sure you know how to turn off verifier via going into safe mode and running
verifier /reset
sometimes with old driver you get a bugcheck during the boot process.
I would assume this is the root cause of all of the bugchecks.

note: looks like you have Microsoft generic usb drivers installed. Some system might require your custom mother board cpu chipset drivers to be installed. you might install
AMD Chipset Driver from your motherboard vendor to see if it helps.
you might remove HidGuardian. I use a usb splitter that has a on/off button for each device I want to use.
Click to expand...
This is pretty complex, but I can try that.
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom