BSOD on Win 8.1 after a few minutes (not in safe mode)

WolfPan

New member
Joined
Dec 21, 2013
Posts
1
Since a few days when starting the laptop in normal mode, after logon Win8.1 starts and after 1 or 2 minutes i get a BSOD (most of the time a DPC_WATCHDOG_VIOLATION).

This never happens in safe mode.

I tried the solutions from
https://www.sysnative.com/forums/windows-update/7702-guide-cnbj2530-dpb-and-prncacla-inf-corruptions-windows-8-8-1-a.html:
1. Repair method 2
2.
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow didn't find any problems after both methods, but the BSOD came back.

My system:
·
OS - Windows 8.1
· x64
· original installed OS on system: Windows 8
· OEM version (came pre-installed on system)
· October 2013
· Age of OS installation: October 2013

· CPU: Intel(R)_Core(TM)_i7-4700MQ_CPU_@_2.40GHz
· Video Card: Intel(R) HD Graphics 4600 + NVIDIA GeForce GT 740M
· MotherBoard: HP)

· System Manufacturer : HP
· Exact model number: Envy 17 j000eb


You'll find the Windows7_Vista_jcgriff2.zip in attachment.

I was unable to run the perfmon /report
due to an error ("Cannot find the path specified"). Can you tell me how to solve this problem?

Kind regards
 

Attachments

Hi,

All of the attached dump files are of the DPC_WATCHDOG_VIOLATION (133) bug check.

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.

1. Please remove COMODO as it's likely causing corruption.

2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

----------------

If you're still crashing after the above, please enable Driver Verifier:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top