📎 AI Summary:
In this WindowsForum thread, the original poster reports random Blue Screen of Death (BSOD) crashes with no clear trigger. A responder analyzes dump files, identifies potential driver corruption—particularly pointing out issues with MSI software and an overclocking utility—and recommends running system scans like sfc /scannow and driver verifier. The overall sentiment is a troubleshooting process aimed at isolating and resolving driver-related blue screens.
In this WindowsForum thread, the original poster reports random Blue Screen of Death (BSOD) crashes with no clear trigger. A responder analyzes dump files, identifies potential driver corruption—particularly pointing out issues with MSI software and an overclocking utility—and recommends running system scans like sfc /scannow and driver verifier. The overall sentiment is a troubleshooting process aimed at isolating and resolving driver-related blue screens.
Solution
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 18, {fffffa800f719de0, fffffa800ff543e0, 1, 500}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4165a )
Followup: MachineOwner
both dump files were the same and point to a possibly corrupted driver although it's difficult to say what or which...
kemical
Essential Member
Member details
- Joined
- Aug 28, 2007
- Messages
- 36,163
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 18, {fffffa800f719de0, fffffa800ff543e0, 1, 500}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4165a )
Followup: MachineOwner
both dump files were the same and point to a possibly corrupted driver although it's difficult to say what or which driver.
I see you have the Intel extreme overclocking utility installed. If your overclocking then please stop until source of bsod is found.
This:
NTIOLib_X64.sys Mon Mar 17 10:24:03 2014: MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5, MSI Super Charger & MSI Smart Utilities.
Please find cmd prompt, right click on it and run as admin
Type: sfc /scannow then press enter
Have you changed anything recently like new hardware/software?
You could also try running the driver verifier and see if this trips anything up into blue screening:
Link Removed
Post any new dump files