- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello. I have been having problems with the whea_uncorrectable error BSOD for a while now. I seem to bluescreen at random times - sometimes when idle, gaming, watching youtube, opening the explorer or just casual browsing (multiple times a day usually, sometimes 10 minutes apart, sometimes hours apart). I tried to stresstest my CPU, GPU, RAM and even SSD, but nothing seemed to trigger the BSOD and everything seems healthy (even though some of my computer components are REALLY old).
After my computer decided its time to update windows, the BSOD started happening again - i tried to uninstall it again since it has worked as a workaround in the past but i can't uninstall it, not in any way.
Now i'm helpless, i have tried everything i could think of and i sadly don't have any spare hardware laying around which i could use to see if it do is one of my components.
I started looking at my minidump files in WinDbg, and i've noticed that every one of them looks pretty much like this: (this is the latest one)
******************************************************************************* * * * 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 nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffc887a44c7028, Address of the nt!_WHEA_ERROR_RECORD structure. Arg3: 00000000f2000140, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 5062 Key : Analysis.Elapsed.mSec Value: 5768 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 499 Key : Analysis.Init.Elapsed.mSec Value: 6739 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : Bugcheck.Code.LegacyAPI Value: 0x124 Key : Dump.Attributes.AsUlong Value: 8 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys Key : Failure.Hash Value: {5371cb52-c3d9-558e-47d4-d31c09567ca2} BUGCHECK_CODE: 124 BUGCHECK_P1: 0 BUGCHECK_P2: ffffc887a44c7028 BUGCHECK_P3: f2000140 BUGCHECK_P4: 10005 FILE_IN_CAB: 022524-8171-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffff8301`860e78e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel.sys STACK_COMMAND: .cxr; .ecxr ; kb FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2} Followup: MachineOwner ---------
bluescreenview indicates it is caused by ntoskrnl.exe but my effort in somehow fixing it didnt work out.
i dont know what to do anymore, any ideas?
I tried:
various stresstests and benchmarks (cpu, gpu, ssd, ram)
sfc /scannow
verifier.exe
dism /...
chkdsk
uninstalling windows updates
updating several drivers
reset BIOS to stock
changed power to high performance (it instantly crashed when i put it to power safe mode)
Specs: (it is weird i know)
CPU Intel Core i5 6600
Motherboard Acer Aspire TC-780 (its from an old prebuild pc)
GPU NVIDIA GeForce GTX 1070 Ti
RAM 12GB of DDR4 ram
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, but your processor is 8 yearss old and no longer supported.
Doc (not an Intel employee or contractor)
[Maybe Windows 12 will be better]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
i know that, and unfortunately i don't have the money right now to replace it, so i am kinda trying everything to make that thing live for as long as possible. and i'm also scared that if i replace it, the bsod will still happen and then i will be out of money again to replace whatever else is probably broken
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
https://www.intel.com/content/www/us/en/support/articles/000028099/processors/intel-core-processors.html
https://www.intel.com/content/www/us/en/support/articles/000025090/processors.html
About the stress test, did you use the ipdt? You can find the link here: https://www.intel.com/content/www/us/en/support/articles/000005567/processors.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
thank you for your suggestions, but unfortunately nothing i could do helped, and it feels like the crashes appear more often now.
I did run the ipdt test, but it said my processor was fine.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page