BSOD oh god why

trinkk · May 9, 2010

Hi, I've been having random bsods for a while now and they're becoming more frequent. Please help me solve this infuriating problem. I've attached my minidumps, thanks.

zigzag3143 · May 9, 2010

trinkk said:
Hi, I've been having random bsods for a while now and they're becoming more frequent. Please help me solve this infuriating problem. I've attached my minidumps, thanks.

Almost all of these were caused by memory corruption. the ones that werent still have a memory component.

I would download memtestx86 and run it for at least 5 passes

let us know if you need help

Ken

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Minidumps\040910-17752-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a07000 PsLoadedModuleList = 0xfffff800`02c44e50
Debug session time: Fri Apr  9 19:35:18.238 2010 (GMT-4)
System Uptime: 0 days 0:01:10.892
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6ec5000e860, 0, fffff80002a94c9e, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDispatchFault+de )

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

1: 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: fffff6ec5000e860, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002a94c9e, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002caf0e0
 fffff6ec5000e860 

FAULTING_IP: 
nt!MiDispatchFault+de
fffff800`02a94c9e 488b1c29        mov     rbx,qword ptr [rcx+rbp]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  MOM.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88007c52820 -- (.trap 0xfffff88007c52820)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=d8a001d0ced80400 rbx=0000000000000000 rcx=fffff68000000000
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a94c9e rsp=fffff88007c529b0 rbp=0000006c5000e860
 r8=ffffd8a001d0ced8  r9=0000000000000000 r10=0000000fffffffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiDispatchFault+0xde:
fffff800`02a94c9e 488b1c29        mov     rbx,qword ptr [rcx+rbp] ds:2121:fffff6ec`5000e860=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002af6b91 to fffff80002a78f00

STACK_TEXT:  
fffff880`07c526b8 fffff800`02af6b91 : 00000000`00000050 fffff6ec`5000e860 00000000`00000000 fffff880`07c52820 : nt!KeBugCheckEx
fffff880`07c526c0 fffff800`02a76fee : 00000000`00000000 000007fe`f55b2500 fffffa80`01cabe00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`07c52820 fffff800`02a94c9e : 00000000`00000000 000007fe`f626965c fffff683`ff7b1348 fffffa80`05b1aac8 : nt!KiPageFault+0x16e
fffff880`07c529b0 fffff800`02a92f23 : ffffffff`ffffff00 000007fe`f55b2500 00000000`00000000 fffffa80`00000000 : nt!MiDispatchFault+0xde
fffff880`07c52ac0 fffff800`02a76fee : 00000000`00000008 00000000`026b4380 ffffffff`fe363c01 00000000`00000000 : nt!MmAccessFault+0x343
fffff880`07c52c20 000007fe`f55b2500 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`1bd1e5e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f55b2500


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDispatchFault+de
fffff800`02a94c9e 488b1c29        mov     rbx,qword ptr [rcx+rbp]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiDispatchFault+de

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiDispatchFault+de

BUCKET_ID:  X64_0x50_nt!MiDispatchFault+de

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

usasma · May 9, 2010

31 memory dumps over the last month (from 09 April 2010 to the present)
7 different STOP errors, with approximately 9 different causes being blamed.
This is, IMO, symptomatic of a hardware problem.

The first suspect is the danew.sys driver - it belongs to your Death Adder mouse.
Please uninstall the current Razer drivers, then install a fresh set by downloading them from here: Razer Support

The next suspect is either the file system on the hard drive - or the hard drive itself. Please try these tests:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

and

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

The next suspect is (IMO) the Death Adder mouse itself. Please unplug it and don't use it for a couple of days.

Summary of the BSOD's:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May  9 19:03:57.379 2010 (GMT-4)
System Uptime: 0 days 0:07:22.018
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for danew.sys
*** ERROR: Module load completed but symbols could not be loaded for danew.sys
Probably caused by : danew.sys ( danew+6da )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May  9 18:55:46.408 2010 (GMT-4)
System Uptime: 0 days 0:07:20.047
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for danew.sys
*** ERROR: Module load completed but symbols could not be loaded for danew.sys
Probably caused by : danew.sys ( danew+6da )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May  9 18:47:49.710 2010 (GMT-4)
System Uptime: 0 days 0:23:42.349
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for danew.sys
*** ERROR: Module load completed but symbols could not be loaded for danew.sys
Probably caused by : danew.sys ( danew+6da )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May  9 18:23:26.705 2010 (GMT-4)
System Uptime: 0 days 0:50:44.094
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for danew.sys
*** ERROR: Module load completed but symbols could not be loaded for danew.sys
Probably caused by : danew.sys ( danew+6da )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May  9 12:25:19.129 2010 (GMT-4)
System Uptime: 0 days 0:00:47.519
BugCheck 3B, {c0000005, fffff9600014378d, fffff88008612010, 0}
Probably caused by : win32k.sys ( win32k!memcpy+bd )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  reader_sl.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May  9 04:00:02.894 2010 (GMT-4)
System Uptime: 0 days 1:01:03.550
BugCheck 3B, {c0000005, fffff9600026123c, fffff880071630e0, 0}
Probably caused by : win32k.sys ( win32k!bDynamicRemoveAllDriverRealizations+24 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May  8 19:55:29.972 2010 (GMT-4)
System Uptime: 0 days 0:00:08.611
BugCheck 24, {1904fb, fffff88003d50718, fffff88003d4ff80, fffff8800130415b}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+736 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May  8 09:53:08.377 2010 (GMT-4)
System Uptime: 0 days 0:08:03.016
BugCheck 3B, {c0000005, fffff960001f1509, fffff88001ffae10, 0}
Probably caused by : win32k.sys ( win32k!UpdateAsyncKeyState+f9 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May  7 22:48:57.314 2010 (GMT-4)
System Uptime: 0 days 8:19:21.953
BugCheck 1000007E, {ffffffffc0000005, fffff880045d5d26, fffff88004bc51b8, fffff88004bc4a20}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+8e )
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May  6 11:28:22.846 2010 (GMT-4)
System Uptime: 0 days 0:02:09.484
BugCheck 3B, {c0000005, fffff80002a73f2e, fffff880071320d0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceSharedLite+4e )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  MOM.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May  5 13:11:49.596 2010 (GMT-4)
System Uptime: 0 days 0:05:42.235
BugCheck 3B, {c0000005, fffff80002da35ba, fffff8800812c750, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+22a )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May  4 19:35:25.554 2010 (GMT-4)
System Uptime: 0 days 0:43:39.193
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for danew.sys
*** ERROR: Module load completed but symbols could not be loaded for danew.sys
Probably caused by : danew.sys ( danew+6da )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May  4 18:50:43.800 2010 (GMT-4)
System Uptime: 0 days 5:27:59.439
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for danew.sys
*** ERROR: Module load completed but symbols could not be loaded for danew.sys
Probably caused by : danew.sys ( danew+6da )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May  1 20:03:19.701 2010 (GMT-4)
System Uptime: 0 days 0:01:26.090
BugCheck F4, {3, fffffa80059dfb30, fffffa80059dfe10, fffff80002dd8540}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000409
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May  1 09:36:25.397 2010 (GMT-4)
System Uptime: 0 days 0:06:27.036
BugCheck 1E, {ffffffffc0000005, fffff8800113ef74, 0, ffffffffffffffff}
Probably caused by : fileinfo.sys ( fileinfo!FIPfStringFind+48 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Apr 28 12:03:03.278 2010 (GMT-4)
System Uptime: 0 days 0:00:37.933
BugCheck 1E, {ffffffffc0000005, fffff80002ad9e74, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiUpdateWsleHash+144 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  wmpnetwk.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Apr 27 22:51:53.724 2010 (GMT-4)
System Uptime: 0 days 0:08:41.379
BugCheck 3B, {c0000005, fffff80002a8e3fd, fffff8800876ac80, 0}
Probably caused by : ntkrnlmp.exe ( nt!RtlpCoalesceFreeBlocks+b1 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Xfire.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Apr 26 12:12:25.672 2010 (GMT-4)
System Uptime: 0 days 0:04:35.310
BugCheck 3B, {c0000005, fffff960001cd242, fffff88008a5a4a0, 0}
Probably caused by : win32k.sys ( win32k!UserVisrgnFromHwnd+2a )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  MediaMonkey.ex
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Apr 25 13:38:57.008 2010 (GMT-4)
System Uptime: 0 days 0:06:51.647
BugCheck 19, {3, fffffa800395b8b0, fffffa800395b8b0, dffffa800395b8b0}
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Apr 23 12:26:40.678 2010 (GMT-4)
System Uptime: 0 days 0:06:38.067
BugCheck 3B, {c0000005, fffff960000e5634, fffff880088ad220, 0}
Probably caused by : win32k.sys ( win32k!NtUserGetThreadState+b4 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  MsMpEng.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Apr 22 12:36:12.325 2010 (GMT-4)
System Uptime: 0 days 0:06:09.964
BugCheck 24, {1904fb, fffff88002f4d5b8, fffff88002f4ce20, fffff80002bbaf8c}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Apr 21 02:43:13.951 2010 (GMT-4)
System Uptime: 0 days 12:52:28.590
BugCheck 3B, {c0000005, fffff80002d9c5ba, fffff88008b48750, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+22a )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Apr 17 19:26:17.672 2010 (GMT-4)
System Uptime: 0 days 0:03:29.311
BugCheck 3B, {c0000005, fffff9600002fb64, fffff88006fbc370, 0}
Probably caused by : win32k.sys ( win32k!RGNOBJ::bCopy+18 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  taskhost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Apr 16 15:19:45.247 2010 (GMT-4)
System Uptime: 0 days 2:51:42.902
BugCheck 3B, {c0000005, fffff960001592d7, fffff880071fdad0, 0}
Probably caused by : win32k.sys ( win32k!EXLATEOBJ::vAddToCache+e7 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Apr 15 12:29:32.085 2010 (GMT-4)
System Uptime: 0 days 0:07:54.723
BugCheck 3B, {c0000005, fffff80002d99b30, fffff88006782050, 0}
Probably caused by : ntkrnlmp.exe ( nt!SepDuplicateToken+290 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Apr 12 12:16:26.790 2010 (GMT-4)
System Uptime: 0 days 0:02:00.429
BugCheck 19, {3, fffffa800395dd70, fffffa800395dd70, dffffa800395dd70}
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Apr 11 14:42:10.959 2010 (GMT-4)
System Uptime: 0 days 2:26:19.613
BugCheck 3B, {c0000005, fffff80002bf20bf, fffff88008d25f10, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Apr 10 10:24:43.860 2010 (GMT-4)
System Uptime: 0 days 0:34:07.498
BugCheck 1000007E, {ffffffffc0000005, fffff80002d7ecda, fffff88003154448, fffff88003153ca0}
Probably caused by : ntkrnlmp.exe ( nt!FsRtlOplockIsFastIoPossible+a )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Apr 10 09:49:40.248 2010 (GMT-4)
System Uptime: 0 days 0:01:14.902
BugCheck 19, {3, fffffa800395acf0, fffffa800395acf0, dffffa800395acf0}
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Apr 10 09:47:27.581 2010 (GMT-4)
System Uptime: 0 days 0:15:39.219
BugCheck 19, {3, fffffa800395a6c0, fffffa800395a6c0, dffffa800395a6c0}
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Apr  9 19:35:18.238 2010 (GMT-4)
System Uptime: 0 days 0:01:10.892
BugCheck 50, {fffff6ec5000e860, 0, fffff80002a94c9e, 5}
Probably caused by : memory_corruption ( nt!MiDispatchFault+de )
BUGCHECK_STR:  0x50
PROCESS_NAME:  MOM.exe

trinkk · May 10, 2010

I reinstalled my Death Adder drivers and ran memtest86+ which showed no errors. I didn't run the HD Diagnostic because there was no tool for my HD, a Samsug Spinpoint F3HD103SJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s. Though even if there was I still would not because of the disclaimer that all my data just might fall through the cracks.

Here's the CHKDSK log.

Code:

Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          5/9/2010 9:30:25 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      TheHO-DOZER
Description:


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  161792 file records processed.                                         

File verification completed.
  286 large file records processed.                                   

  0 bad file records processed.                                     

  2 EA records processed.                                           

  44 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 5)...
  203302 index entries processed.                                        

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      

CHKDSK is verifying security descriptors (stage 3 of 5)...
  161792 file SDs/SIDs processed.                                        

Cleaning up 640 unused index entries from index $SII of file 0x9.
Cleaning up 640 unused index entries from index $SDH of file 0x9.
Cleaning up 640 unused security descriptors.
Security descriptor verification completed.
  20756 data files processed.                                           

CHKDSK is verifying Usn Journal...
  33775792 USN bytes processed.                                            

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  161776 files processed.                                                

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  188372479 free clusters processed.                                        

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

 976751968 KB total disk space.
 222890392 KB in 140400 files.
     80012 KB in 20757 indexes.
         0 KB in bad sectors.
    291644 KB in use by the system.
     65536 KB occupied by the log file.
 753489920 KB available on disk.

      4096 bytes in each allocation unit.
 244187992 total allocation units on disk.
 188372480 allocation units available on disk.

Internal Info:
00 78 02 00 90 75 02 00 8d 9d 04 00 00 00 00 00  .x...u..........
bf 5a 00 00 2c 00 00 00 00 00 00 00 00 00 00 00  .Z..,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-05-10T04:30:25.000000000Z" />
    <EventRecordID>4469</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>TheHO-DOZER</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  161792 file records processed.                                         

File verification completed.
  286 large file records processed.                                   

  0 bad file records processed.                                     

  2 EA records processed.                                           

  44 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 5)...
  203302 index entries processed.                                        

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      

CHKDSK is verifying security descriptors (stage 3 of 5)...
  161792 file SDs/SIDs processed.                                        

Cleaning up 640 unused index entries from index $SII of file 0x9.
Cleaning up 640 unused index entries from index $SDH of file 0x9.
Cleaning up 640 unused security descriptors.
Security descriptor verification completed.
  20756 data files processed.                                           

CHKDSK is verifying Usn Journal...
  33775792 USN bytes processed.                                            

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  161776 files processed.                                                

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  188372479 free clusters processed.                                        

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

 976751968 KB total disk space.
 222890392 KB in 140400 files.
     80012 KB in 20757 indexes.
         0 KB in bad sectors.
    291644 KB in use by the system.
     65536 KB occupied by the log file.
 753489920 KB available on disk.

      4096 bytes in each allocation unit.
 244187992 total allocation units on disk.
 188372480 allocation units available on disk.

Internal Info:
00 78 02 00 90 75 02 00 8d 9d 04 00 00 00 00 00  .x...u..........
bf 5a 00 00 2c 00 00 00 00 00 00 00 00 00 00 00  .Z..,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
  </EventData>
</Event>

Jonathan_King · May 10, 2010

Go ahead and use SeaTools to test your hard drive.

As suggested, unplug your mouse altogether, and see if the BSODs stop.

BSOD oh god why

trinkk

New member

My Computer

zigzag3143

New member

My Computer

usasma

Mr. Cranky Pants

My Computer

trinkk

New member

My Computer

Jonathan_King

New member

My Computer