So, every core is showing as idle - meaning running the Idle "process". There is no real work being done at all. Did you generate this dump file when the system was frozen?
edit: I'm heading out for the night but I'll check back later.
I must have misunderstood. I thought you wanted me to use the right ctrl + scroll lock to force the system to crash and create a dump file from that.
Do I wait until the system freezes up and then use the keyboard shortcut?
Edit - the system just froze up and it wouldn't work as the keyboard is completely unresponsive. But it did actually bsod this time, seems to be stuck at 0% attempting to collect error info though. I'll leave it for a bit and see if it starts responding at all.
After the new Windows installation there were multiple BSOD and multiple unexpected shutdowns and restarts.
None of the steps so far were designed to fix BSOD.
The steps were designed to start with a fresh install and have new files for troubleshooting.
The findings are typical of malfunctioning hardware.
Some new or repeat software stress tests of hardware may be performed.
Software stress tests of hardware often fail to identify the malfunctioning hardware.
Plan to swap test components.
1) Run Tuneup plus:
https://www.tenforums.com/attachment...p_plus_log.bat
Batch files for use in BSOD debugging
Post a share link.
2) Make sure that the new startup and recovery system failure settings are maintained throughout the troubleshooting.
3) Create a new restore point:
Create System Restore Point in Windows 10
4) For new BSOD post a new V2 share link into the newest post
5) Record the date and time for all manual power offs for hangs and freezes.
Code:Event[616]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2023-12-08T13:26:06.1630000Z Event ID: 18 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-D3F620N Description: A fatal hardware error has occurred. Reported by component: Processor Core Error Source: Machine Check Exception Error Type: Cache Hierarchy Error Processor APIC ID: 25 The details view of this entry contains further information.
Thanks for the help so far zbook.
Tuneup.log - Google Drive
The crashes seem to be getting more frequent and it is getting harder to run the diagnostics and upload the results but I will keep at it.
- - - Updated - - -
Tuneup2.txt - Google Drive
So far I've had crashes at 5:41, 5:47 and 5:58.
Are there any tests or diagnostics that I should prioritize first from that list of debugging scripts? Or should I try to do them in order?
@Dean1975
Yes, the idea is to use the keyboard shortcut to manually crash the system when a freeze/hang occurs.
I'm assuming the keyboard shortcut didn't work. It's certainly possible for a system to become so frozen that it won't respond to a USB keyboard. However, I see your motherboard has a PS/2 port for a mouse or keyboard and PS/2 keyboards have extremely high priority. They are much more likely to work during a system hang. Do you have access to a PS/2 keyboard? If not you or a friend, repair shops often have old used PS/2 keyboards they'll sell pretty cheap. They can be good to have when trying to diagnose freezing/hanging problems.
1. System Information.nfo - Google Drive
2. Systeminfo.txt - Google Drive
3. Get-ComputerInfo.txt - Google Drive
- - - Updated - - -
The keyboard shortcut didn't work when the system crashed as both the mouse and keyboard become completely unresponsive. I don't have access to a ps/2 keyboard, I live in a small rural town with no local repair shops and most of my friends use laptops or tablets. I could possibly buy a ps/2 keyboard on amazon or something if they are cheap. Would one of those usb to ps/2 adapters work with my current keyboard?
i'm still saying swop out the PSU and see ...
"testing software" doesn't always pick up hardware issues
take it or leave it
I'm almost to the point of swapping out the whole systemI'm not sure if I have an extra psu packed away. I'd have to do some rummaging through my box of old parts. I do have an old 980 gpu that I can swap in and test though.
- - - Updated - - -
So out of the previous half dozen crashes this morning I was able to manually crash the system once. However, at the bsod it got stuck at 0% when collecting info, I left it sit for almost 30 minutes and there was no progress so I did a hard reset. So I don't know if this memory dump file will contain anything useful but here it is.
MEMORY.zip - Google Drive
If the adapter isn't purple, there's no real way to know if a USB to PS/2 port adapter will work with a keyboard except to try it. I'd try it if you already have an adapter (even if it's green) but I wouldn't bother buying one or a new PS/2 keyboard.
The latest MEMORY.DMP file linked is the manual crash dump from before. The C:\Windows\MEMORY.DMP gets overwritten with each BSOD, assuming dump file creation is successful. So, it doesn't sound like it's in a state when a freeze occurs that it can get input from a keyboard connected via USB.
I swapped out the 850W psu from the problem pc at 9:15 with a working one from my old parts backup system. Both psu's are seasonic so I didn't even need to change cables. System crashed again at 9:20 so it doesn't look like the psu is faulty.
I have installed the 850W psu into the backup system and will run it for a while just to confirm that it is working fine.
Now, since the last crash/freeze-up I cannot get back into the OS on the problem system. At the login screen when I enter in my pin code I am greeted by the following message "This sign in option is disabled because of failed sign-in attempts or repeated shutdowns. Use a different sign-in option, or keep your device powered on for at least 2 hours and then try again."
Since I started testing things this morning around 4 hours ago I have recorded 12 crashes/freeze-ups. A few days ago I was getting one or two per day, so things are definitely getting worse.
Any guesses on what component is causing these crashes? Mobo perhaps? CPU? I have done two separate memtest runs and they found zero issues with the ram. Before the OS reinstall samsung magician showed no issues with either of the 970 evo drives.
I do have an old gtx 980 gpu that I will install and test with. And I guess I can swap cpu's as well. My old parts backup system has a ryzen 3700x and a Asus x470 strix gaming mobo. It's such a royal pain in the ass when shit goes wrong with a hard tubed watercooled system.
- - - Updated - - -
It would appear that my 5950X is dying a slow death. I took the cpu from the main watercooled system and put it in my backup system and had 5 freeze-up/restarts within 30 minutes.
When all these issues started the thought of a cpu dying had not even crossed my mind. I was convinced that it was a software or driver issue. If I didn't have this backup system to test parts in who knows how long it would have taken to figure it out.
I always save my email receipts and this cpu was purchased in May 2021 so its only two and a half years old. I'm not very impressed at the moment, especially since I paid $1100 cdn for it. I've built at least a half dozen systems over the years going all the way back to athlon xp 2500 and up until now never had a cpu fail on me.
Does anyone have experience dealing with AMD warranty claims? I do still have the original box, receipt etc so I guess its time to contact AMD and start a rma or warranty claim.
Thanks to zbook, cwsink and 3nd for their help.
Quote