Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD - ntoskrnl.exe+7cc40

26 Feb 2012   #1

Microsoft Windows 7 Home Premium 64-bit (SP1)
 
 
Random BSOD - ntoskrnl.exe+7cc40

Hi all, I have been getting BSODs since January 2012 while playing games or simply surfing the internet using Firefox or IE9.

My PC build is as follows:

AMD Phenom II X4 945
Biostar A880G+ motherboard
Kingston DDR3 PC1333 x 2 (4GB total)
Palit GTX460 768MB PCI-E
Western Digital HDD 500GB SATA
Windows 7 Home Premium 64bit (OEM DVD from retail shop)

Have just taken out 1 DRAM to isolate the problem; since there are some cases like mine that eventually suggest physical memory module problems in this forum.

Dump files and system health report html file attached.

My System SpecsSystem Spec
.

26 Feb 2012   #2

Windows 7 Ultimate x64
 
 

Hi Miki, welcome to SevenForums!

Four dumps, two memory management, one IRQL and one System Service Exception. There's a few things I want you to do!

First off, in your drivers list I noticed you have dtsoftbus01.sys, which is a driver for Daemon Tools, and Daemon Tools is a VERY large causer of BSODs in the Windows 7 environment. Please fully uninstall Daemon Tools and then restart your system.

Two tests I'd like you to run:

Quote:
Memtest:

Read the following to test your memory for errors.

Driver Verifier:

Read the following
to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80008fa0f0, ffff, 0}

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

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

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

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

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  MemeoDashboard

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000310a150 to fffff8000309ac40

STACK_TEXT:  
fffff880`092715f8 fffff800`0310a150 : 00000000`0000001a 00000000`00041790 fffffa80`008fa0f0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09271600 fffff800`030880ff : fffffa80`00000000 00000000`085fffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`092717c0 fffff800`03099ed3 : ffffffff`ffffffff fffff880`09271a90 fffff880`09271a98 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`092718c0 fffff800`03096470 : fffff800`033179af 00000000`00000010 00000000`00000086 fffff880`09271a88 : nt!KiSystemServiceCopyEnd+0x13
fffff880`09271a58 fffff800`033179af : 00000000`00000010 00000000`00000086 fffff880`09271a88 00000000`00000000 : nt!KiServiceLinkage
fffff880`09271a60 fffff800`03370b8d : 00000000`08500000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlFreeUserStack+0x27
fffff880`09271a90 fffff800`03370eed : fffff880`00000000 00000000`0777e300 00000000`7ef12000 00000000`00000000 : nt!PspExitThread+0x5dd
fffff880`09271b90 fffff800`03370ff5 : fffffa80`06e74b60 00000000`00000000 fffffa80`06e74b60 00000000`0777ec00 : nt!PspTerminateThreadByPointer+0x4d
fffff880`09271be0 fffff800`03099ed3 : fffffa80`06e74b60 fffff880`09271ca0 00000000`7ef12000 00000000`7ef12000 : nt!NtTerminateThread+0x45
fffff880`09271c20 00000000`771f184a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0777e348 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771f184a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+36024
fffff800`0310a150 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+36024

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

Followup: MachineOwner

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa8008125010, 2, 1, fffff80003195fe6}

Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa8008125010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003195fe6, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003311100
 fffffa8008125010 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReleaseConfirmedPageFileSpace+86
fffff800`03195fe6 480fb328        btr     qword ptr [rax],rbp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  CMStarterCore.

TRAP_FRAME:  fffff8800affa780 -- (.trap 0xfffff8800affa780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8006125010 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003195fe6 rsp=fffff8800affa910 rbp=0000000010000000
 r8=fffff8800affa940  r9=0000000fffffffff r10=fffffa8006540a28
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x86:
fffff800`03195fe6 480fb328        btr     qword ptr [rax],rbp ds:c000:fffffa80`06125010=ffffffffffffffff
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030de1e9 to fffff800030dec40

STACK_TEXT:  
fffff880`0affa638 fffff800`030de1e9 : 00000000`0000000a fffffa80`08125010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0affa640 fffff800`030dce60 : 00000000`74a07000 00000000`74a02000 00000000`77474000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0affa780 fffff800`03195fe6 : 00000000`75658000 00000000`00000000 fffffa80`060961f0 00000000`75659000 : nt!KiPageFault+0x260
fffff880`0affa910 fffff800`0308ea1b : 10000000`00000000 00000000`00000026 00000000`00000002 00000000`0000001c : nt!MiReleaseConfirmedPageFileSpace+0x86
fffff880`0affa990 fffff800`030af934 : fffffa80`06540a28 00000000`00000001 00000000`00000000 fffffa80`0000001c : nt! ?? ::FNODOBFM::`string'+0x21b4a
fffff880`0affaa10 fffff800`030b05a2 : 00000000`00000001 fffffa80`06540690 fffffa80`06540690 00000000`00000001 : nt!MiDeleteAllHashMappings+0xe4
fffff880`0affaa50 fffff800`033b4b1a : fffff8a0`0b54a4d0 00000000`00000001 00000000`00000000 fffffa80`064f3760 : nt!MmCleanProcessAddressSpace+0xa2
fffff880`0affaaa0 fffff800`0339648c : 00000000`00000002 00000000`00000001 00000000`7efdb000 00000000`00000000 : nt!PspExitThread+0x56a
fffff880`0affaba0 fffff800`030dded3 : fffffa80`06540690 00000000`00000002 fffffa80`064f3760 00000000`00302ce8 : nt!NtTerminateProcess+0x138
fffff880`0affac20 00000000`771e15da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e318 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771e15da


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReleaseConfirmedPageFileSpace+86
fffff800`03195fe6 480fb328        btr     qword ptr [rax],rbp

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+86

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86

BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86

Followup: MachineOwner

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {31, fffffa8003bba510, fffff88008162000, fffff8a00aa8711e}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+7271 )

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

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

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

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


BUGCHECK_STR:  0x1a_31

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  AcroRd32.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000332eb25 to fffff800030d1c40

STACK_TEXT:  
fffff880`09f2c0b8 fffff800`0332eb25 : 00000000`0000001a 00000000`00000031 fffffa80`03bba510 fffff880`08162000 : nt!KeBugCheckEx
fffff880`09f2c0c0 fffff800`033a9c37 : 00000000`00000000 00000000`00000000 00000000`0000000f fffff8a0`0aa85000 : nt! ?? ::NNGAKEGL::`string'+0x7271
fffff880`09f2c120 fffff800`030b37d2 : fffffa80`008c6f10 00000000`0000e400 fffffa80`0086c3d0 fffffa80`008d5ee0 : nt!MiRelocateImagePfn+0xf7
fffff880`09f2c180 fffff800`033add21 : fffffa80`03ddfc80 fffff6fc`40040a98 fffff8a0`00000002 00000000`00000000 : nt!MiValidateImagePages+0x362
fffff880`09f2c230 fffff800`033ade60 : ffffffff`ffffffff 00000000`00000001 fffff8a0`0aa85000 00000000`0000002a : nt!MiSwitchBaseAddress+0x61
fffff880`09f2c260 fffff800`033ce9ff : 00000000`00000004 00000000`00000080 00000000`01000000 00000000`01000000 : nt!MiRelocateImageAgain+0x100
fffff880`09f2c2b0 fffff800`033ad596 : fffff880`09f2c500 fffff8a0`0b201710 fffff880`09f2c5a8 fffff880`09f2c4f8 : nt!MmCreateSection+0x2df
fffff880`09f2c4b0 fffff800`0352d655 : fffff8a0`0498bab8 00000000`00000000 00000000`00000001 00000002`00000000 : nt!NtCreateSection+0x171
fffff880`09f2c530 fffff800`0352da07 : 00000000`00000010 fffff8a0`0b144550 fffff880`09f2c6c0 00000000`0000002c : nt!PfSnGetSectionObject+0x2d5
fffff880`09f2c620 fffff800`0352de37 : fffff880`09f2c740 00000000`00000001 00000000`00000000 00000000`00000000 : nt!PfSnPrefetchSections+0x247
fffff880`09f2c710 fffff800`0352e25f : 00000210`b6002c91 fffffa80`03fbcb30 fffff8a0`0b201000 00000000`00000000 : nt!PfSnPrefetchScenario+0x187
fffff880`09f2c980 fffff800`0342d2df : 00000000`00000000 00000000`97743aa9 fffffa80`040046a0 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f
fffff880`09f2ca50 fffff800`033bffb8 : fffffa80`03f61b60 fffffa80`040046a0 00000000`14050a00 00000000`fffde000 : nt! ?? ::NNGAKEGL::`string'+0x513d0
fffff880`09f2ca80 fffff800`030c3715 : fffff880`02f63180 00000000`00000000 fffff800`033bfe70 fffffa80`03f61b60 : nt!PspUserThreadStartup+0x148
fffff880`09f2cae0 fffff800`030c3697 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffff880`09f2cc20 00000000`76eec500 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
00000000`000dfae8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76eec500


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::NNGAKEGL::`string'+7271
fffff800`0332eb25 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::NNGAKEGL::`string'+7271

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+7271

BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+7271

Followup: MachineOwner

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880130358c5, fffff88003901990, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Rotate+c1 )

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

1: 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: fffff880130358c5, Address of the instruction which caused the bugcheck
Arg3: fffff88003901990, 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: 
dxgmms1!VIDMM_PROCESS_HEAP::Rotate+c1
fffff880`130358c5 f60601          test    byte ptr [rsi],1

CONTEXT:  fffff88003901990 -- (.cxr 0xfffff88003901990)
rax=fffffa8006eb57c0 rbx=fffffa8006eb57c0 rcx=0000000000000001
rdx=1000000000000000 rsi=1000000000000000 rdi=0000000000000003
rip=fffff880130358c5 rsp=fffff88003902370 rbp=0000000000000000
 r8=0000000000000003  r9=0000000000000000 r10=fffff8000300f000
r11=0000000000000175 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010297
dxgmms1!VIDMM_PROCESS_HEAP::Rotate+0xc1:
fffff880`130358c5 f60601          test    byte ptr [rsi],1 ds:002b:10000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Dragona.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880130358c5

STACK_TEXT:  
fffff880`03902370 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Rotate+0xc1


FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::Rotate+c1
fffff880`130358c5 f60601          test    byte ptr [rsi],1

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::Rotate+c1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff88003901990 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_PROCESS_HEAP::Rotate+c1

BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_PROCESS_HEAP::Rotate+c1

Followup: MachineOwner
My System SpecsSystem Spec
29 Feb 2012   #3

Microsoft Windows 7 Home Premium 64-bit (SP1)
 
 

Quote   Quote: Originally Posted by ePeen View Post
Hi Miki, welcome to SevenForums!

Four dumps, two memory management, one IRQL and one System Service Exception. There's a few things I want you to do!

First off, in your drivers list I noticed you have dtsoftbus01.sys, which is a driver for Daemon Tools, and Daemon Tools is a VERY large causer of BSODs in the Windows 7 environment. Please fully uninstall Daemon Tools and then restart your system.

Two tests I'd like you to run:

Memtest:

Read the following to test your memory for errors.

Driver Verifier:

Read the following
to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.
Thanks ePeen for the welcome and your advice.

There were no problems detected for both memory sticks in all available memory slots (7 passes).

However, when it came to the Driver Verifier, I immediately got a BSOD upon enabling the verifier and rebooting afterwards.

I had checked everything that's not from Microsoft under the Driver verifier's loaded drivers list - which includes AMD drivers, third-party anti-virus and so on. Daemon tools was also uninstalled before I tried Memtest and Driver verifier.

I really hope to find the driver(s) responsible for this BSOD.

By the way, what's the code that you have attached in your previous post? Do I need to do something with it?
My System SpecsSystem Spec
.


02 Mar 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\Miki07\022912-23899-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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03013000 PsLoadedModuleList = 0xfffff800`03258670
Debug session time: Tue Feb 28 23:04:34.215 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:12.994
Loading Kernel Symbols
...............................................................
..............................................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff98009f62e40, 0, fffff88002ca11aa, 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
---------

3: 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: fffff98009f62e40, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff88002ca11aa, 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 fffff800032c2100
 fffff98009f62e40 

FAULTING_IP: 
usbfilter+41aa
fffff880`02ca11aa 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:  fffff88003179280 -- (.trap 0xfffff88003179280)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003179478
rdx=fffff98009f62e10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002ca11aa rsp=fffff88003179410 rbp=0000000000000002
 r8=0000000000000000  r9=fffff88002ca11a5 r10=0000000000000100
r11=fffff88002fd5180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
usbfilter+0x41aa:
fffff880`02ca11aa 8b4230          mov     eax,dword ptr [rdx+30h] ds:5180:fffff980`09f62e40=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000303b9fc to fffff8000308fc40

STACK_TEXT:  
fffff880`03179118 fffff800`0303b9fc : 00000000`00000050 fffff980`09f62e40 00000000`00000000 fffff880`03179280 : nt!KeBugCheckEx
fffff880`03179120 fffff800`0308dd6e : 00000000`00000000 fffff980`09f62e40 fffffa80`041b6000 fffff980`09f64d80 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`03179280 fffff880`02ca11aa : fffff880`03179478 00000000`00000000 fffff980`09f64d80 fffffa80`03f85010 : nt!KiPageFault+0x16e
fffff880`03179410 fffff880`03179478 : 00000000`00000000 fffff980`09f64d80 fffffa80`03f85010 00000000`00000000 : usbfilter+0x41aa
fffff880`03179418 00000000`00000000 : fffff980`09f64d80 fffffa80`03f85010 00000000`00000000 fffff880`03179478 : 0xfffff880`03179478


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbfilter+41aa
fffff880`02ca11aa 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
---------
Points to a USB device causing the crashes.

What devices do you use through USB?

Disable verifier first. Then proceed with USB Driver - General Fix for Problems to start.
My System SpecsSystem Spec
03 Mar 2012   #5

Microsoft Windows 7 Home Premium 64-bit (SP1)
 
 

Quote   Quote: Originally Posted by writhziden;1821544Points to a USB device causing the crashes.

What devices do you use through USB?

Disable verifier first. Then proceed with [URL
http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html[/URL] to start.
Hi writhziden

I had uninstalled the current chipset driver along with the usb filter driver. I went to download the latest chipset driver for my motherboard at AMD website since the one at Biostar's website is quite outdated. According to the description for the usb filter driver during custom installation of the new chipset driver, the usb filter driver is actually meant for legacy usb compatibility (1.0 and 1.1) and since I don't have any hardware that uses such USB standards it should be ok not to install it at all from now on.

Most of my PC peripherals are connected to USB (not including the front panel ones). Keyboard, mouse, printer, web camera, I think.

I did everything as laid out in that link you gave me - including updated drivers for my printer and webcam.

What do I do next?
My System SpecsSystem Spec
03 Mar 2012   #6

Windows 7 Home Premium 64 Bit
 
 

See how the system responds. Do your normal routine for a while (a few days or however long it usually takes to get a crash), and report back whether the problems appears to be solved. You will probably want to test it out more intensively than that before being absolutely sure it is solved, but that should give some indication to how the system is performing.
My System SpecsSystem Spec
03 Mar 2012   #7

Microsoft Windows 7 Home Premium 64-bit (SP1)
 
 

Do I need to enable the driver verifier? What do you mean by testing it out more intensively? Any specific guide I can follow?
My System SpecsSystem Spec
03 Mar 2012   #8

Windows 7 Home Premium 64 Bit
 
 

No, you do not need to enable Verifier at this time. By testing it out more intensively, I just mean testing it for more than just a few days running your normal routine; a few weeks of normal use would be better.
My System SpecsSystem Spec
04 Mar 2012   #9

Microsoft Windows 7 Home Premium 64-bit (SP1)
 
 

Ok, will do so and get back to you if something comes up.
My System SpecsSystem Spec
04 Mar 2012   #10

Windows 7 Home Premium 64 Bit
 
 

Good plan. I'll check back in a few weeks if I do not hear back, as well. Best of luck!
My System SpecsSystem Spec
Reply

 Random BSOD - ntoskrnl.exe+7cc40




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 02:41 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33