Tech Support banner

Status
Not open for further replies.
1 - 4 of 4 Posts

·
Registered
Joined
·
2 Posts
Discussion Starter · #1 ·
I can't reproduce this BSOD but it happens when I am working with/closing a capture card program called AmarecTV: AmaRecTV

99% of the time it is fine using this program. I have never got a BSOD any other way (i.e. normal operation).

Specs:

i5 2500k
Gigabyte P67A-UD4
8 GB RAM
ATI 6850

I have attached the 3 BSOD dumps.
 

Attachments

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Hi,

Three dumps attached, all of the PROCESS_HAS_LOCKED_PAGES (76) bugcheck. This is a device driver bug, it means that a driver is not cleaning up correctly after an I/O. Unfortunately, the 4th argument is 0 and not 1 therefore we cannot find out the guilty driver.

You can go the registry key method to make it so next time you crash, rather than a PROCESS_HAS_LOCKED_PAGES (76) bugcheck, it will be a DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (0xCB) bugcheck. For now though, I am just going to recommend taking the safer route and enable Driver Verifier:

Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 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 by flagging it and causing your system to BSOD.
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"
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)
- Concurrentcy Stress Test (Windows 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 > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- 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.
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 36-48 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 C:\Windows\Minidump
Any other questions can most likely be answered by this article:
http://support.microsoft.com/kb/244617

Regards,

Patrick
 

·
Registered
Joined
·
2 Posts
Discussion Starter · #3 ·
Hi

That makes sense. I am pretty sure the driver culprit is the Blackmagic Intensity Pro capture card I have as it's what I have active in Amarec when I close it. The Blackmagic drivers also have a "WDM" driver which you mentioned in Driver Verifier so that also leads me to believe it is that. Their forums also seem to be littered with similar issues. I'll probably downgrade to older "stable" drivers and test them out.

If it happens again with older ones then I will do the Driver Verifier step.
 
1 - 4 of 4 Posts
Status
Not open for further replies.
Top