[Solved] Ntoskrnl.exe BSOD windows 7 (Caused by PSU)

[jimjamrockshard]

For a while, I've been experiencing many crashes specifically when playing games such as project cars, assassin's creed and watchdogs. For some reason if I lower the graphics settings, some games seem to be just fine, and don't crash untill I bump up the settings, like Rainbow six siege. What happens when my pc crashes is that the screen instantly goes black, and doesn't show an actual BSOD but my graphics card fans blast to the max for a few seconds followed by an automatic reboot. Once rebooted, a windows message pops up showing that it was caused by a BSOD. This first occured when I had a faulty molex to 6-pin pcie cable, which i replaced and it fixed it, but now it's just happening all over again. (Note that my power supply doesn't have a 6-pin pcie cable, and was pretty cheap, I'm thinking this to be the culpret)

----------------------------------------------------------------------------------------------------
My System Specs:
Geforce GTX 1060 3GB
AMD FX-4300
16GB DDR3 RAM
WD 1TB Hard Drive
ASUS M5A78L-M LX3 Micro ATX Motherboard
----------------------------------------------------------------------------------------------------

Minidump For Crash:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\022518-29655-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
Machine Name:
Kernel base = 0xfffff800`04401000 PsLoadedModuleList = 0xfffff800`04643750
Debug session time: Sun Feb 25 10:09:01.766 2018 (UTC + 0:00)
System Uptime: 0 days 0:00:10.828
Loading Kernel Symbols
....................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800e012038, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800e012038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`031c45b0 fffff800`046c0cd9 : fffffa80`0e012010 fffffa80`0cc33b50 fffffa80`00000006 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031c4ad0 fffff800`045a05e7 : fffffa80`0e012010 fffff800`0461a2f8 fffffa80`0cc33b50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031c4b00 fffff800`04507ee5 : fffff800`0467cbc0 00000000`00000001 fffffa80`0dbd6960 fffffa80`0cc33b50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031c4b40 fffff800`0447c085 : fffff880`00e6ee00 fffff800`04507ec0 fffffa80`0cc33b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031c4b70 fffff800`0470c622 : 160a1b19`0a1e1a0b fffffa80`0cc33b50 00000000`00000080 fffffa80`0cbe9870 : nt!ExpWorkerThread+0x111
fffff880`031c4c00 fffff800`04463da6 : fffff880`02fd7180 fffffa80`0cc33b50 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031c4c40 00000000`00000000 : fffff880`031c5000 fffff880`031bf000 fffff880`031c3c40 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------

2: kd> lmvm hardware
start end module name
Mini Kernel Dump does not contain unloaded driver list

-------------------------------------------------------------------------------------------------------

I know it says 'Probably caused by: Hardware' But i'm not sure what exactly could be causing it. If anyone could help me it would be much appreciated!

 

[Colif]

WHEA stands for Windows Hardware Error Architecture. Its an error called by the CPU but not necessarily caused by it

Can you go to C:\Windows\Minidump and copy the files there to another folder
From the other folder, upload the copies to a file sharing web site and share a link here, I will get someone to convert file for us.

Remove any overclocks
Remove any overclocking software, so MSI Afterburner, for instance.
can be caused by overheating

If you don't have any of those, it might well be that PSU you mentioned.. it just might not have the juice needed tor run the GPU. What Make/model PSU is it?

 

[jimjamrockshard]

WHEA stands for Windows Hardware Error Architecture. Its an error called by the CPU but not necessarily caused by it

Can you go to C:\Windows\Minidump and copy the files there to another folder
From the other folder, upload the copies to a file sharing web site and share a link here, I will get someone to convert file for us.

Remove any overclocks
Remove any overclocking software, so MSI Afterburner, for instance.
can be caused by overheating

If you don't have any of those, it might well be that PSU you mentioned.. it just might not have the juice needed tor run the GPU. What Make/model PSU is it?

So I sort of found out the model of the PSU, which is 'ATX Switching PSU Model: ATX-500B' but I got it in a cheap bundle with the 'Cit Phaser' case from Amazon I had. I'm pretty sure that tempreature isn't the problem because the case i have (Corsair 400C) has good airflow with two fans, and I checked the temps during games, with my cpu under 50C and GPU around 60C during gameplay. Another thing to note is that I test if the BSOD is still there by running Project Cars on max settings, and load in a map. As soon as it loads the map, it instantly crashes.

Here's the link to the Minidump file I uploaded: http://www119.zippyshare.com/v/e38hw0wy/file.html

I did uninstall GPU Tweak II, and i'll remove the overclock on my ram which I did recently, but I still think the problem will occur.

I hope this is useful, and thanks for helping me out!

 

[johnbl]

system up time was 10 seconds, most likely the motherboard reset the cpu and you got the bugcheck on the next boot.

most likely cause would be a graphic card using too much power via the pci/e bus. this triggers the motherboard logic to protect the motherboard graphics slot by having the motherboard reset the CPU.
the power supply is suppose to prevent the reset of the cpu from automatically starting but a lot of power supplies just fake the power_ok signal and the CPU just starts up again before the power is stable, then the CPU gets a internal error and the CPU memory controller calls a bugcheck 0x124 to shut down the system.

Best to focus on why the motherboard logic reset the CPU. Remove gpu tweak tools, any gpu overclock, remove CPU overclock, remove bios overclock. generally if it was cpu overheating the system uptimer would be longer. on older machines, blow out the dust from fans and make sure the fans are spinning. older power supplies can begin to provide incorrect voltages. Ie check the voltages in BIOS and see if they are within spec. older machines can have overclocking in bios, you can update the BIOS or reset it to defaults to get the best possible voltage defaults for your motherboard.

 

[jimjamrockshard]

system up time was 10 seconds, most likely the motherboard reset the cpu and you got the bugcheck on the next boot.

most likely cause would be a graphic card using too much power via the pci/e bus. this triggers the motherboard logic to protect the motherboard graphics slot by having the motherboard reset the CPU.
the power supply is suppose to prevent the reset of the cpu from automatically starting but a lot of power supplies just fake the power_ok signal and the CPU just starts up again before the power is stable, then the CPU gets a internal error and the CPU memory controller calls a bugcheck 0x124 to shut down the system.

Best to focus on why the motherboard logic reset the CPU. Remove gpu tweak tools, any gpu overclock, remove CPU overclock, remove bios overclock. generally if it was cpu overheating the system uptimer would be longer. on older machines, blow out the dust from fans and make sure the fans are spinning. older power supplies can begin to provide incorrect voltages. Ie check the voltages in BIOS and see if they are within spec. older machines can have overclocking in bios, you can update the BIOS or reset it to defaults to get the best possible voltage defaults for your motherboard.

Sorry for the late reply, I reset my BIOS and all the overclocks but the issue still persists, and i do often clean out my parts carefully. Just want to add that this problem started roughly when a security update for .NET Framework
3.5.1 on Windows 7 failed to install, so could that be linked somehow with the problem? If not, do you think that I should get antother PSU instead because the one right now seems quite dodgy and isn't even certified.

 

[Colif]

.net shouldn't cause WHEA errors but that PSU sure could. They can die after a few years so better to retire them before they go bang (one of mine did that, lucky only killed itself) and take a few parts with it.

 

[jimjamrockshard]

.net shouldn't cause WHEA errors but that PSU sure could. They can die after a few years so better to retire them before they go bang (one of mine did that, lucky only killed itself) and take a few parts with it.

Okay, I think I'll be able to get one soon now that I have the money, I'll keep you updated if it fixes it, and thanks for helping out!

 

[jimjamrockshard]

.net shouldn't cause WHEA errors but that PSU sure could. They can die after a few years so better to retire them before they go bang (one of mine did that, lucky only killed itself) and take a few parts with it.

Well I got a new 600W PSU with 80 plus bronze to be safe, and this seems to have fixed the prolem. I can now run my games at higher settings without it crashing at all, and i want to thank you a lot for your help. I had a feeling in the beginning that it probably was my old PSU. If anything does happen I'll let you know or probably creat a new forum.