Windows 10: HAL_INITIALIZATION_FAILURE crash dump
Because details about the results are needed.
Because it is not believable that you've performed all tests on each drive/partition in only a few hours.
System File Check
Please try following:
- Open an admin command prompt
- Copy/paste "sfc /scannow" (without quotes) and press enter
- When it is finished reboot your system
- Open again an admin command prompt
- Enter sfc/scannow again
If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at %systemroot%\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
Make a photo of SFC and post it.
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
Has the problem re-occured since troubleshooting?
No - so let's let sleeping dogs lie ...
I keep getting IRQL_NOT_LESS_OR_EQUAL BSOD and I'd like to get it resolved.
I've tried a clean install of OS, resetting BIOS settings and driver updates, but none have helped. PC passed a Intel CPU check and Memtest86+ check.
Here is a...
I've been experiencing some random BSOD and freezes and managed to create crash dump files using driver verifier.
Unfortunately I cannot read what driver is causing the BSOD's / freezes.
Can someone please help me?
So my PC has been BSOD like crazy in windows 10.
I have tried debugging using WinDbg, all crash dump errors point towards ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1164c )
Please advice, what am I missing?
I have attached the crash dump...
Windows 10 has been working like a Dream but now its turned into a nightmare! Constantly Crashing after an hour of use, has anyone else had this problem, as its been working fine for months.
I've just got build 10122 and looking through the SSD shows 15.9 gb of Windows old. This pc has run W10 since the beginning with a clean install so W old is only from previous iterations of 10. Is it wise to dump the old files?