BSOD While editing video. 0x00000076

SoCalledComrad · 16 Jul 2012

Hey,

recently I started getting a BSOD while editing video, the BSOD occurs while the video is rendering but sometimes it also happens when I'm converting the video in 'any video converter' Could someone please take a look at the dump files and help me with this?

My OS is windows 7 home premium 64bit OEM and I already tried reinstalling my OS and it worked but as soon as I started reinstalling my software the blue screen returned. Now that I think about it it comes to my mind that the BSOD started after installing a driver to capture my speakers audio for a program called 'Debut Video Capture Software'

I ran BlueScreenView and it told me the same thing as before reinstalling my os:
PROCESS_HAS_LOCKED_PAGES caused by driver ntoskrnl.exe and caused by address ntoskrnl.exe+7f1c0 (I included a screenshot of BlueScreenView in the dump files)

My laptop is an acer aspire 7715G. Could someone please give me clear instuctions on how to fix this. (I'm not good when it comes to messing with windows)

Thank you! (Sorry for my English)

note: When the BSOD occurs my laptop reboots and when I then try to render/convert a video it does work.

UPDATE: I' just used system restore to go back the the point before I installed that audio capture driver and I'm hoping it will fix it.

usasma · 17 Jul 2012

Everything points to audio - but there's no specific solutions available.
Try running Driver Verifier acccording to these instructions: Driver Verifier Settings

Please post back to let us know how comfortable you are with registry edits - as the next step involves this suggested edit (from the dump file):

PROCESS_HAS_LOCKED_PAGES (76)
Caused by a driver not cleaning up correctly after an I/O.
Arguments:
Arg1: 0000000000000000, Locked memory pages found in process being terminated.
Arg2: fffffa800530b060, Process address.
Arg3: 00000000000000a9, Number of locked pages.
Arg4: 0000000000000000, Pointer to driver stacks (if enabled) or 0 if not.
Issue a !search over all of physical memory for the current process pointer.
This will yield at least one MDL which points to it. Then do another !search
for each MDL found, this will yield the IRP(s) that point to it, revealing
which driver is leaking the pages.
Otherwise, set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\TrackLockedPages to a DWORD 1 value and reboot. Then the system
will save stack traces so the guilty driver can be easily identified.
When you enable this flag, if the driver commits the error again you will
see a different bugcheck - DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (0xCB) -
which can identify the offending driver(s).

Please look over the driver table below and locate the drivers dated from 2009 and earlier.
Below the driver table is a list of links that you can use to locate information on the drivers.
Use that information to attempt to update all drivers dated from 2009 and earlier.
Antivirus and video drivers should be updated to the latest available version regardless of how old they are.

If the above steps don't stop the BSOD's, please zip up and upload any new memory dumps with your next post - and we'll see what we can figure out from there.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


DKbFltr.sys      Wed Mar 25 23:15:42 2009 (49CAF35E)
L1C62x64.sys     Mon Jul 27 03:04:36 2009 (4A6D5184)
NTIDrvr.sys      Tue Mar 24 23:09:39 2009 (49C9A073)
RTKVHD64.sys     Tue Jul 28 09:00:05 2009 (4A6EF655)
SynTP.sys        Thu Jun 18 22:33:58 2009 (4A3AF916)
UBHelper.sys     Mon Apr 27 04:48:19 2009 (49F57153)
amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA)
aswFsBlk.SYS     Tue Jul 03 12:13:12 2012 (4FF31A18)
aswMonFlt.sys    Tue Jul 03 12:13:24 2012 (4FF31A24)
aswSP.SYS        Tue Jul 03 12:14:23 2012 (4FF31A5F)
aswSnx.SYS       Tue Jul 03 12:14:27 2012 (4FF31A63)
aswTdi.SYS       Tue Jul 03 12:13:33 2012 (4FF31A2D)
aswrdr2.sys      Tue Jul 03 12:13:43 2012 (4FF31A37)
bcmwl664.sys     Fri Aug 21 20:17:40 2009 (4A8F3924)
dump_iaStor.sys  Tue Oct 13 14:15:56 2009 (4AD4C3DC)
iaStor.sys       Tue Oct 13 14:15:56 2009 (4AD4C3DC)
igdkmd64.sys     Wed Sep 02 14:54:15 2009 (4A9EBF57)
mwlPSDFilter.sys Tue Jun 02 06:07:30 2009 (4A24F9E2)
mwlPSDNServ.sys  Tue Jun 02 06:07:39 2009 (4A24F9EB)
mwlPSDVDisk.sys  Tue Jun 02 06:15:29 2009 (4A24FBC1)
stdriver64.sys   Thu Mar 17 20:17:45 2011 (4D82A4A9)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071612-20872-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Jul 16 11:56:47.183 2012 (UTC - 4:00)
System Uptime: 0 days 2:31:03.040
BugCheck 76, {0, fffffa800530b060, a9, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18026 )
PROCESS_NAME:  audiodg.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
BUGCHECK_STR:  0x76
FAILURE_BUCKET_ID:  X64_0x76_audiodg.exe_nt!_??_::NNGAKEGL::_string_+18026
Bugcheck code 00000076
Arguments 00000000`00000000 fffffa80`0530b060 00000000`000000a9 00000000`00000000
BiosVersion = V3.07
BiosReleaseDate = 02/10/2010
SystemManufacturer = Acer      
SystemProductName = Aspire 7715Z    
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

SoCalledComrad · 17 Jul 2012

Thank you for the help but it think that the solution was a bit more simple:

I simply uninstalled the video capture program (Debut Video Capture) and while uninstalling it asked me if I wanted to uninstall the sound tap driver and I said yes.

Since then I've been trying to provoke a blue screen but it seems like uninstalling the driver fixed the problem because I have been rendering and converting videos (which normally causes my bluescreens) and all my attempts were successful.

I already e-mailed the company that produces capture software, but they haven't responded yet.

I think I can mark this thread as solved.