Here, you would still use an application such as BlueSceenWindow to find the cause of the error. ![]() Such an example is the FAULTY_HARDWARE_CORRUPTED_PAGE error. While driver issues are usually easily fixed, a BSOD that is a result of failed hardware is a different story. What If The Minidump File Shows A Hardware Error? Using this view of the Windows minidump file, we can deduce that the BSOD was likely caused by a graphics driver issue, which can typically be corrected by installing a newer version of the driver or reinstalling the current driver. Doing a quick check on Google, we can see that dxgmms2.sys is related to the Windows DirectX drivers, while ntoskrnl.exe is the operating system kernel executable - responsible for keeping the operating system running. So those will also need to be looked into. We know that watchdog.sys is the potential cause, but what about dxgmms2.sys and ntoskrnel.exe? As those were the affected files, we need to find out what those are as well. This is a good starting point as you can now check Google or Bing, to see how this could become a problem and possible solutions. ![]() In this image, we can see that the watchdog.sys caused the problem. ![]() In this screenshot (see how to take screenshots in Windows for more), we can see that on this specific minidump, there was an issue detected that affected three files dxgmms2.sys, ntoskrnl.exe and watchdog.sys.įurther on the upper panel, we can see in the right column that there’s a section that tells us what caused the crash.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |