New
#41
i pressed remove,and its in quarantine now
i read somewhere that deleteing keys with malware bytes fixes them
i pressed remove,and its in quarantine now
i read somewhere that deleteing keys with malware bytes fixes them
That is true, at least for some Malware. Some are more than Malwarebytes can handle. I suggest that you start a thread in the System Security section, System Security - Windows 7 Forums, and get some advice from the security Gurus. Some malware are very deep rooted and difficult to get rid of. Some require a formatting and a clean install.
Bsod went away for a day or two then reoccured
On Thu 20/01/2011 17:27:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012011-23415-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 20/01/2011 17:27:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 20/01/2011 21:05:16 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x57386)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
i did an sfc /scannow and it found corrupted files but could not repair them
i have attached its log
Update: was installing microsoft office and bluescreened again upon restart my Windows explorer
kept crashing constantly and i wasnt able to do anything until it bluescreened after 10 seconds, so i went into safe mode and i've read through the SFC log and renamed a file called umb.dll which it couldn't fix and also the properties of the file says its previous name was UMB.dll
anyway i've renamed this file to umb.old
and now all is booting fine, hopefully i dont get another bluescreen
Last edited by ratchetclan4; 20 Jan 2011 at 16:55.
UMB.dll is a Windows file by Microsoft, User Mode Bus Driver Interface Dll. Run SFC again and see if it reinstalls it. Please upload the dumps files to us.
Bsods went away for a few days but have now reoccured, i got one within 5 seconds of call of duty black ops gameplay
i've did a few tests
I ran Prime95 Blend Test
-----------------------------
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected,
I ran Memtest for 8hours
-----------------------
No Errors
I ran Passmark and it passed all the tests
however when i ran the Alien Physics Simulation (3-12fps) i bluescreened
to these
so far all my bluescreens relate toCode:On Sat 29/01/2011 03:25:26 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\012911-20701-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) Bugcheck code: 0x1A (0x403, 0xFFFFF6800011D8B0, 0x8880000035C15867, 0xFFEFF6800011D8B0) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 29/01/2011 03:25:26 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x1A (0x403, 0xFFFFF6800011D8B0, 0x8880000035C15867, 0xFFEFF6800011D8B0) Error: MEMORY_MANAGEMENT Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Dxgmm1.sys
ntkrnlmp.sys
ntoskrnl.exe
nv4_disp.dll
Dis you run Memtest from a cold boot after you computer had been off for an hour or so? If not, run it again from a cold boot and let it run for a minimum of 7 passes. RAM - Test with Memtest86+. Let us know the results.
Prime shows a hardware problem. I suggest that you run it again. https://www.sevenforums.com/tutorials...t-prime95.html. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Let's sort out the hardware error. Your last four dumps each show a different bugcheck. This indicates a hardware or a hardware related problem. Post back with your results.
If you have no hardware errors, either in Memtest or Prime, enable Driver Verifier carefully following the instructions in this tutorial: Driver Verifier - Enable and Disable. If verifier finds a faulty driver, it will trigger a BSOD. Upload any and all Verifier enabled dumps.Bugcheck 3B, SYSTEM_SERVICE_EXCEPTION.
Bugcheck 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.
Bugcheck 1A, MEMORY_MANAGEMENT.
Bugcheck 1E, KMODE_EXCEPTION_NOT_HANDLED
Code:Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`0181b000 PsLoadedModuleList = 0xfffff800`01a58e50 Debug session time: Fri Jan 28 22:51:59.692 2011 (GMT-5) System Uptime: 0 days 2:22:33.816 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff8000184c23b, fffff8800d4e5e50, 0} Probably caused by : ntkrnlmp.exe ( nt!ExQueryPoolUsage+e0 ) Followup: MachineOwner --------- 2: 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: fffff8000184c23b, Address of the exception record for the exception that caused the bugcheck Arg3: fffff8800d4e5e50, 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!ExQueryPoolUsage+e0 fffff800`0184c23b 8379e400 cmp dword ptr [rcx-1Ch],0 CONTEXT: fffff8800d4e5e50 -- (.cxr 0xfffff8800d4e5e50) rax=00000000000384fe rbx=0000000000000000 rcx=ffdff80001a06920 rdx=fffff8800d4e697c rsi=00000000000fb99e rdi=0000000007ddec90 rip=fffff8000184c23b rsp=fffff8800d4e6830 rbp=fffff8800d4e6ca0 r8=fffff8800d4e6978 r9=fffff80001a30720 r10=0000000000000005 r11=fffff8800d4e695c r12=0000000000000004 r13=000000000001fed5 r14=fffff80001ac3900 r15=0000000000000000 iopl=0 nv up ei ng nz na po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287 nt!ExQueryPoolUsage+0xe0: fffff800`0184c23b 8379e400 cmp dword ptr [rcx-1Ch],0 ds:002b:ffdff800`01a06904=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: wlcomm.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8000184c23b STACK_TEXT: fffff880`0d4e6830 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExQueryPoolUsage+0xe0 FOLLOWUP_IP: nt!ExQueryPoolUsage+e0 fffff800`0184c23b 8379e400 cmp dword ptr [rcx-1Ch],0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ExQueryPoolUsage+e0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 STACK_COMMAND: .cxr 0xfffff8800d4e5e50 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!ExQueryPoolUsage+e0 BUCKET_ID: X64_0x3B_nt!ExQueryPoolUsage+e0 Followup: MachineOwner --------- Debug session time: Fri Jan 28 19:05:33.131 2011 (GMT-5) System Uptime: 0 days 6:50:11.881 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff800018b8719, fffff8800fdab8c8, fffff8800fdab120} Unable to load image \SystemRoot\system32\DRIVERS\netr6164.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for netr6164.sys *** ERROR: Module load completed but symbols could not be loaded for netr6164.sys Probably caused by : netr6164.sys ( netr6164+2a0d ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff800018b8719, The address that the exception occurred at Arg3: fffff8800fdab8c8, Exception Record Address Arg4: fffff8800fdab120, Context Record Address 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!KeSynchronizeExecution+9 fffff800`018b8719 488b7148 mov rsi,qword ptr [rcx+48h] EXCEPTION_RECORD: fffff8800fdab8c8 -- (.exr 0xfffff8800fdab8c8) ExceptionAddress: fffff800018b8719 (nt!KeSynchronizeExecution+0x0000000000000009) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff8800fdab120 -- (.cxr 0xfffff8800fdab120) rax=000000000400000a rbx=0000000000010000 rcx=ffdffa800561a548 rdx=fffff8800367505c rsi=fffffa8005c97000 rdi=0000000000000000 rip=fffff800018b8719 rsp=fffff8800fdabb00 rbp=0000000000000020 r8=fffffa8005c97000 r9=fffffa8005c97000 r10=fffffa8005649680 r11=fffff8800367505c r12=0000000000000000 r13=0000000000000000 r14=0000000000003000 r15=fffff880036767b8 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!KeSynchronizeExecution+0x9: fffff800`018b8719 488b7148 mov rsi,qword ptr [rcx+48h] ds:002b:ffdffa80`0561a590=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001af30e0 ffffffffffffffff FOLLOWUP_IP: netr6164+2a0d fffff880`03676a0d ?? ??? BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff88001537759 to fffff800018b8719 STACK_TEXT: fffff880`0fdabb00 fffff880`01537759 : 00000000`00003000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x9 fffff880`0fdabb40 fffff880`03676a0d : 00000000`00010000 00000000`00010000 00000000`00000020 fffffa80`0832e060 : ndis!NdisMSynchronizeWithInterruptEx+0x49 fffff880`0fdabb70 00000000`00010000 : 00000000`00010000 00000000`00000020 fffffa80`0832e060 fffffa80`05633978 : netr6164+0x2a0d fffff880`0fdabb78 00000000`00010000 : 00000000`00000020 fffffa80`0832e060 fffffa80`05633978 fffff880`01534e4b : 0x10000 fffff880`0fdabb80 00000000`00000020 : fffffa80`0832e060 fffffa80`05633978 fffff880`01534e4b fffffa80`0561f1a0 : 0x10000 fffff880`0fdabb88 fffffa80`0832e060 : fffffa80`05633978 fffff880`01534e4b fffffa80`0561f1a0 00000000`00000000 : 0x20 fffff880`0fdabb90 fffffa80`05633978 : fffff880`01534e4b fffffa80`0561f1a0 00000000`00000000 00000000`00000000 : 0xfffffa80`0832e060 fffff880`0fdabb98 fffff880`01534e4b : fffffa80`0561f1a0 00000000`00000000 00000000`00000000 fffffa80`05633950 : 0xfffffa80`05633978 fffff880`0fdabba0 fffff880`014babfd : fffffa80`05633c58 00000000`0000000a 00000000`00000003 00000000`00000003 : ndis! ?? ::DKGKHJNI::`string'+0x1597 fffff880`0fdabc10 fffff880`014e1b0c : 00000000`00000000 fffffa80`05633c58 00000000`00000080 fffffa80`04ae0b60 : ndis!ndisQueuedMiniportDpcWorkItem+0xcd fffff880`0fdabcb0 fffff800`01b60166 : 00000000`00000000 fffffa80`0832e060 00000000`00000080 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x12c fffff880`0fdabd40 fffff800`0189b486 : fffff880`009bf180 fffffa80`0832e060 fffff880`009c9fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0fdabd80 00000000`00000000 : fffff880`0fdac000 fffff880`0fda6000 fffff880`0fdaba00 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: netr6164+2a0d FOLLOWUP_NAME: MachineOwner MODULE_NAME: netr6164 IMAGE_NAME: netr6164.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ad7e54b STACK_COMMAND: .cxr 0xfffff8800fdab120 ; kb FAILURE_BUCKET_ID: X64_0x7E_netr6164+2a0d BUCKET_ID: X64_0x7E_netr6164+2a0d Followup: MachineOwner --------- Debug session time: Sat Jan 29 10:25:26.331 2011 (GMT-5) System Uptime: 0 days 1:09:07.081 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list ........... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {403, fffff6800011d8b0, 8880000035c15867, ffeff6800011d8b0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31f72 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000000403, The subtype of the bugcheck. Arg2: fffff6800011d8b0 Arg3: 8880000035c15867 Arg4: ffeff6800011d8b0 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_403 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: pt.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001a3e228 to fffff80001a88f00 STACK_TEXT: fffff880`09f927b8 fffff800`01a3e228 : 00000000`0000001a 00000000`00000403 fffff680`0011d8b0 88800000`35c15867 : nt!KeBugCheckEx fffff880`09f927c0 fffff800`01ab9b51 : 00000000`00000000 fffff680`0011dff8 fffffa80`05544b30 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x31f72 fffff880`09f92970 fffff800`01acac4a : 00000000`00000000 00000000`2f19afff fffffa80`00000000 fffffa80`05544b30 : nt!MiDeleteVirtualAddresses+0x408 fffff880`09f92b30 fffff800`01a88153 : ffffffff`ffffffff 00000000`000f82c0 00000000`000f8288 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca fffff880`09f92c20 00000000`771c009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`000f81f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771c009a STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+31f72 fffff800`01a3e228 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+31f72 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31f72 BUCKET_ID: X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31f72 Followup: MachineOwner --------- Debug session time: Sat Jan 29 07:16:42.126 2011 (GMT-5) System Uptime: 0 days 0:18:04.250 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +5e4c952f01a0dd48 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: BlackOps.exe CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff88001efb8a8 -- (.exr 0xfffff88001efb8a8) ExceptionAddress: fffff88003500b3d (dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x000000000000007d) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff88001efb950 -- (.trap 0xfffff88001efb950) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffeffa8005304320 rbx=0000000000000000 rcx=fffffa8007f34620 rdx=fffffa8006c923b0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88003500b3d rsp=fffff88001efbae0 rbp=fffffa8005106a60 r8=00000000000000c4 r9=fffffa8007f37268 r10=fffffa8005d2f9b0 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x7d: fffff880`03500b3d f0834018ff lock add dword ptr [rax+18h],0FFFFFFFFh ds:b000:ffeffa80`05304338=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001a80c2e to fffff80001a88ed0 STACK_TEXT: fffff880`01efa988 fffff800`01a80c2e : fffffa80`000000c0 00000000`00000000 fffff880`01efb100 fffff800`01ab5e28 : nt!KeBugCheck fffff880`01efa990 fffff800`01aaebed : fffff800`01c95c24 fffff800`01bcea3c fffff800`01a17000 fffff880`01efb8a8 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`01efa9c0 fffff800`01ab6250 : fffff800`01bd6a88 fffff880`01efaa38 fffff880`01efb8a8 fffff800`01a17000 : nt!RtlpExecuteHandlerForException+0xd fffff880`01efa9f0 fffff800`01ac31b5 : fffff880`01efb8a8 fffff880`01efb100 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x410 fffff880`01efb0d0 fffff800`01a88542 : fffff880`01efb8a8 fffffa80`05d40680 fffff880`01efb950 fffffa80`06c923b0 : nt!KiDispatchException+0x135 fffff880`01efb770 fffff800`01a86e4a : 00000000`00000202 fffff800`01a8d9fa fffff880`01e5c180 fffffa80`05d23b60 : nt!KiExceptionDispatch+0xc2 fffff880`01efb950 fffff880`03500b3d : fffffa80`054eb740 00000000`00000001 fffffa80`05d2f1f0 fffffa80`05106a60 : nt!KiGeneralProtectionFault+0x10a fffff880`01efbae0 fffff880`03504677 : fffffa80`0549b000 fffffa80`05d2f1f0 fffffa80`05d3f000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x7d fffff880`01efbb10 fffff880`03503e00 : 00000000`00000000 fffffa80`054c3000 00000000`00000000 fffff880`038b70e4 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x253 fffff880`01efbbb0 fffff880`03503c4c : 00000000`00000000 fffffa80`05d2f1f0 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198 fffff880`01efbc00 fffff880`0340a1cf : fffffa80`0567f480 00000000`00000000 00000000`00000022 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94 fffff880`01efbc50 fffff880`03785a88 : fffffa80`0569d000 fffffa80`0569d000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgNotifyDpcCB+0x77 fffff880`01efbc80 fffffa80`0569d000 : fffffa80`0569d000 00000000`00000000 00000000`00000000 fffff880`03785a1b : nvlddmkm+0xb5a88 fffff880`01efbc88 fffffa80`0569d000 : 00000000`00000000 00000000`00000000 fffff880`03785a1b fffffa80`0569d000 : 0xfffffa80`0569d000 fffff880`01efbc90 00000000`00000000 : 00000000`00000000 fffff880`03785a1b fffffa80`0569d000 00000000`00000000 : 0xfffffa80`0569d000 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d fffff880`03500b3d f0834018ff lock add dword ptr [rax+18h],0FFFFFFFFh SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578 FAILURE_BUCKET_ID: X64_0x1E_dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d BUCKET_ID: X64_0x1E_dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d Followup: MachineOwner --------- 3: kd> lmtsmn start end module name fffff880`00f0d000 fffff880`00f64000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`02e43000 fffff880`02ecd000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`03551000 fffff880`03567000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`0315a000 fffff880`0316f000 amdppm amdppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`010ec000 fffff880`010f7000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`00e1a000 fffff880`00e23000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00e23000 fffff880`00e4d000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`013ed000 fffff880`013f4000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`03123000 fffff880`03134000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`07fa7000 fffff880`07fc5000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`00760000 fffff960`00787000 cdd cdd.dll Mon Jul 13 21:25:40 2009 (4A5BDE94) fffff880`015d3000 fffff880`015fd000 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`01450000 fffff880`01480000 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`014b6000 fffff880`01529000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`03541000 fffff880`03551000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`0455c000 fffff880`0456a000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`03082000 fffff880`03105000 csc csc.sys Mon Jul 13 19:24:26 2009 (4A5BC22A) fffff880`03105000 fffff880`03123000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`03073000 fffff880`03082000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`0143a000 fffff880`01450000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`0445c000 fffff880`0447e000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`0456a000 fffff880`04574000 dump_diskdump dump_diskdump.sys Mon Jul 13 20:01:00 2009 (4A5BCABC) fffff880`045b3000 fffff880`045c6000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`04574000 fffff880`045b3000 dump_nvstor64 dump_nvstor64.sys Tue Aug 04 20:31:07 2009 (4A78D2CB) fffff880`04484000 fffff880`04490000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`03407000 fffff880`034fb000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`034fb000 fffff880`03541000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`01143000 fffff880`01157000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`010f7000 fffff880`01143000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`0153a000 fffff880`01544000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`01400000 fffff880`0143a000 fvevol fvevol.sys Mon Jul 13 19:22:15 2009 (4A5BC1A7) fffff880`017b0000 fffff880`017fa000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`01ff4000 fffff800`0203d000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`02fc3000 fffff880`02fe7000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`0366f000 fffff880`036cb000 HdAudio HdAudio.sys Mon Jul 13 20:06:59 2009 (4A5BCC23) fffff880`044bd000 fffff880`044d6000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`044d6000 fffff880`044de080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`044af000 fffff880`044bd000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`07edf000 fffff880`07fa7000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`015ca000 fffff880`015d3000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`04359000 fffff880`04368000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`044df000 fffff880`044ed000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`017eb000 fffff800`017f5000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`04377000 fffff880`043ba000 ks ks.sys Mon Jul 13 20:00:31 2009 (4A5BCA9F) fffff880`013d3000 fffff880`013ed000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`01660000 fffff880`0168b000 ksecpkg ksecpkg.sys Mon Jul 13 19:50:34 2009 (4A5BC84A) fffff880`0447e000 fffff880`04483200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`045e9000 fffff880`045fe000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`045c6000 fffff880`045e9000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00c29000 fffff880`00c36000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65) fffff880`044fa000 fffff880`04508000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`04368000 fffff880`04377000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`044ed000 fffff880`044fa000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00e00000 fffff880`00e1a000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`01000000 fffff880`01031000 MpFilter MpFilter.sys Tue Sep 14 20:19:28 2010 (4C901110) fffff880`08531000 fffff880`08541000 MpNWMon MpNWMon.sys Tue Sep 14 20:19:30 2010 (4C901112) fffff880`07fc5000 fffff880`07fdd000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`07e00000 fffff880`07e2c000 mrxsmb mrxsmb.sys Mon Jul 13 19:23:59 2009 (4A5BC20F) fffff880`086d8000 fffff880`08725000 mrxsmb10 mrxsmb10.sys Mon Jul 13 19:24:08 2009 (4A5BC218) fffff880`08725000 fffff880`08748000 mrxsmb20 mrxsmb20.sys Mon Jul 13 19:24:05 2009 (4A5BC215) fffff880`01031000 fffff880`0103c000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00f6d000 fffff880`00f77000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`01157000 fffff880`011b5000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`03068000 fffff880`03073000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`016aa000 fffff880`016bc000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`016be000 fffff880`017b0000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`0358b000 fffff880`03597000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`07eb4000 fffff880`07ec7000 ndisuio ndisuio.sys Mon Jul 13 20:09:25 2009 (4A5BCCB5) fffff880`03597000 fffff880`035c6000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`0365a000 fffff880`0366f000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`02f57000 fffff880`02f66000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`02ecd000 fffff880`02f12000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`01600000 fffff880`01660000 NETIO NETIO.SYS Thu Apr 08 22:43:59 2010 (4BBE946F) fffff880`08556000 fffff880`085c9000 netr6164 netr6164.sys Wed Apr 07 08:07:21 2010 (4BBC7579) fffff880`08541000 fffff880`08556000 NisDrvWFP NisDrvWFP.sys Tue Sep 14 20:20:25 2010 (4C901149) fffff880`00def000 fffff880`00e00000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`0305c000 fffff880`03068000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`01a17000 fffff800`01ff4000 nt ntkrnlmp.exe Mon Jul 13 19:40:48 2009 (4A5BC600) fffff880`01230000 fffff880`013d3000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`014ab000 fffff880`014b4000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`0432b000 fffff880`0432c180 nvBridge nvBridge.kmd Fri Jan 07 20:57:22 2011 (4D27C482) fffff880`036d0000 fffff880`0432ad00 nvlddmkm nvlddmkm.sys Fri Jan 07 21:07:22 2011 (4D27C6DA) fffff880`00dc4000 fffff880`00def000 nvstor nvstor.sys Wed May 20 02:45:37 2009 (4A13A711) fffff880`010ad000 fffff880`010ec000 nvstor64 nvstor64.sys Tue Aug 04 20:31:07 2009 (4A78D2CB) fffff880`07e61000 fffff880`07eb4000 nwifi nwifi.sys Mon Jul 13 20:07:23 2009 (4A5BCC3B) fffff880`02f1b000 fffff880`02f41000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`0316f000 fffff880`0318c000 parport parport.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`00fb7000 fffff880`00fcc000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00f77000 fffff880`00faa000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00fe1000 fffff880`00fe8000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00fe8000 fffff880`00ff8000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`01529000 fffff880`0153a000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`08748000 fffff880`087ee000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`0441f000 fffff880`0445c000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00c36000 fffff880`00c4a000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`03567000 fffff880`0358b000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`035c6000 fffff880`035e1000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`0432d000 fffff880`0434e000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`035e1000 fffff880`035fb000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`0300b000 fffff880`0305c000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`0434e000 fffff880`04359000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA) fffff880`0121e000 fffff880`01227000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`01227000 fffff880`01230000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`013f4000 fffff880`013fd000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`01590000 fffff880`015ca000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`07ec7000 fffff880`07edf000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`087ee000 fffff880`087f9000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`0318c000 fffff880`03198000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`02f66000 fffff880`02f83000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`016a3000 fffff880`016aa000 speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798) fffff880`0169b000 fffff880`016a3000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`08428000 fffff880`084c0000 srv srv.sys Mon Jul 13 19:25:11 2009 (4A5BC257) fffff880`0863f000 fffff880`086a8000 srv2 srv2.sys Mon Jul 13 19:25:02 2009 (4A5BC24E) fffff880`08600000 fffff880`0862d000 srvnet srvnet.sys Mon Jul 13 19:24:58 2009 (4A5BC24A) fffff880`0104b000 fffff880`010ad000 storport storport.sys Mon Jul 13 20:01:18 2009 (4A5BCACE) fffff880`035fb000 fffff880`035fc480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01803000 fffff880`01a00000 tcpip tcpip.sys Thu Apr 08 22:45:54 2010 (4BBE94E2) fffff880`0862d000 fffff880`0863f000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`02e36000 fffff880`02e43000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`02e18000 fffff880`02e36000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`02f9e000 fffff880`02fb2000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`004e0000 fffff960`004ea000 TSDDD TSDDD.dll unavailable (00000000) fffff880`03134000 fffff880`0315a000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`04508000 fffff880`0455c000 udfs udfs.sys Mon Jul 13 19:23:37 2009 (4A5BC1F9) fffff880`043ba000 fffff880`043cc000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`04490000 fffff880`044ad000 usbccgp usbccgp.sys Mon Jul 13 20:06:45 2009 (4A5BCC15) fffff880`044ad000 fffff880`044aef00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`02fb2000 fffff880`02fc3000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`03600000 fffff880`0365a000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`03198000 fffff880`031a3000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`031a3000 fffff880`031f9000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`00faa000 fffff880`00fb7000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`01200000 fffff880`0120e000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`00c00000 fffff880`00c25000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`0168b000 fffff880`0169b000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E) fffff880`00fcc000 fffff880`00fe1000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00d68000 fffff880`00dc4000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`01544000 fffff880`01590000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`085c9000 fffff880`085d6000 vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39) fffff880`02f41000 fffff880`02f57000 vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A) fffff880`02f83000 fffff880`02f9e000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`0120e000 fffff880`0121e000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00e5a000 fffff880`00efe000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00efe000 fffff880`00f0d000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02f12000 fffff880`02f1b000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`00030000 fffff960`0033f000 win32k win32k.sys Mon Jul 13 19:40:16 2009 (4A5BC5E0) fffff880`00f64000 fffff880`00f6d000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`043cc000 fffff880`043ed000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) Unloaded modules: fffff880`084c0000 fffff880`08531000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`084c0000 fffff880`08531000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01480000 fffff880`0148e000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0148e000 fffff880`01498000 dump_storpor Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`011b5000 fffff880`011f4000 dump_nvstor6 Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01498000 fffff880`014ab000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000
I have good news, or so i hope for now!
my pc became unbootable (black screen after startup) or Bsod
so i tried it with just one stick of ram in and instantly got a new error
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
i took the stick out and put my other one in and all is working fine!
im guessing it was a faulty stick
It sure does sound like that stick is bad. You can run Memtest on that one stick you think it faulty and see what it shows.
I ran memtest a week ago with both sticks for 16 hours
No errors.
I'd rather not run memtest until problems arise,its a pain to get these sticks out of this motherboard, dont want to break my working one ha.
also Can faulty memory, corrupt video drivers and network card ones?
just my video drivers kept getting a yellow ! over them before i removed that ram
RAM, video drivers, and the network card are all interrelated when running on your system. A fault on one definitely affects the others. It unlikely that bad RAM will damage a video card or that a bad video driver will damage the video card or the RAM. That is really what crashes are for. When things are not running properly, the system shuts down to avoid damage to hardware. Thus you have a crash.