Question WHEA_ UNCORRECTABLE_ERROR after a full reset ?

[larry_foulke]

I had some issues recently with my gpu not working. Something led to it having error 43, which would not let windows run it after a crash. I received help from this forum and found that the other gpu I had worked fine. I used it by itself for a bit untill i got another BSOD, Then I decided to reset my pc. After doing that It seemed to be stable so i reconnected the other card again, and windows detected it no problem. then I got the BSOD. The 2nd card isnt being detected again, so it may be a hardware issue, but the fact it happened when it wasnt connected makes me think otherwise. I get error Whea_uncorrectable_error
whenever it crashes, and I see the following strings of numbers:
0r0000000000000000
OKFFFFA1S7FE526028
0x0000000062000000
0r000000000070005

My current rig is

https://pcpartpicker.com/list/XGscZw

I'd appreciate any help

 

[helpstar]

is the BIOS of motherboard up to date?

check the motherboard´s CPU socket for bent pins

 

[ubuysa]

Upload the mindumps (they're in C:\Windows\Minidump). Zip them up and upload them here.

Also please export and upload your System and Application logs. Here's how to do that....

1. Enter the command eventvwr into the Run command box. The Event Viewer will open.
2. Locate the Windows Logs folder in the left hand pane and expand it by clicking on the arrow (>) to the left of it.
3. Right-click on the Application entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'Application' (an .evtx suffix will be added automatically).
4. Right-click on the System entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'System' (an .evtx suffix will be added automatically).
5. Zip the Application.evtx and System.evtx files together and upload the zip file here.

 

[larry_foulke]

is the BIOS of motherboard up to date?

check the motherboard´s CPU socket for bent pins

Will do.

Upload the mindumps (they're in C:\Windows\Minidump). Zip them up and upload them here.

Also please export and upload your System and Application logs. Here's how to do that....

1. Enter the command eventvwr into the Run command box. The Event Viewer will open.
2. Locate the Windows Logs folder in the left hand pane and expand it by clicking on the arrow (>) to the left of it.
3. Right-click on the Application entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'Application' (an .evtx suffix will be added automatically).
4. Right-click on the System entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'System' (an .evtx suffix will be added automatically).
5. Zip the Application.evtx and System.evtx files together and upload the zip file here.

here they are https://www.mediafire.com/file/bjhsq3lwjkys6q6/EVTX_files.7z/file
https://www.mediafire.com/file/2qqfl5tf4q8pi7z/Minidump.7z/file i hope its okay to upload them like this. i dont think this website supports uploading files as i couldnt find a way to upload them directly.

 

[ubuysa]

That's fine, thanks.

I can see five BSODs in your System log (which only goes back to 10th July) but you uploaded only two dumps. What happened to the other three dumps? The more dumps you can upload the more confidence we can have in any diagnosis we make.

I see nothing in your System or Application lopgs to account for the bugchecks - this often points to a sudden and undexpected hardware failure. Both dumps are pretty much identical, they both seem to fail during idle processing with a machine check hardware error....

9: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffffa900`97d468e8 fffff801`64ab77ba     nt!KeBugCheckEx
01 ffffa900`97d468f0 fffff801`640815b0     nt!HalBugCheckSystem+0xca
02 ffffa900`97d46930 fffff801`64bb9a9e     PSHED!PshedBugCheckSystem+0x10
03 ffffa900`97d46960 fffff801`64ab90e1     nt!WheaReportHwError+0x46e
04 ffffa900`97d46a40 fffff801`64ab9453     nt!HalpMcaReportError+0xb1
05 ffffa900`97d46bb0 fffff801`64ab9330     nt!HalpMceHandlerCore+0xef
06 ffffa900`97d46c00 fffff801`64ab9581     nt!HalpMceHandler+0xe0
07 ffffa900`97d46c40 fffff801`64ab87eb     nt!HalpMceHandlerWithRendezvous+0xc9
08 ffffa900`97d46c70 fffff801`64abb035     nt!HalpHandleMachineCheck+0x5f
09 ffffa900`97d46ca0 fffff801`64b10b59     nt!HalHandleMcheck+0x35
0a ffffa900`97d46cd0 fffff801`64a0cbba     nt!KiHandleMcheck+0x9
0b ffffa900`97d46d00 fffff801`64a0c877     nt!KxMcheckAbort+0x7a
0c ffffa900`97d46e40 fffff801`6d41138f     nt!KiMcheckAbort+0x277
0d ffffef04`d92aef78 00000000`00000000     intelppm!MWaitIdle+0x1f

You read these call stacks from the bottom up, you can see we start in the intelppm.sys driver. This is a Microsoft driver that is called when a processor is idle; ie. it has no work on the ready queue. The intelppm.sys driver is the 'Processor Power Management' driver and it's job is twofold; to look for useful work to do (executing a DPC queue for example) and to halt the processor in a low power state waiting for an interrupt to wake it when more work arrives. The very next function call is to the kernel machine check abort function (nt!KiMcheckAbort+0x277), so the hardware machine check occurred during intelppm.sys processing.

It's not unusual for some CPUs to become unstable at lower power settings, though AMD processors seem to suffer more than Intel, and this would appear to be a potential low power CPU instability problem.

The first thing you need to do is remove any CPU overclock and/or CPU undervolt that you may have applied. With this type of BSOD the CPU must be running at stock voltages and frequencies.

There are two ways of stopping the CPU from entering lower power states:

• Switch your Power Options profile to the (Windows) High Performance profile
• Change the Power Options Processor Power Management values so that the Minimum Processor State is 99% and the Maximum Processor State is 99%

Try each of those, one at a time, and each for a day or two. See whether they stop the BSODs. If they do, then you most likely have a CPU that's becoming unstable in lower power states.

 

[larry_foulke]

That's fine, thanks.

I can see five BSODs in your System log (which only goes back to 10th July) but you uploaded only two dumps. What happened to the other three dumps? The more dumps you can upload the more confidence we can have in any diagnosis we make.

I see nothing in your System or Application lopgs to account for the bugchecks - this often points to a sudden and undexpected hardware failure. Both dumps are pretty much identical, they both seem to fail during idle processing with a machine check hardware error....

9: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffffa900`97d468e8 fffff801`64ab77ba     nt!KeBugCheckEx
01 ffffa900`97d468f0 fffff801`640815b0     nt!HalBugCheckSystem+0xca
02 ffffa900`97d46930 fffff801`64bb9a9e     PSHED!PshedBugCheckSystem+0x10
03 ffffa900`97d46960 fffff801`64ab90e1     nt!WheaReportHwError+0x46e
04 ffffa900`97d46a40 fffff801`64ab9453     nt!HalpMcaReportError+0xb1
05 ffffa900`97d46bb0 fffff801`64ab9330     nt!HalpMceHandlerCore+0xef
06 ffffa900`97d46c00 fffff801`64ab9581     nt!HalpMceHandler+0xe0
07 ffffa900`97d46c40 fffff801`64ab87eb     nt!HalpMceHandlerWithRendezvous+0xc9
08 ffffa900`97d46c70 fffff801`64abb035     nt!HalpHandleMachineCheck+0x5f
09 ffffa900`97d46ca0 fffff801`64b10b59     nt!HalHandleMcheck+0x35
0a ffffa900`97d46cd0 fffff801`64a0cbba     nt!KiHandleMcheck+0x9
0b ffffa900`97d46d00 fffff801`64a0c877     nt!KxMcheckAbort+0x7a
0c ffffa900`97d46e40 fffff801`6d41138f     nt!KiMcheckAbort+0x277
0d ffffef04`d92aef78 00000000`00000000     intelppm!MWaitIdle+0x1f

You read these call stacks from the bottom up, you can see we start in the intelppm.sys driver. This is a Microsoft driver that is called when a processor is idle; ie. it has no work on the ready queue. The intelppm.sys driver is the 'Processor Power Management' driver and it's job is twofold; to look for useful work to do (executing a DPC queue for example) and to halt the processor in a low power state waiting for an interrupt to wake it when more work arrives. The very next function call is to the kernel machine check abort function (nt!KiMcheckAbort+0x277), so the hardware machine check occurred during intelppm.sys processing.

It's not unusual for some CPUs to become unstable at lower power settings, though AMD processors seem to suffer more than Intel, and this would appear to be a potential low power CPU instability problem.

The first thing you need to do is remove any CPU overclock and/or CPU undervolt that you may have applied. With this type of BSOD the CPU must be running at stock voltages and frequencies.

There are two ways of stopping the CPU from entering lower power states:

• Switch your Power Options profile to the (Windows) High Performance profile
• Change the Power Options Processor Power Management values so that the Minimum Processor State is 99% and the Maximum Processor State is 99%

Try each of those, one at a time, and each for a day or two. See whether they stop the BSODs. If they do, then you most likely have a CPU that's becoming unstable in lower power states.

there were only 2 dump files. I'll change the power management values as you reccomend and see if that helps