Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, 0, 0}
*** WARNING: Unable to verify timestamp for ha20x22k.sys
*** ERROR: Module load completed but symbols could not be loaded for ha20x22k.sys
Probably caused by : ha20x22k.sys ( ha20x22k+7b5f1 )
Followup: MachineOwner
Hi,
the above dump file has the following cause:
This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above.
Reference I can see by the details within the dump file that the driver ha20x22k.sys was involved:
Code:
FAILURE_BUCKET_ID: 0x133_ISR_ha20x22k+7b5f1
It's possible that it could be a different driver affecting the driver outlined above but if that does prove to be the case then testing will eventually bring the culprit to light. If the changes outlined below makes no difference to the bsods we'll use the driver verifer.
ha20x22k.sys Sat Dec 19 00:09:02 2015: Creative Technology Audigy. Please check for updates but if if non are available please re-install driver. When you re-install it please right-click start up exe and run as admin.
avgntflt.sys Wed Jan 13 17:40:59 2016: Avira AV, please remove until after troubleshooting has been completed. Avira has been known to cause issues in the past and we would ask that you just run on the default Defender for now as this is super stable.
Find command prompt, right click on it and run as administrator. Type:
sfc /scannow
press enter and await results
In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).
If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
If the bsod's continue after making the above changes then please run the driver verifier. You will need to first create a recovery disk or USB in case the verifier causes a bsod loop on start up. You'll need the recovery disk/usb to boot into safe mode and then turn the verifier off:
Creating a USB recovery drive - Windows Help Here is a short guide on running the verifer:
How do I fix a Blue Screen in Windows using Driver Verifier? Post any new dump files.
