PC rebooting itself

youradds

Bronze Level Poster
Hi,

I have a new build, with the spec:

Case CORSAIR 4000D AIRFLOW TEMPERED GLASS GAMING CASE
Processor (CPU) AMD Ryzen 9 7900 12 Core CPU (4.0GHz-5.4GHz/76MB CACHE/AM5)
Motherboard ASUS® PRIME B650-PLUS (AM5, DDR5, PCIe 4.0)
Memory (RAM) 32GB Corsair VENGEANCE DDR5 5200MHz (2 x 16GB)
Graphics Card INTEGRATED GRAPHICS ACCELERATOR (GPU) Graphics Card Support Bracket
NONE (BRACKET INCLUDED AS STANDARD ON 4070 Ti / RX 7700 XT AND ABOVE)
1st M.2 SSD Drive 512GB SOLIDIGM P44 PRO GEN 4 M.2 NVMe PCIe SSD (up to 7000MB/sR, 4700MB/sW)
Memory Card Reader USB 3.0 EXTERNAL SD/MICRO SD CARD READER
Power Supply CORSAIR 850W RMx SERIES™ MODULAR 80 PLUS® GOLD, ULTRA QUIET
Processor Cooling CORSAIR H100x RGB ELITE HIGH PERFORMANCE CPU COOLER
Thermal Paste STANDARD THERMAL PASTE FOR SUFFICIENT COOLING
Sound Card ONBOARD 6 CHANNEL (5.1) HIGH DEF AUDIO (AS STANDARD)
Network Card ONBOARD 2.5Gbe LAN PORT
Wireless Network Card WIRELESS INTEL® Wi-Fi 6E AX210 2,400Mbps/5GHz, 300Mbps/2.4GHz PCI-E CARD + BT 5.0
USB/Thunderbolt Options MIN. 2 x USB 3.0 & 2 x USB 2.0 PORTS @ BACK PANEL + MIN. 2 FRONT PORTS
Operating System Windows 11 Home 64 Bit - inc. Single Licence

It has been running really well - except for 2 times where it has randomly done a black screen, and a forced reboot. I intentionally went for an 850w PSU as I have moved my Radeon RX 580 GFX card, as I need more screens for work.

I have 2 external SSDs + an extra 4tb m.2 drive.

Each time its done the reboot, I haven't been doing loads (minimal load, with no heavy programs running)

Could anyone please suggest where I could look next? Its only happened 2 times since having the machine - but its bloody annoying (especially if I'm in the middle of a job :/

FYI, the spec shows: "Maximum Required Power 132W" - so even with my extra GFX card it wouldn't come to anywhere near the 850w
"

Cheers

Andy
 

FigmentOfYourImagination

Gold Level Poster
Whilst it's not a BSOD, there should (hopefully) still be useful logs etc around. have a read through this, look in the areas it mentions and upload anything to cloud and link here (make sure to make any file viewings to public)

 

youradds

Bronze Level Poster
Thanks @FigmentOfYourImagination - is this it? https://drive.google.com/file/d/1wS2L2A1Sp4utD19_i5GmTFDXQstNCTWT/view?usp=sharing . I tried using the SysnativeFileCollections thing, but it seems to hang (even after running for 20-30 mins)

I did notice this in the Event Viewer which is a bit concerning:

1726566281113.png


I also saw about running sfc, so I've done:


sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

I guess lets see if it happens again!
 
Last edited:

FigmentOfYourImagination

Gold Level Poster
I'll leave deciphering anything in those files to someone more experienced in things like this. However, a brief look at the application logs and the majority of the red (most serious usually) errors is the DropBox service. Assuming you have the system set up to sync to Dropbox, I would try disabling that and see if it makes a difference...probably not but worth a shot
 

FigmentOfYourImagination

Gold Level Poster
Just had a quick look through the system logs and there is a Whea Logger event at 10:07 this morning. It is indicating a fatal hardware error and says the component is the memory. I'm not a diagnostic person but I'd be looking at the RAM on the back of that.

Go to: https://www.memtest86.com/

Install the tool onto a flash drive and reboot. It will then run. It needs the full 4 iterations (usually takes a few hours). While it's not 100% infallible, it usually points out any RAM errors
 

youradds

Bronze Level Poster
Just had a quick look through the system logs and there is a Whea Logger event at 10:07 this morning. It is indicating a fatal hardware error and says the component is the memory. I'm not a diagnostic person but I'd be looking at the RAM on the back of that.

Go to: https://www.memtest86.com/

Install the tool onto a flash drive and reboot. It will then run. It needs the full 4 iterations (usually takes a few hours). While it's not 100% infallible, it usually points out any RAM errors
Thanks - I'll give that a go :)
 

ubuysa

The BSOD Doctor
It's a good idea to run Memtest86, please run it twice however, so you do 8 iterations of the 13 different tests.

However, the system log also shows that you have had a BSOD today...
Code:
Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          17/09/2024 12:07:25
Event ID:      1001
Task Category: None
Level:         Error
Keywords:    
User:          SYSTEM
Computer:      AndyNewPC
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff860e505d5028, 0x00000000b4800800, 0x00000000060c0859). A dump was saved in: C:\windows\MEMORY.DMP. Report Id: f5617add-bc86-4c70-8900-846ae8bf5d3c.
The 0x124 bugcheck is a WHEA_UNCORRECTABLE_ERROR, the first argument (0) indicates a machine check exception. This will be the BSOD associated with the WHEA error pointed out earlier. I'd like to ee that dump but rather than just upload that can you please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

In addition, your system log contains huge numbers (hundreds!) of error messages for your AX210 wireless card...
Code:
Log Name:      System
Source:        Netwtw14
Date:          11/09/2024 16:20:41
Event ID:      5005
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      AndyNewPC
Description:
Intel(R) Wi-Fi 6E AX210 160MHz : Has encountered an internal error and has failed.
If you're using that wireless card then this could well be the root cause. I'll know more when I see the Sysnative output.
 

youradds

Bronze Level Poster
Thanks for the reply. I've run Memtest86 once (took 2 1/2 hours), and it came back as a pass.


(I tried to upload as an attachment, but I got broken thumbs, and they were lost when saving my post?)


I'll run another one of them later

Here is the Sysnative one (I finally worked out where it was saving the files)


Thank you ;)
 

FigmentOfYourImagination

Gold Level Poster
While we are waiting for Ubuysa to look through the latest logs etc you posted, I'd recommend opening up the case (don't worry about the warranty, PCS have an open-case policy so you can remove things etc) and completely removing the Wi-Fi card (unless you are using it and can't connect a cable of course). Whilst it may be completely unrelated to the issue, my experience tells me it's possible. Back in 2012, I bought a custom PC (not from PCS) with a WI-Fi card and had no end of issues with crashes, BSODs etc....after hours and hours of troubleshooting, I read something about faulty Wi-Fi cards causing issues unrelated to networking...I removed the Wi-Fi card and never had another crash or BSOD
 

youradds

Bronze Level Poster
Thanks. Interestingly I haven't had anything happen since running this:

sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

I use the wireless card for printing - so I'll leave it for the moment and see if it happens again. If it does, I'll d/c it and see if it happens again. Its weird how it happened 3 times yesterday - and hasn't happened once today (or since those 3 times yesterday)
 

ubuysa

The BSOD Doctor
It is possible that SFC fixed the issue, but it's unlikely. I can now see from the Sysnative upload that you're not using the AX210, nor are you using the additional Realtek 8811CU USB WiFi adapter that you have installed. You saaid above that...
I use the wireless card for printing...
....but which wirelsss card do you use?

I agree with @FigmentOfYourImagination that remviong the AX210 to see whether it affects these forced reboots - which it potentially could be. There are no error indications for the USB WiFi card, so try using that instead.

The dump doesn't help much sadly, minidumps only contain the status for the processor that took the bugcheck and in this case that's just for the processor that serviced the machine check exception. HJowever, it did give me a chance to display the loaded modules in the dump and I came across one curiosity that may well be significant; there are two versions of the AMD graphics driver amdkmdag.sys installed, and both are loaded....
Rich (BB code):
7: kd> lmDvmamdkmdag_fffff80201fe0000
Browse full module list
start             end                 module name
fffff802`01fe0000 fffff802`08571000   amdkmdag_fffff80201fe0000   (deferred)          
    Image path: \SystemRoot\System32\DriverStore\FileRepository\u0403811.inf_amd64_52448c34fb47b343\B403843\amdkmdag.sys
    Image name: amdkmdag.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Tue May 28 00:21:31 2024 (6654F95B)
    CheckSum:         0653962F
    ImageSize:        06591000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
7: kd> lmDvmamdkmdag
Browse full module list
start             end                 module name
fffff801`dee60000 fffff801`e5428000   amdkmdag   (deferred)          
    Image path: \SystemRoot\System32\DriverStore\FileRepository\u0399660.inf_amd64_d7fa3539ce499e50\B399655\amdkmdag.sys
    Image name: amdkmdag.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Mon Nov 27 19:02:44 2023 (6564CBB4)
    CheckSum:         065800C8
    ImageSize:        065C8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
You can see from the listing of the two drivers, that they refernce two different versions of amdkmdag.sys (note the differetnt timestamps and the different storage locations) and yet both versions are loaded and thus active at the same time. This is much more likely to be the cause of your black screen that anything else.

It looks as though you may have had an issue when you installed your AMD Radeon RX 580 GFX card and installed two different driver versions for it.

I would now run DDU to remove all traces of the AMD graphics driver and then download and install the latest driver from AMD.
 

FigmentOfYourImagination

Gold Level Poster
I use the wireless card for printing

Sorry, I missed that bit earlier. How is your printer set up? I only ask as wireless printers run through the router. So, for example, I have my main PC in the living room which is wired to the router...I then have a wireless printer in the bedroom which connects wirelessly to the router, which then feeds the signal to the PC via the internet cable. If your PC also has a wired internet connection, then the Wi-Fi card shouldn't be needed.
 

ubuysa

The BSOD Doctor
Sorry, I missed that bit earlier. How is your printer set up? I only ask as wireless printers run through the router. So, for example, I have my main PC in the living room which is wired to the router...I then have a wireless printer in the bedroom which connects wirelessly to the router, which then feeds the signal to the PC via the internet cable. If your PC also has a wired internet connection, then the Wi-Fi card shouldn't be needed.
Very true. (y)
 

TonyCarter

VALUED CONTRIBUTOR
Sorry, I missed that bit earlier. How is your printer set up? I only ask as wireless printers run through the router. So, for example, I have my main PC in the living room which is wired to the router...I then have a wireless printer in the bedroom which connects wirelessly to the router, which then feeds the signal to the PC via the internet cable. If your PC also has a wired internet connection, then the Wi-Fi card shouldn't be needed.
Modern (i.e. post 2014) may have WiFi Direct, which means you can print directly over an ad-hoc wifi connection (from phones, laptops, cameras, PCs, etc.).





 

youradds

Bronze Level Poster
It is possible that SFC fixed the issue, but it's unlikely. I can now see from the Sysnative upload that you're not using the AX210, nor are you using the additional Realtek 8811CU USB WiFi adapter that you have installed. You saaid above that...

....but which wirelsss card do you use?

I agree with @FigmentOfYourImagination that remviong the AX210 to see whether it affects these forced reboots - which it potentially could be. There are no error indications for the USB WiFi card, so try using that instead.

The dump doesn't help much sadly, minidumps only contain the status for the processor that took the bugcheck and in this case that's just for the processor that serviced the machine check exception. HJowever, it did give me a chance to display the loaded modules in the dump and I came across one curiosity that may well be significant; there are two versions of the AMD graphics driver amdkmdag.sys installed, and both are loaded....
Rich (BB code):
7: kd> lmDvmamdkmdag_fffff80201fe0000
Browse full module list
start             end                 module name
fffff802`01fe0000 fffff802`08571000   amdkmdag_fffff80201fe0000   (deferred)         
    Image path: \SystemRoot\System32\DriverStore\FileRepository\u0403811.inf_amd64_52448c34fb47b343\B403843\amdkmdag.sys
    Image name: amdkmdag.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Tue May 28 00:21:31 2024 (6654F95B)
    CheckSum:         0653962F
    ImageSize:        06591000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
7: kd> lmDvmamdkmdag
Browse full module list
start             end                 module name
fffff801`dee60000 fffff801`e5428000   amdkmdag   (deferred)         
    Image path: \SystemRoot\System32\DriverStore\FileRepository\u0399660.inf_amd64_d7fa3539ce499e50\B399655\amdkmdag.sys
    Image name: amdkmdag.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Mon Nov 27 19:02:44 2023 (6564CBB4)
    CheckSum:         065800C8
    ImageSize:        065C8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
You can see from the listing of the two drivers, that they refernce two different versions of amdkmdag.sys (note the differetnt timestamps and the different storage locations) and yet both versions are loaded and thus active at the same time. This is much more likely to be the cause of your black screen that anything else.

It looks as though you may have had an issue when you installed your AMD Radeon RX 580 GFX card and installed two different driver versions for it.

I would now run DDU to remove all traces of the AMD graphics driver and then download and install the latest driver from AMD.
Thanks for the details. I tried running DDU. It removed the GFX drivers, and went down to 1 screen. I then downloaded https://www.amd.com/en/support/download/drivers.html and run that - but it gave an error:

Screenshot 2024-09-18 110917.png

After that, when I rebooted it went into a meltdown mode, and wouldn't even get my into safe mode. I ended up having to do a restore point recovery , which fortunatly got me into the machine - but I think its still got the duplicatd drivers on. I'm scared to try it again now :/
 

youradds

Bronze Level Poster
Sorry, I missed that bit earlier. How is your printer set up? I only ask as wireless printers run through the router. So, for example, I have my main PC in the living room which is wired to the router...I then have a wireless printer in the bedroom which connects wirelessly to the router, which then feeds the signal to the PC via the internet cable. If your PC also has a wired internet connection, then the Wi-Fi card shouldn't be needed.

I have a brother HL-L8260CDW. It doesn't have any cables in. I have it set up on my deco mesh, which requires me to be connected the deco network before it'll find it on my PC. My PC is connected via LAN, so maybe I need to reconfigure the printer to use the main routers network directly instead (its right below the printer, so signal strength is fine :)). I'll have a look at that once this power issue is sorted. One thing at a time haha

....but which wirelsss card do you use?

Just the one that I got with the machine: Wireless Network Card WIRELESS INTEL® Wi-Fi 6E AX210 2,400Mbps/5GHz, 300Mbps/2.4GHz PCI-E CARD + BT 5.0
 

youradds

Bronze Level Poster
I think I managed to run DDU and then installing the AMD GFX drivers. Is there a way that I can see if there is just the one running now?
 
Top