BSOD sometime on my system

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\symetric\030412-19234-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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e61000 PsLoadedModuleList = 0xfffff800`030a6670
Debug session time: Sun Mar  4 06:50:20.748 2012 (UTC - 7:00)
System Uptime: 1 days 12:10:07.606
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffff8a00c01a8e0, fffff8a00c01b6d0, 3ddf9bcc}

GetPointerFromAddress: unable to read from fffff80003110100
Probably caused by : ntkrnlmp.exe ( nt!IopDeleteFile+168 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a00c01a8e0, The pool entry we were looking for within the page.
Arg3: fffff8a00c01b6d0, The next pool entry.
Arg4: 000000003ddf9bcc, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffff8a00c01a8e0 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000300bcae to fffff80002eddc40

STACK_TEXT:  
fffff880`031fca18 fffff800`0300bcae : 00000000`00000019 00000000`00000020 fffff8a0`0c01a8e0 fffff8a0`0c01b6d0 : nt!KeBugCheckEx
fffff880`031fca20 fffff800`031da3d8 : fffffa80`047e0940 00000000`00000001 fffffa80`61a19383 fffffa80`047e0940 : nt!ExDeferredFreePool+0x12da
fffff880`031fcad0 fffff800`02ee7af4 : 00000000`00000001 00000000`00000000 fffffa80`039f0f30 00000000`00000000 : nt!IopDeleteFile+0x168
fffff880`031fcb60 fffff800`0317d285 : 00000000`00000000 00000000`00084081 fffffa80`05d7c540 fffffa80`0765ad60 : nt!ObfDereferenceObject+0xd4
fffff880`031fcbc0 fffff800`02f2b18d : fffffa80`05d7c548 00000000`00000001 00000000`00000000 03555209`00000631 : nt!MiSegmentDelete+0xa1
fffff880`031fcc00 fffff800`02f2b051 : 00000000`00000000 00000000`00000080 fffffa80`039e0040 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131
fffff880`031fccc0 fffff800`03178fee : 82287000`0002d700 00020000`00002000 2549c880`00880500 12003200`00142901 : nt!MiDereferenceSegmentThread+0x10d
fffff880`031fcd40 fffff800`02ecf5e6 : fffff880`02f63180 fffffa80`039f8400 fffff880`02f6dfc0 7d3f3f3f`9f7f7f3f : nt!PspSystemThreadStartup+0x5a
fffff880`031fcd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!IopDeleteFile+168
fffff800`031da3d8 488b8bb0000000  mov     rcx,qword ptr [rbx+0B0h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!IopDeleteFile+168

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x19_20_nt!IopDeleteFile+168

BUCKET_ID:  X64_0x19_20_nt!IopDeleteFile+168

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

That crash indicates an underlying driver problem. Unfortunately, the analysis does not indicate which driver. It may be the USB receiver as suspected. The only other suspect driver I really see is:

Code:

ctac32k	fffff880`04ad7000	fffff880`04b85000	Wed Jul 02 02:38:22 2008 (486b3e7e)	00095082		ctac32k.sys

ctac32k.sys
but we should focus on seeing if the problems are resolved with the wired mouse and keyboard and RAM change. We don't want to address too many things at once.

writhziden said:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [D:\Kingston\BSODDmpFiles\symetric\030412-19234-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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e61000 PsLoadedModuleList = 0xfffff800`030a6670
Debug session time: Sun Mar  4 06:50:20.748 2012 (UTC - 7:00)
System Uptime: 1 days 12:10:07.606
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 19, {20, fffff8a00c01a8e0, fffff8a00c01b6d0, 3ddf9bcc}
 
GetPointerFromAddress: unable to read from fffff80003110100
Probably caused by : ntkrnlmp.exe ( nt!IopDeleteFile+168 )
 
Followup: MachineOwner
---------
 
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a00c01a8e0, The pool entry we were looking for within the page.
Arg3: fffff8a00c01b6d0, The next pool entry.
Arg4: 000000003ddf9bcc, (reserved)
 
Debugging Details:
------------------
 
 
BUGCHECK_STR:  0x19_20
 
POOL_ADDRESS:  fffff8a00c01a8e0 
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
LAST_CONTROL_TRANSFER:  from fffff8000300bcae to fffff80002eddc40
 
STACK_TEXT:  
fffff880`031fca18 fffff800`0300bcae : 00000000`00000019 00000000`00000020 fffff8a0`0c01a8e0 fffff8a0`0c01b6d0 : nt!KeBugCheckEx
fffff880`031fca20 fffff800`031da3d8 : fffffa80`047e0940 00000000`00000001 fffffa80`61a19383 fffffa80`047e0940 : nt!ExDeferredFreePool+0x12da
fffff880`031fcad0 fffff800`02ee7af4 : 00000000`00000001 00000000`00000000 fffffa80`039f0f30 00000000`00000000 : nt!IopDeleteFile+0x168
fffff880`031fcb60 fffff800`0317d285 : 00000000`00000000 00000000`00084081 fffffa80`05d7c540 fffffa80`0765ad60 : nt!ObfDereferenceObject+0xd4
fffff880`031fcbc0 fffff800`02f2b18d : fffffa80`05d7c548 00000000`00000001 00000000`00000000 03555209`00000631 : nt!MiSegmentDelete+0xa1
fffff880`031fcc00 fffff800`02f2b051 : 00000000`00000000 00000000`00000080 fffffa80`039e0040 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131
fffff880`031fccc0 fffff800`03178fee : 82287000`0002d700 00020000`00002000 2549c880`00880500 12003200`00142901 : nt!MiDereferenceSegmentThread+0x10d
fffff880`031fcd40 fffff800`02ecf5e6 : fffff880`02f63180 fffffa80`039f8400 fffff880`02f6dfc0 7d3f3f3f`9f7f7f3f : nt!PspSystemThreadStartup+0x5a
fffff880`031fcd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nt!IopDeleteFile+168
fffff800`031da3d8 488b8bb0000000  mov     rcx,qword ptr [rbx+0B0h]
 
SYMBOL_STACK_INDEX:  2
 
SYMBOL_NAME:  nt!IopDeleteFile+168
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
 
FAILURE_BUCKET_ID:  X64_0x19_20_nt!IopDeleteFile+168
 
BUCKET_ID:  X64_0x19_20_nt!IopDeleteFile+168
 
Followup: MachineOwner
---------

That crash indicates an underlying driver problem. Unfortunately, the analysis does not indicate which driver. It may be the USB receiver as suspected. The only other suspect driver I really see is:

Code:

ctac32k    fffff880`04ad7000    fffff880`04b85000    Wed Jul 02 02:38:22 2008 (486b3e7e)    00095082        ctac32k.sys

ctac32k.sys
but we should focus on seeing if the problems are resolved with the wired mouse and keyboard and RAM change. We don't want to address too many things at once.

Ok, so I leave my wired mouse and KB plug. Only 4 gig RAM installed. and I dont plug any other USB device ???

Do what you normally do and see how things go. You don't have to avoid all USB devices, just the receiver that seems to be causing the problems for now. If you get another USB related crash with a different device, then we can consider keeping all devices removed except the currently connected USB mouse.

Dave76 said:

Good info on the settings.

As writhziden mentioned, let's see if removing the wireless receiver shows any difference.

I would update the ctac32k.sys, Creative Audio Driver, it is out of date and may be causing issues.

Writhziden, when I was not logged on the forum and check DAVE76 reply, when we pass the mouse over the word "driver" that link us to the site I mentioned before in my post (the DRIVER Scanner from lutility.com)

Ok now, Dave76

We try to update the ctac32k.sy driver but it is the last one I got...we think..

Dated : May 5, 2010

This morning, it seem I will have a BSOD soon lol... I think. I try to open my mail inbox by MSN MEssenger and it pop me a error (that I dont rememer exactly) like Windows cannot execute..." Last time I saw that error, I got a BSOD 10 min after...

But I re-try to open the inbox mailbox from MSN and it is ok.

Last night, I plugged my Xbox360 receiver in one of the USB Port to play a game, after I unplugged it.

We will see...maybe all what I say will never happen lol..

Let us know whether you crash as suspected.

Also, if you get another error, let us know the exact message. Thanks. :)

Hi guys, just to tell you that I'm not dead... I still got any BSOD since 1 week now....

I have onlye my kb and mouse plugged and still have 4 gig of ram... must be my wireless keyboard or mouse that cause the problem...

I wonder if I can put back my other 4 gig of ram and plug my 8 usb switch in my computer ?!...

I would recommend that you add things back one peripheral (piece of hardware) at a time. Try to determine what peripheral is causing the crashes.