Possible out of date drivers:
Code:
itecir fffff880`01056000 fffff880`010b2000 Mon Mar 09 02:58:47 2009 (49b4da47) 0000f5e6 itecir.sys
k57nd60a fffff880`05a00000 fffff880`05a51000 Sun Jun 07 01:36:34 2009 (4a2b6e02) 000539bb k57nd60a.sys
risdpe64 fffff880`05ef2000 fffff880`05f0b000 Wed Jul 01 03:31:57 2009 (4a4b2d0d) 000184aa risdpe64.sys
rimspe64 fffff880`05f0b000 fffff880`05f24000 Wed Jul 01 17:54:49 2009 (4a4bf749) 0001665d rimspe64.sys
rixdpe64 fffff880`05f24000 fffff880`05f7a000 Sat Jul 04 04:27:00 2009 (4a4f2e74) 000196e3 rixdpe64.sys
itecir.sys
k57nd60a.sys
risdpe64.sys
rimspe64.sys
rixdpe64.sys
I suspect your driver in red above is the culprit of the crashes. Do you have Bluetooth drivers through Broadcom installed by chance?
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\Bobashnabala\032212-26067-01 m.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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c1f000 PsLoadedModuleList = 0xfffff800`02e63650
Debug session time: Wed Mar 21 21:57:02.226 2012 (UTC - 6:00)
System Uptime: 7 days 4:38:48.694
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffffffb2, 0, fffff80002ca7859, 0}
Could not read faulting driver name
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpIdleTimeWorker+63 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffffffffffb2, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ca7859, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ecd100
ffffffffffffffb2
FAULTING_IP:
nt!IoReuseIrp+19
fffff800`02ca7859 0fb75902 movzx ebx,word ptr [rcx+2]
MM_INTERNAL_CODE: 0
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff880035b6a70 -- (.trap 0xfffff880035b6a70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880035b6c28 rbx=0000000000000000 rcx=ffffffffffffffb0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ca7859 rsp=fffff880035b6c00 rbp=fffffa80043e2c80
r8=0000000000000000 r9=0000000000000000 r10=0000000000000024
r11=fffffa8007c76db8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!IoReuseIrp+0x19:
fffff800`02ca7859 0fb75902 movzx ebx,word ptr [rcx+2] ds:0d78:ffffffff`ffffffb2=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c4825c to fffff80002c9bd40
STACK_TEXT:
fffff880`035b6908 fffff800`02c4825c : 00000000`00000050 ffffffff`ffffffb2 00000000`00000000 fffff880`035b6a70 : nt!KeBugCheckEx
fffff880`035b6910 fffff800`02c99e6e : 00000000`00000000 ffffffff`ffffffb2 00000000`00000000 fffffa80`043e2b30 : nt! ?? ::FNODOBFM::`string'+0x456cf
fffff880`035b6a70 fffff800`02ca7859 : fffffa80`00000019 fffff880`035b6c58 00000000`00000008 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`035b6c00 fffff880`0569aadf : fffffa80`043e2b30 fffffa80`043e2c80 ffffffff`ffffffb0 00000000`00000000 : nt!IoReuseIrp+0x19
fffff880`035b6c30 fffff800`02f91723 : fffffa80`043e2b30 fffff800`02e3b2b8 fffffa80`03c22680 fffffa80`03c22680 : HIDCLASS!HidpIdleTimeWorker+0x63
fffff880`035b6c80 fffff800`02ca5471 : fffffa80`070b2000 fffff800`02f91701 fffffa80`54515700 fffffa80`03c22680 : nt!IopProcessWorkItem+0x23
fffff880`035b6cb0 fffff800`02f35f7a : 00000000`00000000 fffffa80`03c22680 00000000`00000080 fffffa80`03c0eb30 : nt!ExpWorkerThread+0x111
fffff880`035b6d40 fffff800`02c8c9c6 : fffff880`033d5180 fffffa80`03c22680 fffff880`033dffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`035b6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
HIDCLASS!HidpIdleTimeWorker+63
fffff880`0569aadf 4885f6 test rsi,rsi
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: HIDCLASS!HidpIdleTimeWorker+63
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: HIDCLASS
IMAGE_NAME: HIDCLASS.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7a665
FAILURE_BUCKET_ID: X64_0x50_HIDCLASS!HidpIdleTimeWorker+63
BUCKET_ID: X64_0x50_HIDCLASS!HidpIdleTimeWorker+63
Followup: MachineOwner
---------
This crash usually means USB devices or Bluetooth devices are not functioning properly. Do you remember what you were doing at the time of the crash?
Check your device manager under Human Interface Devices for Bluetooth devices. See if you can find an update for the device. If you do not use Bluetooth, you can also disable the device by right clicking it and clicking disable.
To get to Device Manager: Start Menu -> Right click Computer -> Manage -> Device Manager from the list on the left.
Alternatively: Start Menu -> Control Panel -> Hardware and Sound -> Device Manager