PC crashing with BSOD

Hi all,

 

I've noticed the last week my PC crashing multiple times a day.  I've attached my Speccy and Event Viewer log below:

 

https://imgur.com/a/pWQkLkY

 

I've also attached a dump file:

 

https://www.mediafire.com/file/se8hc17u0tk8ce9/Minidump.rar/file

 

I have looked at the Windows Update logs last update was on 02/09 and the crashes started happening more frequently from 03/09 which coincided with me moving the PC from my table top to the floor. Another thing I may be doing differently is having the DP Cable from the monitor going straight into the motherboard as opposed to the GPU (it's not quite long enough to reach now the PC on the floor).

 

Yesterday I updated my motherboard BIOS to the most up to date version but the crashes have continued since (10+ in the last 24 hours).

 

Can anyone please advise what may be causing this or help with troubleshooting? I can supply more information if required.

 

Greatly appreciated, computer problems are frustrating!

 

Thank you

 

 

Hello and welcome for the forum!

 

It would help if you follow the BSOD posting instructions so that we get all the relevant troubleshooting logs, dumps and data.

 

Firstly, plugging the monitor into the motherboard will cause it to use the iGPU (if you have one) in the CPU and graphics performance will be poor. The GPU will then be unused.

 

Of the five dumps, three are 0x101 CLOCK_WATCHDOG_TIMEOUT which can only be debugged with the kernel dump in the file C:\Windows\Memory.dmp. Unfortunately that file only contains the most recent kernel dump and that's not a 0x101 dump. Next time you get a 0x101 CLOCK_WATCHDOG_TIMEOUT BSOD please upload the file C:\Windows\Memory.dmp immediately (before another BSOD overwrites it.

 

One of the dumps is a 0x133 DPC_WATCHDOG_VIOLATION, which means that a DPC ran for longer than allowed. Unfortunately it's not clear from this dump what DPC that was.

 

The fifth dump is (I suspect) the charm, and explains the 0x133 dump too. This dump is a 0x12B FAULTY_HARDWARE_CORRUPTED_PAGE and as you might expect it indicates a hard RAM failure. I'm not certain that this explains the 0x101 bugchecks but one thing at a time.

 

The first thing I'd suggest, since you have recently moved the PC, is that you remove and re-seat the RAM cards. If that doesn't help, then on a different PC download Memtest86 (Free) and use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Then boot that USB drive on your failing PC. Memtest86 will start running as soon as it boots, if no errors have been found after the four iterations that the free version does, then restart Memtest86 and do another four iterations.

 

Let us know how that goes.

Edited by ubuysa, 07 September 2023 - 08:47 AM.

Hi ubuysa,

 

Thank you very much for your reply.

 

I have already moved the PC tower back to the tabletop and plugged the DP cable into the GPU and ensured the RAM kits are securely in place.

 

I have noted what you have said about the Memory.dmp and will try my best to capture when the 0x101 CLOCK_WATCHDOG_TIMEOUT BSOD appears.

 

Finally I have already downloaded the Memtest86 and will proceed as instructed when necessary. 

Edited by hamluis, 08 September 2023 - 04:47 PM.

Hi, Welcome to BC.
 
There is no need to use the Quote All window. Thanks.  
The Posting Instructions are here and you need to open the URL and follow please : https://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/ /11
it is a 3 step process to attach.  Note : Do not .RAR the file.  No forum and nobody unless know the person should use a .RAR, thanks.
 
Please do Speccy Report as a URL : Please Post a "link" of Speccy Report.
Please install Speccy Free : https://m.majorgeeks.com/files/details/speccy.html
Use Custom Install
  At the Top Left Corner of Speccy --> Click File and then Click Publish Snapshot Report, a window will popup and Click YES. --> Another popup will appear and then Click "Copy To Clipboard" then Paste that "link" to your next reply in your thread.


As per not following/or missed the Posting Instructions what you have provided with the Dumps would guess be fine but to everything else to look at root causes is missing.
 
If do not know this is your M/B Support Page : https://www.asus.com/motherboards-components/motherboards/tuf-gaming/tuf-gaming-b650-plus-wifi/helpdesk_knowledge/?model2Name=TUF-GAMING-B650-PLUS-WIFI
Current BIOS Version is : 1654  Released : 2023/08/29    If not running this version would suggest do so.   May want to Download your Manual.
"1. Update AGESA version to Combo AM5 PI 1.0.0.7c
2. Improve system performance
Before running the USB BIOS Flashback tool, please rename the BIOS file (TGB650PW.CAP) using BIOSRenamer."
 
NOTE : Interesting on your Driver Page there is a Note for Updating Chipset : NOTICE:  Due to the different structure for drivers, suggest you remove the old driver first before install this version driver.
So in this case it maybe best to run ASUS supplied rather than MS as no idea what it or how it updates the Chipset.
 
Note : a fairly new Lan Driver : 2022/09/13 if Armoury Crate has not been supplying the Updates or you have missed looking for them.
 
Mod Edit:  Merged posts - Hamluis.

Edited by hamluis, 08 September 2023 - 04:49 PM.

Hi all,

 

I just want to say since I've moved the PC tower back onto the table top and re-plugged the DP cable into the GPu as opposed to the motherboard it appears to have fixed the issue.

 

No crashes in the last 48 hours, not entirely sure why going through the motherboard was causing the crashes.

 

Appreciate all the comments in troubleshooting.

 

Thank you

Since Post was merged the above is still last post on any date.     Should do Post # 4 regardless.