BSOD once every few months since I bought a new PC

Frozy · 18 Sep 2023

Hello, in November 2022, I bought a new PC and changed everything excluding the following pieces:
Power Supply (XFX Pro 1000W)
NVMe™ SSD (WD Black 1TB)
Case (Graphite Series™ 780T Full-Tower)
CPU Water Cooler (Hydro Series™ H100i v2)

Since then, I sometimes will get a BSOD (watchdog) when doing random things such as navigating on google chrome or running a video game. Please note that I also messed with overclocking at start but then decided to revert all changes to default.

I also noticed that everytime I restart my PC, it restarts twice. The fans on the case also sometimes make more noise than usual, or simply don't run. I have to use soft violence to get them going again (they are clean).

Finally, I ran a powercfg -energy and see link for results (there were some errors and warnings) here.

C:\Windows\System32>powercfg -energy
Enabling tracing for 60 seconds...
Observing system behavior...
Analyzing trace data...
Analysis complete.

Energy efficiency problems were found.

11 Errors
9 Warnings
58 Informational

I am currently running a high performance power plan.

Windows version: Version 22H2 Build 22621.2283

V2 Log

zbook · 18 Sep 2023

Please post a new V2 share link.

(Make sure that there are no additional attachments with the V2)
(The attachment should not be 2.3 GB)

Frozy · 18 Sep 2023

The Minidump file (MEMORY.DMP) is 31.7gbs. That is why.

zbook · 18 Sep 2023

Please follow the posting instructions.

Frozy · 18 Sep 2023

zbook said:

Please follow the posting instructions.

I'm not sure why you are replying this. It sounds rather unhelpful. If you want to help, please point me in the direction in which I did not follow the instructions. I read the instructions multiple times before I posted and I just read them again. I don't see any issue with what I did.

zbook · 18 Sep 2023

The instruction is to run V2 and post a share link.

There were no other files to be attached to the V2 share link.

Frozy · 18 Sep 2023

zbook said:

The instruction are to run V2 and post a share link.

There were no other files to be attached to the V2 share link.

When I ran the V2 log, it first opened a command prompt, then a powershell, then a second command prompt which lasted for a long time until it confirmed the location of the zip file it produced. Then I went to Google Drive and uploaded that file as mentioned in the posting instructions when the file is too large. I did not attach any additional file inside that zip file. That zip file is what outputed from the V2 log process.

zbook · 18 Sep 2023

Imagine the V2 log collector collects files that can be downloaded quickly.
Imagine that someone decides to include in the attachment additional files.
Now there is an unknown time.

Frozy · 18 Sep 2023

I have no idea what you are saying but you can consider this issue as solved. I will seek help somewhere else.

ubuysa · 19 Sep 2023

Hello, I'm sorry you weren't made to feel more welcome. Let me try and help you. You wrote...

Frozy said:

The Minidump file (MEMORY.DMP) is 31.7gbs. That is why.

That's not a mindump it's a complete memory dump, and nobody is ever going to download that - I don't image that you want to upload it!

In the RUN command box enter the command sysdm.cpl. In the window that opens, click the Advanced tab. Click the bottom Settings button (in the Start-up and Recovery section). Using the pull-down menu in the 'Write debugging information' section, select 'Automatic memory dump'. Also ensure that the 'Overwrite any existing file' box IS checked. Then click OK.

Also take a look in the folder C:\Windows\Minidump and let us know if there are any .dmp files in there. If not then sadly we'll have to wait for more BSODs to occur and more dumps to be written.