Solved New Bsod Today

[warshiv]

Ok its been 2 days since the last help seemed to have fixed my Bsod issue, just today this happened tho attached the file hopefully its not the same thing again.

Cyberpower build Preinstalled win 7 x64
did a fresh install from supplied disc
amd phenom x6 t1055
8 gigs ram
2x ati 5770 vid cards
1t hardrive
system is 2 months old and cyberpower wants

 

[yowanvista]

BSOD caused by your ATI display driver

As it is the same BSOD error, there is a high probability that your graphic card is faulty

Possible causes:bad RAM/PSU, incorrect RAM timings/voltages, bad Graphics card, overheating, outdated driver

Uninstall the ATI driver then use driver sweeper to remove leftover ATI files
Guru3D - Driver Sweeper

Then reinstall your driver: ATI Radeon


This was likely caused by the following module: atikmpag.sys
Bugcheck code: 0x116 (0xFFFFFA8008021010, 0xFFFFF88006133F94, 0x0, 0x2)
Error: VIDEO_TDR_ERROR

 

[richc46]

Dont know about last time, but replace your driver
Atikmpag.sys file description
Productname: AMD driver
Company: Advanced Micro Devices, Inc.

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Documents[1].zip\Windows_NT6_BSOD_jcgriff2\102910-20607-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50
Debug session time: Fri Oct 29 11:46:38.162 2010 (GMT-4)
System Uptime: 0 days 0:20:57.066
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8008021010, fffff88006133f94, 0, 2}
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+6f94 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008021010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006133f94, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
------------------
 
FAULTING_IP: 
atikmpag+6f94
fffff880`06133f94 4883ec28        sub     rsp,28h
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`07035a58 fffff880`040d2ef8 : 00000000`00000116 fffffa80`08021010 fffff880`06133f94 00000000`00000000 : nt!KeBugCheckEx
fffff880`07035a60 fffff880`040d2c02 : fffff880`06133f94 fffffa80`08021010 fffffa80`06ef6300 fffffa80`06d17010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07035aa0 fffff880`04179f07 : fffffa80`08021010 00000000`00000000 fffffa80`06ef6300 fffffa80`06d17010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`07035ad0 fffff880`041a7d7e : fffffa80`ffffffff 00000000`00013a38 fffff880`07035c30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07035bb0 fffff880`0417529e : fffffa80`06d17010 ffffffff`feced300 fffffa80`06ef6300 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`07035bf0 fffff880`041a1e7a : 00000000`00000000 fffffa80`07014d50 00000000`00000080 fffffa80`06d17010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`07035d00 fffff800`02f2dc06 : 00000000`fffffc32 fffffa80`09ad9770 fffffa80`06cad9e0 fffffa80`09ad9770 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07035d40 fffff800`02c67c26 : fffff880`02dd5180 fffffa80`09ad9770 fffff880`02de0040 fffff880`01656c20 : nt!PspSystemThreadStartup+0x5a
fffff880`07035d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+6f94
fffff880`06133f94 4883ec28        sub     rsp,28h
SYMBOL_NAME:  atikmpag+6f94
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4cbfa04f
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------

It would have helped if you stayed in the same thread. The more pieces we have the more accurate the analysis
It appears that the driver was recently updated. The date is current. What was your last problem?

 

[warshiv]

Quick question other then running furmark and 3dmark on each card individually in each slot individually is there any other test i can perfrom to check the vid cards?

thanks

As yowan noted last time it was the Video driver and sound driver i redid the vid driver and removed the sound driver and it seemed to be fine for 2 days until just when i posted this message.

 

[richc46]

That is the test that we use. Dont know of others.

 

[warshiv]

Newest Bsod after reinstall of ati 10.10

crashed one mroe time just posting this to verify that its the card/pcie slot and not the drivers thanks for the info on this matter tho.

 

[CarlTR6]

This latest dump blames the Windows system Direct X Driver, more than likely not the real cause. It is another video error. Are you overclocking anything? If so, please return everything to default values.

All of your drivers are up to date except this one. I believe there is a later version available.

AtiPcie.sys Tue May 05 11:00:22 2009 - ATI PCIE Driver for ATI PCIE chipsetGlobal Provider of Innovative Graphics, Processors and Media Solutions | AMD

 

[warshiv]

Once again with a twist

Ok no overclocking never made it that far with the comp.
newest BSOD's 2 in a row with a single vid card in atm hoping its this vidcard or the slot its in now so i can finally rma this and get it fixed.

 

[CarlTR6]

Error code 1A, MEMORY_MANAGEMENT. Usual causes: Device driver, memory, kernel.

Error code 3B, SYSTEM_SERVICE_EXCEPTION. Usual causes: System service, Device driver, graphics driver, ?memory.

Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e3de50
Debug session time: Mon Nov  1 13:37:04.700 2010 (GMT-4)
System Uptime: 0 days 0:24:47.604
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 38, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000038
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  GoogleToolbarU

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880033088e0 -- (.trap 0xfffff880033088e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8008972dc0 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8a00251fab0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d76817 rsp=fffff88003308a70 rbp=0000000000000000
 r8=fffffa800987000c  r9=fffffa8007388048 r10=fffffa8006cd64b0
r11=fffffa8009ee3720 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiEmptyPageAccessLog+0xe7:
fffff800`02d76817 8b4138          mov     eax,dword ptr [rcx+38h] ds:00000000`00000038=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c1cb7a to fffff80002c70740

STACK_TEXT:  
fffff880`03308778 fffff800`02c1cb7a : 00000000`0000001a 00000000`00041287 00000000`00000038 00000000`00000000 : nt!KeBugCheckEx
fffff880`03308780 fffff800`02c6e82e : 00000000`00000000 00000000`00a6240c 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42ba5
fffff880`033088e0 fffff800`02d76817 : 00000000`00000000 fffffa80`06cd64f0 fffffa80`0987e060 fffffa80`0987e060 : nt!KiPageFault+0x16e
fffff880`03308a70 fffff800`02cf2aac : fffffa80`0987e060 00000003`00000000 00000000`00000000 fffffa80`08972dc0 : nt!MiEmptyPageAccessLog+0xe7
fffff880`03308ae0 fffff800`02c84ee2 : 00000000`000005d0 00000000`00000000 fffffa80`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x4972b
fffff880`03308b80 fffff800`02c85173 : 00000000`00000008 fffff880`03308c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03308bd0 fffff800`02f14c06 : fffffa80`06d258e0 00000000`00000080 fffffa80`06cad890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03308d40 fffff800`02c4ec26 : fffff880`02f64180 fffffa80`06d258e0 fffff880`02f6f040 89480000`0228249c : nt!PspSystemThreadStartup+0x5a
fffff880`03308d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42ba5
fffff800`02c1cb7a cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42ba5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002fb7d90, fffff8800bb8c090, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObDereferenceSecurityDescriptor+20 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002fb7d90, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800bb8c090, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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!ObDereferenceSecurityDescriptor+20
fffff800`02fb7d90 8b4610          mov     eax,dword ptr [rsi+10h]

CONTEXT:  fffff8800bb8c090 -- (.cxr 0xfffff8800bb8c090)
rax=fffff8800bb8ca88 rbx=0000000000000000 rcx=0000000000000100
rdx=0000000000000001 rsi=00000000000000e0 rdi=0000000000000000
rip=fffff80002fb7d90 rsp=fffff8800bb8ca60 rbp=fffffa800a4871d0
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff8800bb8cb38 r12=0000000000000001 r13=fffffa800a462060
r14=00000000770a8b00 r15=fffff8a0025325f0
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ObDereferenceSecurityDescriptor+0x20:
fffff800`02fb7d90 8b4610          mov     eax,dword ptr [rsi+10h] ds:002b:00000000`000000f0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  SearchProtocol

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f822c4 to fffff80002fb7d90

STACK_TEXT:  
fffff880`0bb8ca60 fffff800`02f822c4 : 00000000`00000000 fffffa80`0a4871d0 fffffa80`06d2b410 00000000`00000000 : nt!ObDereferenceSecurityDescriptor+0x20
fffff880`0bb8ca90 fffff800`02cc08ee : 00000000`00000000 fffffa80`0a462060 fffffa80`06d2b410 fffff880`0bb8cbc0 : nt!SeDefaultObjectMethod+0xa8
fffff880`0bb8cae0 fffff800`02fd1514 : fffffa80`0a462060 00000000`00000000 fffffa80`0a463060 00000000`00000000 : nt!ObfDereferenceObject+0x10e
fffff880`0bb8cb40 fffff800`02fd1414 : 00000000`000003d4 fffffa80`0a462060 fffff8a0`025325f0 00000000`000003d4 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`0bb8cbd0 fffff800`02cba993 : fffffa80`0a463060 fffff880`0bb8cca0 000007fe`fb800000 00000000`00000001 : nt!ObpCloseHandle+0x94
fffff880`0bb8cc20 00000000`76fbfe4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0020fa08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fbfe4a


FOLLOWUP_IP: 
nt!ObDereferenceSecurityDescriptor+20
fffff800`02fb7d90 8b4610          mov     eax,dword ptr [rsi+10h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObDereferenceSecurityDescriptor+20

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff8800bb8c090 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ObDereferenceSecurityDescriptor+20

BUCKET_ID:  X64_0x3B_nt!ObDereferenceSecurityDescriptor+20

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

I recommend that you test your RAM with Memetest following the instructions in this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Run Memetest for at least seven passes from both a warm boot and a cold boot after your computer has been off for a while. Each run will take 6-8 hours. Errors will show on you screen in red. Post your results.

If Memetest shows no errors, enable Driver Verifier following the instructions in this tutorial: Driver Verifier - Enable and Disable. Use your computer normally while Driver Verifier is running. Upload any and all dumps generated by Driver Verifier.

 

[warshiv]

Ok will do, already ran verifier once but didnt save the logs so ill run it again.
and ill run memtest as well thanks......

 

[CarlTR6]

You are welcome. Start with Memtest.

 

[warshiv]

Welp memtest crapped on on the 1st pass then i realized my voltage for my adata memory was low in the bios so i upeed the voltage and am now going to rerun memtest but figured i would post the past few crashes i have had.

BTW verifier wouldnt even run yet I tried.

guess ill be back after i see if memtest make its past the first sweep with the higher voltage.

 

[CarlTR6]

Do concentrate on your RAM problem until you get that solved. You will continue to get crashes into the RAM issues are resolved.

 

[zigzag3143]

Do concentrate on your RAM problem until you get that solved. You will continue to get crashes into the RAM issues are resolved.

Absolutely RAM. it is so bad we cant even read any info from the DMPS.

 

[warshiv]

Ok memtest passed with no errors 11 times after voltage increase.
Verifier wouldnt even run comp crashed i attached the newest files.
Hopefully im finally getting somewhere with this thanks again for all the help.

 

[CarlTR6]

Error code D5, DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL. Usual causes: Device driver

Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c52000 PsLoadedModuleList = 0xfffff800`02e8fe50
Debug session time: Wed Nov  3 12:52:02.909 2010 (GMT-4)
System Uptime: 0 days 0:00:19.252
Loading Kernel Symbols
...............................................................
..........................................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff98003136ed0, 0, fffff88004de41aa, 0}

Unable to load image \SystemRoot\system32\DRIVERS\usbfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys

Could not read faulting driver name
Probably caused by : usbfilter.sys ( usbfilter+41aa )

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

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

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff98003136ed0, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff88004de41aa, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efa0e0
 fffff98003136ed0 

FAULTING_IP: 
usbfilter+41aa
fffff880`04de41aa 8b4230          mov     eax,dword ptr [rdx+30h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD5

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002f76280 -- (.trap 0xfffff88002f76280)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88002f76478
rdx=fffff98003136ea0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004de41aa rsp=fffff88002f76410 rbp=0000000000000002
 r8=0000000000000000  r9=fffff88004de41a5 r10=0000000000000000
r11=fffff88002e88180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
usbfilter+0x41aa:
fffff880`04de41aa 8b4230          mov     eax,dword ptr [rdx+30h] ds:8180:fffff980`03136ed0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d42f14 to fffff80002cc2740

STACK_TEXT:  
fffff880`02f76118 fffff800`02d42f14 : 00000000`00000050 fffff980`03136ed0 00000000`00000000 fffff880`02f76280 : nt!KeBugCheckEx
fffff880`02f76120 fffff800`02cc082e : 00000000`00000000 fffff980`03174d80 fffffa80`08b9a000 fffff800`02cf533f : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`02f76280 fffff880`04de41aa : fffff880`02f76478 00000000`00000000 fffff980`03174d80 fffffa80`09791f40 : nt!KiPageFault+0x16e
fffff880`02f76410 fffff880`02f76478 : 00000000`00000000 fffff980`03174d80 fffffa80`09791f40 00000000`00000000 : usbfilter+0x41aa
fffff880`02f76418 00000000`00000000 : fffff980`03174d80 fffffa80`09791f40 00000000`00000000 fffff880`02f76478 : 0xfffff880`02f76478


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbfilter+41aa
fffff880`04de41aa 8b4230          mov     eax,dword ptr [rdx+30h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbfilter+41aa

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbfilter

IMAGE_NAME:  usbfilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b3082ae

FAILURE_BUCKET_ID:  X64_0xD5_VRF_usbfilter+41aa

BUCKET_ID:  X64_0xD5_VRF_usbfilter+41aa

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

5: kd> lmtsmn
start             end                 module name
fffff880`00f89000 fffff880`00fe0000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02b4d000 fffff880`02bd7000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`042e1000 fffff880`042f7000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`03e64000 fffff880`03e79000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00ff3000 fffff880`00ffe000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00ecd000 fffff880`00ed6000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00d92000 fffff880`00dbc000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`04608000 fffff880`04dde000   atikmdag atikmdag.sys Wed Oct 20 22:45:58 2010 (4CBFA966)
fffff880`04012000 fffff880`0405d000   atikmpag atikmpag.sys Wed Oct 20 22:07:11 2010 (4CBFA04F)
fffff880`0143a000 fffff880`01442000   AtiPcie  AtiPcie.sys  Tue May 05 11:00:22 2009 (4A005486)
fffff880`02aa1000 fffff880`02aa8000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03e2d000 fffff880`03e3e000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`02a41000 fffff880`02a6b000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00ca8000 fffff880`00d68000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01000000 fffff880`01030000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c4a000 fffff880`00ca8000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`010ee000 fffff880`01161000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`042d1000 fffff880`042e1000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`013e3000 fffff880`013f1000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03e0f000 fffff880`03e2d000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`03e00000 fffff880`03e0f000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`015e7000 fffff880`015fd000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01200000 fffff880`01209000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`013f1000 fffff880`013fd000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00c00000 fffff880`00c13000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`0405d000 fffff880`04151000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`04151000 fffff880`04197000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`0107c000 fffff880`01090000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01030000 fffff880`0107c000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`013d9000 fffff880`013e3000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`00dbc000 fffff880`00df6000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01161000 fffff880`011ab000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02c09000 fffff800`02c52000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`04197000 fffff880`041bb000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`015de000 fffff880`015e7000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`043ac000 fffff880`043bb000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00bb7000 fffff800`00bc1000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`03e79000 fffff880`03ebc000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`013ae000 fffff880`013c8000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01599000 fffff880`015c4000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`04200000 fffff880`04203d80   LGBusEnum LGBusEnum.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
fffff880`00c29000 fffff880`00c36000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`043bb000 fffff880`043ca000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`00d78000 fffff880`00d92000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02a6b000 fffff880`02a98000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
fffff880`02b06000 fffff880`02b11000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fe9000 fffff880`00ff3000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01090000 fffff880`010ee000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`03fef000 fffff880`03ffa000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`015cc000 fffff880`015de000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01447000 fffff880`01539000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0431b000 fffff880`04327000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`04327000 fffff880`04356000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`03f37000 fffff880`03f46000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`03ec3000 fffff880`03f08000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01539000 fffff880`01599000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`02b11000 fffff880`02b22000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03fe3000 fffff880`03fef000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02c52000 fffff800`0322e000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`0120b000 fffff880`013ae000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`02a98000 fffff880`02aa1000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`041bb000 fffff880`041eb000   nusb3xhc nusb3xhc.sys Tue Feb 23 21:10:16 2010 (4B848A88)
fffff880`03f11000 fffff880`03f37000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00e40000 fffff880`00e55000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e00000 fffff880`00e33000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00ec6000 fffff880`00ecd000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00d68000 fffff880`00d78000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013c8000 fffff880`013d9000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00c36000 fffff880`00c4a000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`042f7000 fffff880`0431b000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04356000 fffff880`04371000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`04371000 fffff880`04392000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`04392000 fffff880`043ac000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03f92000 fffff880`03fe3000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`02aeb000 fffff880`02af4000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02af4000 fffff880`02afd000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02afd000 fffff880`02b06000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01400000 fffff880`0143a000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`0427b000 fffff880`042d1000   Rt64win7 Rt64win7.sys Wed Jun 23 05:10:45 2010 (4C21CF95)
fffff880`0426f000 fffff880`0427b000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`03f46000 fffff880`03f63000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`015c4000 fffff880`015cc000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`043fb000 fffff880`043fc480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`02b40000 fffff880`02b4d000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`02b22000 fffff880`02b40000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`03f7e000 fffff880`03f92000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff880`03e3e000 fffff880`03e64000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`043ca000 fffff880`043dc000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`04dde000 fffff880`04ddff00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`0425e000 fffff880`0426f000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04de0000 fffff880`04ded000   usbfilter usbfilter.sys Tue Dec 22 03:26:22 2009 (4B3082AE)
fffff880`04ded000 fffff880`04df8000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04208000 fffff880`0425e000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`00e33000 fffff880`00e40000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`02aa8000 fffff880`02ab6000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`02ab6000 fffff880`02adb000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00e55000 fffff880`00e6a000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e6a000 fffff880`00ec6000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`011ab000 fffff880`011f7000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`03f63000 fffff880`03f7e000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`02adb000 fffff880`02aeb000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00ed6000 fffff880`00f7a000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f7a000 fffff880`00f89000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`03f08000 fffff880`03f11000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`00fe0000 fffff880`00fe9000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)

Unloaded modules:
fffff880`043ca000 fffff880`043fb000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`043ca000 fffff880`043fb000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000

This a Driver Verifier enabled dump and it blames usbfilter.sys, which is a Windows system driver and very unlikely to be the cause. The up time before this crash was only 19 seconds. This indicates a hardware problem. For now, turn off Driver Veririfier and see how your sytem does. Upload the next dump and we will take another look.

I still suspect a RAM problem. Try running Memtest from a cold boot after your computer has been off for a while. Post back with the results.

I also suggest that you run Prime95 following the instructions in this tutorial: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs).

 

[warshiv]

Ok memtest crapped out with a ton of errors running off of a cold boot guess im sending system back for a ram overhaul.

Never got verifier to run either tho.

 

[CarlTR6]

Don't worry about verifier, you found your problem. Good job! Let us know how your system does when you get your computer back.

 

[warshiv]

Will do thanks for all the help!

 

[CarlTR6]

You are very welcome.