Solved BSOD while converting video files

[mike212]

I cannot generate a system health report even though the Performance Logs & Alerts service is running (An error occured while attempting to generate the report). I've attached a dump of the BSOD files. I've had 4 BSOD's within the past few days. The two most recently were back to back. As with most computer owners, I install new drivers all the time. I recently installed new video card drivers, audio card drivers, etc. Your guess is as good as mine as far as new drivers go.

The BSOD is reproducible if I open up the video conversion app and run it to a certain point. It also occurs with itunes open. Occasionally my PC will hang after I successfully sync my iPod.

- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? yes
- an OEM or full retail version? oem

- What is the age of system (hardware)? 3+ years
- What is the age of OS installation (have you re-installed the OS?) 3+ years

Thanks for your help!

 

[mike212]

Here is a report of my hardware with AIDA

 

[writhziden]

Problem Devices:

AMD High Definition Audio Device	HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1002\5&2BD0AD1&0&0001	This device is disabled.
avast! Network Shield Support	ROOT\LEGACY_ASWTDI\0000	This device is not present, is not working properly, or does not have all its drivers installed.

Did you intentionally disable the AMD HD audio? What about avast!?


Security Software: If you disabled avast! intentionally, enable it again. It is not a likely culprit to the crashes.

Possible out of date drivers:

[B][COLOR="Red"]ASACPI	fffff880`04df0000	fffff880`04df8000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys[/COLOR][/B]
[B][COLOR="Red"]ahcix64s	fffff880`01af4000	fffff880`01b44000	Tue Mar 17 00:38:19 2009 (49bf455b)	00038ade		ahcix64s.sys
dump_ahcix64s	fffff880`09ba8000	fffff880`09bf8000	Tue Mar 17 00:38:19 2009 (49bf455b)	00038ade		dump_ahcix64s.sys
amdsbs	fffff880`0111b000	fffff880`01162000	Fri Mar 20 12:36:03 2009 (49c3e213)	0003938a		amdsbs.sys[/COLOR][/B]
AsUpIO	fffff880`04b9a000	fffff880`04ba0000	Sun Jul 05 20:21:38 2009 (4a515fb2)	0000edf8		AsUpIO.sys

Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:

1. Going to the Asus motherboard support site
   When you reach the website:
2. Click Downloads -> Windows 7 64bit
3. Scroll down the page and click Utilities
4. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
5. Search for "ATK0110" (without quotes)
6. Download and install the driver.
7. After installation is complete, verify that it installed correctly.
   • Click Start Menu
   • Click My Computer
   • Go to C:\WIndows\System32\drivers\
   • Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)

Thanks to JMH and zigzag3143 for the above information.
ahcix64s.sys -> Downloads -> Windows 7 64bit -> Others -> RAID Controller Driver
dump_ahcix64s.sys -> Downloads -> Windows 7 64bit -> Others -> RAID Controller Driver
amdsbs.sys -> Downloads -> Windows 7 64bit -> Others -> RAID Controller Driver (not sure about this one???)
AsUpIO.sys

[list=1][*]
Loading Dump File [D:\Kingston\BSODDmpFiles\mike212\Windows_NT6_BSOD_jcgriff2\033112-33493-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03249000 PsLoadedModuleList = 0xfffff800`0348d650
Debug session time: Sat Mar 31 03:59:13.053 2012 (UTC - 6:00)
System Uptime: 0 days 0:06:57.645
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8000329dc90, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!RtlpVirtualUnwind+714 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8000329dc90, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!RtlpVirtualUnwind+714
fffff800`0329dc90 493b09          cmp     rcx,qword ptr [r9]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034f7100
 0000000000000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SABnzbd.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800bab22e0 -- (.trap 0xfffff8800bab22e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffdda2ff00 rbx=0000000000000000 rcx=00000101dda2ff05
rdx=fffff8800bab2ca7 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000329dc90 rsp=fffff8800bab2478 rbp=fffff8800bab2ca0
 r8=fffffa8003368840  r9=0000000000000000 r10=fffffffffff3c70a
r11=fffffa80048bc480 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
nt!RtlpVirtualUnwind+0x714:
fffff800`0329dc90 493b09          cmp     rcx,qword ptr [r9] ds:23b4:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003310a08 to fffff800032c5d40

STACK_TEXT:  
fffff880`0bab1a58 fffff800`03310a08 : 00000000`0000001e ffffffff`c0000005 fffff800`0329dc90 00000000`00000000 : nt!KeBugCheckEx
fffff880`0bab1a60 fffff800`032c53c2 : fffff880`0bab2238 fffffa80`02dda100 fffff880`0bab22e0 fffffa80`04902b60 : nt! ?? ::FNODOBFM::`string'+0x48d2d
fffff880`0bab2100 fffff800`032c3f3a : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`02dda100 : nt!KiExceptionDispatch+0xc2
fffff880`0bab22e0 fffff800`0329dc90 : fffff880`02f42a61 fffff880`0bab2970 fffff880`0bab2790 fffff880`0bab2790 : nt!KiPageFault+0x23a
fffff880`0bab2478 fffff880`0bab24f8 : fffffa80`048bc450 00000000`00000000 fffffa80`0488fba0 00000000`00000000 : nt!RtlpVirtualUnwind+0x714
fffff880`0bab2508 fffffa80`048bc450 : 00000000`00000000 fffffa80`0488fba0 00000000`00000000 00000000`065db024 : 0xfffff880`0bab24f8
fffff880`0bab2510 00000000`00000000 : fffffa80`0488fba0 00000000`00000000 00000000`065db024 fffffa80`048bc450 : 0xfffffa80`048bc450


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!RtlpVirtualUnwind+714
fffff800`0329dc90 493b09          cmp     rcx,qword ptr [r9]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!RtlpVirtualUnwind+714

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!RtlpVirtualUnwind+714

BUCKET_ID:  X64_0x1E_c0000005_nt!RtlpVirtualUnwind+714

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\mike212\Windows_NT6_BSOD_jcgriff2\033112-33009-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03249000 PsLoadedModuleList = 0xfffff800`0348d650
Debug session time: Sat Mar 31 03:52:41.834 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:26.426
Loading Kernel Symbols
.......................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8003007038, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8003007038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`033876f0 fffff800`0350acb9 : fffffa80`03007010 fffffa80`018c4040 fffffa80`00000005 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03387c10 fffff800`033eb687 : fffffa80`03007010 fffff800`034652b8 fffffa80`018c4040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03387c40 fffff800`03352a35 : fffff800`034c6ac0 00000000`00000001 fffffa80`02840820 fffffa80`018c4040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03387c80 fffff800`032cf471 : fffff880`01030e00 fffff800`03352a10 fffffa80`018c4000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03387cb0 fffff800`0355ff7a : 00000000`00000000 fffffa80`018c4040 00000000`00000080 fffffa80`018b2040 : nt!ExpWorkerThread+0x111
fffff880`03387d40 fffff800`032b69c6 : fffff880`03163180 fffffa80`018c4040 fffff880`0316dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03387d80 00000000`00000000 : fffff880`03388000 fffff880`03382000 fffff880`033870d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

Followup: MachineOwner
---------


[/list]

1. Caused by Sabnzbd.exe. I am not familiar with this program. Are you?
2. Stop 0x124 hardware crash

See http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html and use the following to supplement the help in that link:

• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[mike212]

Turns out the problem was in my bios. I enabled "advanced clock calibration" and the setting to turn on all 4 cores of the CPU. The BSOD would occur. Once I disabled advanced clock calibration - no more BSOD. Thanks writhziden!

 

[writhziden]

No problem. Glad it is resolved now. You may mark the thread solved if you wish.