Windows 10: -Closed-BSOD Whea_Uncorrectable_Error with two suspected culprit files

This thread is closed due to the issue stated being "resolved" (although not through conventional methods).

I'm posting a second thread about my issues since I provided the incorrect information on my previous thread regarding this. This time I've identified the two files that are causing these crashes to happen while playing Half-Life 2. These two files are hal.dll and ntoskrnl.exe, and I would really like to know how to fix them. I've tried reinstalling windows before using the option found in my laptop (After doing sfc/scannow in console) and it hasn't fixed the issue.

Any help would be greatly appreciated.

New dxdiag report-thing: Attachment 90586

BlueScreenView screenshot: Attachment 90612

:)

 

Help diagnosing BSOD, suspect on-board Bluetooth is the culprit

Ok I uploaded the new minidump to my onedrive, verifier-minidump.zip

Looking at the BSOD in BlueScreenView, it looks like the issue is vivefs.sys, so my HTC Vive driver? I believe the driver is up to date, I may have to contact HTC/Valve?

 

Help diagnosing BSOD, suspect on-board Bluetooth is the culprit

Thank you.

So I started Verifier as instructed in that link and on reboot the computer blue screens before Windows even finishes loading. I'll go read through the Verifier page again, but what do I do from here?

 

3 of the 4 dumps dump shows a hardware error:
Code: 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: ffffe0010a050028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.[/quote] The error record indicates a CPU problem:

Code: kd> !errrec ffffe0010a050028 =============================================================================== Common Platform Error Record @ ffffe0010a050028 ------------------------------------------------------------------------------- Record Id : 01d1e02f08d2b659 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 7/17/2016 14:21:40 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe0010a0500a8 Section @ ffffe0010a050180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Micro-Architectural Error Flags : 0x00 CPU Version : 0x00000000000306c3 Processor ID : 0x0000000000000007 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe0010a0500f0 Section @ ffffe0010a050240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000007 CPU Id : c3 06 03 00 00 08 10 07 - ff fb fa 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffe0010a050240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe0010a050138 Section @ ffffe0010a0502c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 7 Bank 4) Status : 0xbe00000000800400 Address : 0xfffff80077f0ccb8 Misc. : 0xfffff80077f0ccb8[/quote] See if you can run Prime95 to stress test your CPU.
===================================================
Follow this tutorial to stress test your CPU:
Prime95 - Stress Test Your CPU - Windows 10 Forums

I believe you are looking at a CPU replacement. I'll ask some of the other folks here to also look at this and see what they think.

 

Glad I asked! One of the responses I got said this is not necessarilly a CPU problem and can be caused by many other things.

Follow the directions at this link for a good troubleshooting process to follow to try to resolve the 0x124 BSOD.

Stop 0x124 - what it means and what to try - Windows 7 Help Forums

Written for Windows 7 but applies to Windows 8.1 and 10 as well.

Take a look at it then post back your thoughts on doing as described.

 

One other thing you can try up front is to do a Clean Boot. This can help determine if the problem is being caused by something that starts at boot time or not.

See here: How to Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

 

I've gone a bit through the logs and would like to say something about certain Windows Error Reports in the dxdiag.txt.

These WER's are nothing to be worried about, it is about SFC errors due to hash mismatched in the COMPONENTS hive.
The COMPONENTS hive holds hashes that are not the right one for these manifest files which is why SFC reports errors.
These manifest files are from Avast, Avast is aware of the issue and is working on a fix.

This is not an issue that can be fixed through regedit, because the COMPONENTS hive is not visible in the registry editor.
If it was then someone could bring a lot of damage onto a system.
Code: +++ WER7 +++: Fault bucket , type 0 Event Name: WindowsWcpStoreCorruption Response: Not available Cab Id: 0 Problem signature: P1: 10.0.10586.486:1 P2: FileHashMismatch P3: \winsxs\manifests\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.manifest P4: P5: P6: P7: P8: P9: P10: +++ WER5 +++: Fault bucket 126702013853, type 5 Event Name: WindowsWcpStoreCorruption Response: Not available Cab Id: 0 Problem signature: P1: 10.0.10586.486:1 P2: FileHashMismatch P3: \winsxs\manifests\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.manifest P4: P5: P6: P7: P8: P9: P10:[/quote] Uninstalling doesn't help, the uninstaller misses these manifests.

 

Thanks a lot for replying. I've been away from my laptop for a while and will be able to provide more information about my issues soon.

 

I'm back at my computer for a while. Is there any way that I can prevent this/stop this from happening altogether?

 

Does the crash only occur when you play Half-life 2?

To answer this, you can't fix them.
Both of these files are Windows files, only updated through Windows Update.
HAL.dll is the Hardware Abstraction Layer DLL, the DLL that provides hardware communication.
Ntoskrnl.exe is one of the Windows files of the Windows Kernel.

If a Windows file is blamed you can always safely assume that it definitely is not the cause, Windows files are often blamed because they are the last one active, fortunately that doesn't make it the root cause because else Windows would not be the OS that so many people daily use.
Fortunately some of the Windows files do can give clues about possible causes sometimes.

 

This crash has occured when playing Half-Life 2, Fistful of Frags, and Team Fortress 2, which all use the Source physics engine, which might be causing the issue (although I've not seen any reports on this crash anywhere else). Recently, this crash has escalated to not even showing the blue-screen when it crashes, rather looping the last bit of audio and freezing on the last frame played. I waited for about half an hour before restarting my computer and checking bluescreenview, which hadn't changed.

Thanks for your reply.

 

Please upload a new zip from the DM Log Collector for analysis.

 

Attachment 93117 Here it is.

 

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Dell. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver, you can use this tutorial for the installation part *Arrow NVIDIA Drivers - Avoid Problems - Windows 7 Help Forums
Attachment 93146
Code: Windows Error Reporting: +++ WER0 +++: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: NvStreamUserAgent.exe P2: 7.1.2084.9592 P3: 57605c64 P4: ntdll.dll P5: 10.0.10586.306 P6: 571af2eb P7: c0000005 P8: 000000000002e909 P9: P10: +++ WER1 +++ Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: NvStreamUserAgent.exe P2: 7.1.2084.9592 P3: 57605c64 P4: ntdll.dll P5: 10.0.10586.306 P6: 571af2eb P7: c0000005 P8: 000000000002e909 P9: P10: +++ WER2 +++: Fault bucket 129133875103, type 5 Event Name: FaultTolerantHeap Response: Not available Cab Id: 0 Problem signature: P1: NvStreamUserAgent.exe P2: 7.1.2084.9592 P3: 57605C64 P4: ffffbaad P5: P6: P7: P8: P9: P10: +++ WER3 +++ Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: NvStreamUserAgent.exe P2: 7.1.2084.9592 P3: 57605c64 P4: ntdll.dll P5: 10.0.10586.306 P6: 571af2eb P7: c0000005 P8: 000000000002e909 P9: P10:[/quote]

 

I've done everything you've asked but now I'm getting a CLOCK_WATCHDOG_TIMEOUT error when playing the same games. It does what it would normally do when it crashes, except it actually goes to the normal BSOD error message. It starts to gather information about the crash but gets stuck at around 5-30%.