Very Strange Recurring BSOD

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  • Hello everyone We want to personally apologize to everyone for the downtime that we've experienced. We are working to get everything back up as quickly as possible. Due to the issues we've had, your password will need to be reset. Please click the button that says "Forgot Your Password" and change it. We are working to have things back to normal. Emails are fixed and should now send properly. Thank you all for your patience. Thanks, PCHF Management
Status
Not open for further replies.

UberRix

PCHF Member
Jan 5, 2022
2
0
24
Hello all,

I have encountered a strange error with my PC for quite a while now. Whenever my computer is doing any strenuous activity (in my case, it is invariably video games with a significant graphical element), my computer will crash. Confusingly, it will only flash the blue screen of death for less than half a second and then reboot. If I change the setting in the “startup and recovery” section of the control panel which automatically restarts my computer, the blue screen stays, but is stuck on 0% collecting data. This means that I cannot access the dump that windows could have created and have little information on what the crash is related to. I did check the event viewer, and got this information:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 1/3/2022 12:22:44 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: DESKTOP-LEFMQC7
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

I have heard that this is associated with a faulty power supply unit, but would like to exhaust every possibility other than that. Any help would be much appreciated. What follows is a list of my PC specs and everything that I have already tried troubleshooting.

Changing power settings: I changed my settings to the most energy intensive ones possible, to no avail.
run windows memory diagnostic + chkdsk: No problems reported
driver update: Windows says all my drivers are up to date, and I made sure that my graphics drivers were as well.
is the PC overheating?: I used HWiNFO to log data right before I induced the crash, temps seemed fine (nothing in the 80+ range fahrenheit). It's worth noting that all the data collected 30 seconds before the crash is erased, so I have really no way of knowing if there was a significant temp/power spike. For anyone interested, here is the csv file: https://drive.google.com/file/d/16ZRG86B82e2EF1IbPDVA9ro1mloB4cab/view?usp=sharing. The crash occurred at 3 mins 30 secs from this logs perspective. I used GenericLogViewer to look at the data.


GPU: NVIDIA GeForce GTX 980 Ti
CPU: AMD Ryzen 5 3600X
Motherboard: GIGABYTE AB350-Gaming-CF
SSD: Samsung SSD 970 EVO 1TB
RAM1: Crucial Ballistix 8GB (part number: BLS8G4D26BFSE.16FE)
RAM2: Crucial Ballistix 16GB (part number: BLS16G4D240FSE.16FD)
PCU: Kentek 1050 Watt Power Supply (model number: KTPS-1050)

I am posting this here to make sure that I have exhausted all possibilities, and buying a new power supply is really the right option. Any advice would be greatly appreciated.
 
The key word for researching this appears to be the "keyword 70368744177664" -I suggest you do that.

Microsoft mentions " ...
ntkrnlmp.exe is a Windows component which means something else drove it into Fault. The real cause is most likely the ATI/AMD video drivers dated 10/5/2017 and/or the motherboard and CPU.

Check with ASUStek and AMS/ATI Supports, their on-line documentation and drivers, and ask in their forums about any known issues. Update the BIOS, chipset drivers, and the major on-board and separate device drivers (especially the video drivers)...."

I will have to add:

Make sure the system is not overclocked.
The memory is on the QVL for this particular motherboard.
The Video drivers are not beta or tweaked.
 
  • Like
Reactions: veeg
The key word for researching this appears to be the "keyword 70368744177664" -I suggest you do that.

Microsoft mentions " ...
ntkrnlmp.exe is a Windows component which means something else drove it into Fault. The real cause is most likely the ATI/AMD video drivers dated 10/5/2017 and/or the motherboard and CPU.

Check with ASUStek and AMS/ATI Supports, their on-line documentation and drivers, and ask in their forums about any known issues. Update the BIOS, chipset drivers, and the major on-board and separate device drivers (especially the video drivers)...."

I will have to add:

Make sure the system is not overclocked.
The memory is on the QVL for this particular motherboard.
The Video drivers are not beta or tweaked.
I appreciate the reply. However, I have a few questions. 1 - my cpu is very often operating at above the base speed (i.e. operating at 4.1GHz, when the base speed is 3.8GHz). I have heard that this is normal and does not nessecariliy mean the my pc is overclocking. Might this still contribute to the problem? Question 2 - when talking about the QVL, do you mean RAM in specific? I am not very well acquainted with QVLs, would this be the right one to check? https://download.gigabyte.com/FileList/Memory/mb_memory_ga-ab350-gaming.pdf
 
Hi

Sorry for answering back... ...backwards.

Yes, that is the QVL, and the memory you have IS NOT THERE.
Is there anything in the BIOS that prevents the CPU from overclocking? If yes, disable it-or set the BIOS default (AFTER you update the BIOS-if there is a new version available).

Also see if there are any driver updates in GIGABYTE's site for your motherboard.

Have to point out that personally I would first put the default settings and then go from that.
 
Last edited:
I have heard that this is associated with a faulty power supply unit
PCU: Kentek 1050 Watt Power Supply (model number: KTPS-1050)

Released in 2011, no energy efficiency rating or warranty period information available so yes, a strong contender as the cause.

Confusingly, it will only flash the blue screen of death for less than half a second and then reboot.

Software such as Windows can crash and when it does crash you get a BSOD and when enabled a crash dmp is generated, programs or games when they crash can on occasion close to the desktop but the computer will still be 100% functional.

Hardware failure such as a weak power supply and/or overheating are not software related and when a computer for example suddenly turns off or freezes etc the behaviour should be described as the "computer shut down unexpectedly" or froze and not as having crashed as the latter implies a software issue as opposed to an obvious hardware issue when described properly.

Having the correct info means that helpers will not be looking for a software issue when the problem is clearly hardware related.

Download then run Speccy (free) and post the resultant url for us, details here, this will provide us with information about your computer hardware + any software that you have installed that may explain the present issue/s.

To publish a Speccy profile to the Web:

In Speccy, click File, and then click Publish Snapshot.

In the Publish Snapshot dialog box, click Yes to enable Speccy to proceed.

Speccy publishes the profile and displays a second Publish Snapshot. You can open the URL in your default browser, copy it to the clipboard, or close the dialog box.



Download MiniToolBox and save the file to the Desktop.

Close the browser and run the tool, check the following options;

List last 10 Event Viewer Errors
List Installed Programs
List Devices (Only Problems)
List Users, Partitions and Memory size

Click on Go.

Post the resulting log in your next reply for us if you will.
 
Status
Not open for further replies.