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: BSOD

25 Nov 2010   #1
Asats

windows 7 64 bit
 
 
BSOD

well after having fixed previous issues with my computer (Thanks again to everyone btw) im back with yet another BSOD

- Win 7 x64
- the original installed OS on the system
- a retail version
- Full Retail = you purchased it from retailer

- 2 months?
- What is the age of OS installation 2 months


My System SpecsSystem Spec
.
25 Nov 2010   #2
Asats

windows 7 64 bit
 
 

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: fe
BCP1: 0000000000000005
BCP2: FFFFFA8004FA81A0
BCP3: 0000000010DE077C
BCP4: FFFFFA800508CC50
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

latest crash notes
My System SpecsSystem Spec
25 Nov 2010   #3
Asats

windows 7 64 bit
 
 

Here is some dump files from today
My System SpecsSystem Spec
.

25 Nov 2010   #4
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Quote:
Error code 1E (2X), KMODE_EXCEPTION_NOT_HANDLED. Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

Error code FE, BUGCODE_USB_DRIVER. Usual causes: USB device driver

Error code DA, SYSTEM_PTE_MISUSE. Usual causes: Device driver

Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
All of your dumps indicate driver issues and memory corruption. One dump blames nvlddmkm.sys which is a video driver. Just on a hunch, I a recommend that you uninstall UniBlue. I wonder if it is interfering with drivers and causing conflicts. After you uninstall UniBlue, please enable Driver Verifier following the instructions in the tutorial linked below. Use you computer normally while Driver Verifier is running. If Driver Verifier finds a faulty driver, it will trigger a BSOD. Upload any Driver Verifier enabled dumps; hopefully the dump will point out the offending driver.

Driver Verifier - Enable and Disable

Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a4c000 PsLoadedModuleList = 0xfffff800`02c89e50
Debug session time: Thu Nov 25 19:15:20.424 2010 (GMT-5)
System Uptime: 0 days 0:29:37.907
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}

Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmFlush+25 )

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:
------------------


OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+5c54952f01a5dae4
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002ffb6c8 -- (.exr 0xfffff88002ffb6c8)
ExceptionAddress: fffff80002a1fe8d (hal!memcpy+0x00000000000000bd)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002ffb770 -- (.trap 0xfffff88002ffb770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=6d61726170206563 rbx=0000000000000000 rcx=00fef88006209020
rdx=ff01000002a61000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a1fe8d rsp=fffff88002ffb908 rbp=0000000000000002
 r8=0000000000001000  r9=0000000000000080 r10=909090007325203a
r11=00fef88006209000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
hal!memcpy+0xbd:
fffff800`02a1fe8d 488941e0        mov     qword ptr [rcx-20h],rax ds:8000:00fef880`06209000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ab446e to fffff80002abc710

STACK_TEXT:  
fffff880`02ffa7b8 fffff800`02ab446e : 00000000`00000010 fffff880`02ffa9d0 fffff880`02ffaf30 fffff800`02ae9668 : nt!KeBugCheck
fffff880`02ffa7c0 fffff800`02ae240d : fffff800`02ccab7c fffff800`02c04e84 fffff800`02a4c000 fffff880`02ffb6c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffa7f0 fffff800`02ae9a90 : fffff800`02c0bb14 fffff880`02ffa868 fffff880`02ffb6c8 fffff800`02a4c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffa820 fffff800`02af69ef : fffff880`02ffb6c8 fffff880`02ffaf30 fffff880`00000000 00000000`00000002 : nt!RtlDispatchException+0x410
fffff880`02ffaf00 fffff800`02abbd82 : fffff880`02ffb6c8 00fef880`06209000 fffff880`02ffb770 00000000`00001000 : nt!KiDispatchException+0x16f
fffff880`02ffb590 fffff800`02aba68a : 00000014`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffb770 fffff800`02a1fe8d : fffff800`02a05e15 fffff880`06206000 00000000`00000002 fffffa80`0444f940 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffb908 fffff800`02a05e15 : fffff880`06206000 00000000`00000002 fffffa80`0444f940 00000000`00001000 : hal!memcpy+0xbd
fffff880`02ffb910 fffff800`02a0569a : fffffa80`04575810 00000000`00001000 fffffa80`046f0f80 00000000`00004000 : hal!HalpDmaSyncMapBuffers+0x1bd
fffff880`02ffb9c0 fffff800`02a0883f : fffffa80`04575810 00ff0000`00000000 fffffa80`046f0f80 00000000`00007000 : hal!HalpDmaFlushScatterTransfer+0xae
fffff880`02ffba10 fffff800`02a077d5 : fffffa80`06a59640 00ff0000`00000000 00000000`00007000 fffffa80`0444f940 : hal!IoFlushAdapterBuffers+0xaf
fffff880`02ffba50 fffff880`00fc4199 : fffffa80`06a595a0 fffffa80`046eb1b0 fffffa80`06a595a0 fffffa80`044a4b40 : hal!HalPutScatterGatherList+0x85
fffff880`02ffbab0 fffff880`00e0c43b : 00000000`00000000 00000000`00000001 fffff800`02ab8123 00000000`00000009 : PCIIDEX!BmFlush+0x25
fffff880`02ffbae0 fffff880`00e0c0ec : fffffa80`0430c1a0 00000000`00000000 fffffa80`0430c1a0 fffffa80`06a595a0 : ataport!IdeProcessCompletedRequests+0x123
fffff880`02ffbc10 fffff800`02ac7bfc : fffff880`02fd3180 0000000a`59a62ef4 fffffa80`0430c050 fffffa80`0430c118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02ffbcd0 fffff800`02ac4eea : fffff880`02fd3180 fffff880`02fddfc0 00000000`00000000 fffff880`00e0bf44 : nt!KiRetireDpcList+0x1bc
fffff880`02ffbd80 00000000`00000000 : fffff880`02ffc000 fffff880`02ff6000 fffff880`02ffbd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
PCIIDEX!BmFlush+25
fffff880`00fc4199 4883a3e003000000 and     qword ptr [rbx+3E0h],0

SYMBOL_STACK_INDEX:  c

SYMBOL_NAME:  PCIIDEX!BmFlush+25

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PCIIDEX

IMAGE_NAME:  PCIIDEX.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc114

FAILURE_BUCKET_ID:  X64_0x1E_PCIIDEX!BmFlush+25

BUCKET_ID:  X64_0x1E_PCIIDEX!BmFlush+25

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

Debug session time: Thu Nov 25 21:02:16.673 2010 (GMT-5)
System Uptime: 0 days 0:01:40.593
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, fffffa8004fa81a0, 10de077c, fffffa800508cc50}

Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )

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

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

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
    using a physical memory address that was not allocated by
    the USBport driver.
Arg2: fffffa8004fa81a0, Device extension pointer of the host controller
Arg3: 0000000010de077c, PCI Vendor,Product id for the controller
Arg4: fffffa800508cc50, Pointer to Endpoint data structure

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88003e2fe4e to fffff80002a8f740

STACK_TEXT:  
fffff880`02dfca18 fffff880`03e2fe4e : 00000000`000000fe 00000000`00000005 fffffa80`04fa81a0 00000000`10de077c : nt!KeBugCheckEx
fffff880`02dfca20 fffff880`03e5dfdf : 00000000`ce00b180 fffffa80`04fa96a0 fffffa80`0508cee0 00000000`00000000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff880`02dfca60 fffff880`03e5dba4 : fffff880`031d2080 fffffa80`053b56a0 fffffa80`0508cee0 fffff880`02dfcb01 : usbehci!EHCI_sMode_PollEndpointSlot+0x67
fffff880`02dfcaf0 fffff880`03e62a71 : fffffa80`0508cc50 fffffa80`04fa81a0 00000000`00000000 00000000`00000000 : usbehci!EHCI_PollPerAsyEndpoint+0x84
fffff880`02dfcb70 fffff880`03e03e8b : 00000000`00000002 fffffa80`04fa81a0 00000000`00000000 00000000`00000000 : usbehci!EHCI_PollEndpoint+0x41
fffff880`02dfcbb0 fffff880`03e089b1 : 00000000`00000000 00000000`00000004 fffffa80`0508ca10 fffffa80`04fa8050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`02dfcbe0 fffff880`03e14043 : fffffa80`04fa81a0 00000000`00000000 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`02dfcc40 fffff880`03e04f89 : fffffa80`04fa8050 00000000`00000000 fffffa80`04fa8a02 fffffa80`04fa8a10 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1af
fffff880`02dfcca0 fffff800`02a9abfc : fffff880`02dd4180 fffffa80`04fa8a10 fffffa80`04fa8a28 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02dfccd0 fffff800`02a97eea : fffff880`02dd4180 fffff880`02ddefc0 00000000`00000000 fffff880`03e04db0 : nt!KiRetireDpcList+0x1bc
fffff880`02dfcd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci!EHCI_sMode_PollEndpointSlot+67
fffff880`03e5dfdf 4533c9          xor     r9d,r9d

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  usbehci!EHCI_sMode_PollEndpointSlot+67

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc06

FAILURE_BUCKET_ID:  X64_0xFE_usbehci!EHCI_sMode_PollEndpointSlot+67

BUCKET_ID:  X64_0xFE_usbehci!EHCI_sMode_PollEndpointSlot+67

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

Debug session time: Thu Nov 25 16:22:56.543 2010 (GMT-5)
System Uptime: 0 days 0:19:07.400
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DA, {504, fffff6fc400299b8, 1, 5337}

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

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

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

SYSTEM_PTE_MISUSE (da)
The stack trace identifies the guilty driver.
Arguments:
Arg1: 0000000000000504, Type of error.
Arg2: fffff6fc400299b8
Arg3: 0000000000000001
Arg4: 0000000000005337

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xDA

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002b2de11 to fffff80002ad5740

STACK_TEXT:  
fffff880`031169d8 fffff800`02b2de11 : 00000000`000000da 00000000`00000504 fffff6fc`400299b8 00000000`00000001 : nt!KeBugCheckEx
fffff880`031169e0 fffff800`02ae55e4 : 00000000`00000000 fffff800`02c8a720 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0xb43b
fffff880`03116af0 fffff800`02ae8df5 : fffffa80`03973b30 00000000`00000008 00005349`000c6680 00000000`00000001 : nt!MiEmptyPteBins+0x10d
fffff880`03116b40 fffff800`02ae9eb4 : 00000000`00000008 00000000`00000001 fffffa80`03973b30 fffff800`02ae90cb : nt!MiAdjustPteBins+0x29
fffff880`03116b80 fffff800`02aea173 : 00000000`00000008 fffff880`03116c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x40
fffff880`03116bd0 fffff800`02d79c06 : fffffa80`03a09ae0 00000000`00000080 fffffa80`03973b30 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03116d40 fffff800`02ab3c26 : fffff880`02d63180 fffffa80`03a09ae0 fffff880`02d6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03116d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+b43b
fffff800`02b2de11 cc              int     3

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xDA_nt!_??_::FNODOBFM::_string_+b43b

BUCKET_ID:  X64_0xDA_nt!_??_::FNODOBFM::_string_+b43b

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

Debug session time: Thu Nov 25 17:23:48.019 2010 (GMT-5)
System Uptime: 0 days 0:50:14.502
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
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
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88004b8f319, fffff8800391eec8, fffff8800391e730}

Probably caused by : nvlddmkm.sys ( nvlddmkm+38d319 )

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: fffff88004b8f319, The address that the exception occurred at
Arg3: fffff8800391eec8, Exception Record Address
Arg4: fffff8800391e730, 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: 
nvlddmkm+38d319
fffff880`04b8f319 4439410c        cmp     dword ptr [rcx+0Ch],r8d

EXCEPTION_RECORD:  fffff8800391eec8 -- (.exr 0xfffff8800391eec8)
ExceptionAddress: fffff88004b8f319 (nvlddmkm+0x000000000038d319)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800391e730 -- (.cxr 0xfffff8800391e730)
rax=fffffa800442c8f0 rbx=fffffa8005af9610 rcx=ff00fa8004049d20
rdx=0000000000000000 rsi=fffffa8005acc000 rdi=0000000000000001
rip=fffff88004b8f319 rsp=fffff8800391f108 rbp=fffffa8005ada840
 r8=00000000ff00e052  r9=00000000c1d00780 r10=fffff8800391f170
r11=fffff8800391f0e0 r12=0000000000000006 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nvlddmkm+0x38d319:
fffff880`04b8f319 4439410c        cmp     dword ptr [rcx+0Ch],r8d ds:002b:ff00fa80`04049d2c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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 fffff80002cc30e0
 ffffffffffffffff 

FOLLOWUP_IP: 
nvlddmkm+38d319
fffff880`04b8f319 4439410c        cmp     dword ptr [rcx+0Ch],r8d

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88004bf123b to fffff88004b8f319

STACK_TEXT:  
fffff880`0391f108 fffff880`04bf123b : fffffa80`05af9610 fffffa80`05ada840 fffffa80`05acc000 fffffa80`05acc000 : nvlddmkm+0x38d319
fffff880`0391f110 fffffa80`05af9610 : fffffa80`05ada840 fffffa80`05acc000 fffffa80`05acc000 fffff880`0391f170 : nvlddmkm+0x3ef23b
fffff880`0391f118 fffffa80`05ada840 : fffffa80`05acc000 fffffa80`05acc000 fffff880`0391f170 fffff880`04a155a5 : 0xfffffa80`05af9610
fffff880`0391f120 fffffa80`05acc000 : fffffa80`05acc000 fffff880`0391f170 fffff880`04a155a5 00000000`00000000 : 0xfffffa80`05ada840
fffff880`0391f128 fffffa80`05acc000 : fffff880`0391f170 fffff880`04a155a5 00000000`00000000 00000000`00000001 : 0xfffffa80`05acc000
fffff880`0391f130 fffff880`0391f170 : fffff880`04a155a5 00000000`00000000 00000000`00000001 00000000`00000006 : 0xfffffa80`05acc000
fffff880`0391f138 fffff880`04a155a5 : 00000000`00000000 00000000`00000001 00000000`00000006 00000000`00000001 : 0xfffff880`0391f170
fffff880`0391f140 00000000`00000000 : 00000000`00000001 00000000`00000006 00000000`00000001 fffffa80`05acc000 : nvlddmkm+0x2135a5


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+38d319

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cb9dd0e

STACK_COMMAND:  .cxr 0xfffff8800391e730 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+38d319

BUCKET_ID:  X64_0x7E_nvlddmkm+38d319

Followup: MachineOwner
---------
My System SpecsSystem Spec
26 Nov 2010   #5
Asats

windows 7 64 bit
 
 

i did what you suggested and nothing came of it blue screen after blue screen so i re-installed win 7 and re did all my drivers and still bsod latest dump files attached...i think it may be time to see the doc.
My System SpecsSystem Spec
26 Nov 2010   #6
Asats

windows 7 64 bit
 
 

here is a minidup file after i enabled driver verifier thanks in advance
My System SpecsSystem Spec
26 Nov 2010   #7
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Neither of these dumps are Driver Verifier enabled dumps; but that's OK. The latest dump blames your NTFS file system and memory corruption. The other one blames a system driver and memory corruption.
Quote:
Error code 24, NTFS_FILE_SYSTEM. Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure.

Error code 3B, SYSTEM_SERVICE_EXCEPTION. Usual causes: System service, Device driver, graphics driver, ?memory.
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0285a000 PsLoadedModuleList = 0xfffff800`02a97e50
Debug session time: Fri Nov 26 09:04:13.515 2010 (GMT-5)
System Uptime: 0 days 0:07:40.419
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88003b3b168, fffff88003b3a9d0, fffff880010d672f}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+26f )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88003b3b168
Arg3: fffff88003b3a9d0
Arg4: fffff880010d672f

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


EXCEPTION_RECORD:  fffff88003b3b168 -- (.exr 0xfffff88003b3b168)
ExceptionAddress: fffff880010d672f (Ntfs!NtfsCommonClose+0x000000000000026f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003b3a9d0 -- (.cxr 0xfffff88003b3a9d0)
rax=ffabf8a009cf0478 rbx=fffffa8003c6e840 rcx=fffff8a009c140d8
rdx=0000000000000000 rsi=fffff8a006e7c2f0 rdi=fffff88003b3b4c8
rip=fffff880010d672f rsp=fffff88003b3b3a0 rbp=fffff88003b3b5c0
 r8=fffffa8005fc37f8  r9=0000000000000009 r10=0000000000000004
r11=fffff8a009cc4470 r12=fffffa8004ed4180 r13=fffffa8005fc3800
r14=fffff8a006e7c688 r15=fffffa8003c9c500
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
Ntfs!NtfsCommonClose+0x26f:
fffff880`010d672f 488908          mov     qword ptr [rax],rcx ds:002b:ffabf8a0`09cf0478=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  1

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_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 fffff80002b020e0
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsCommonClose+26f
fffff880`010d672f 488908          mov     qword ptr [rax],rcx

FAULTING_IP: 
Ntfs!NtfsCommonClose+26f
fffff880`010d672f 488908          mov     qword ptr [rax],rcx

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff880010deadc to fffff880010d672f

STACK_TEXT:  
fffff880`03b3b3a0 fffff880`010deadc : fffffa80`03c6e840 fffff8a0`06e7c420 fffff8a0`06e7c2f0 fffffa80`04ed4180 : Ntfs!NtfsCommonClose+0x26f
fffff880`03b3b470 fffff880`00e6b23f : fffff880`03b3b601 fffffa80`03c9d410 fffff880`03b38000 00000000`00000002 : Ntfs!NtfsFsdClose+0x2dc
fffff880`03b3b570 fffff880`00e696df : fffffa80`048e19e0 fffffa80`03c9d410 fffffa80`04512e00 fffffa80`03c9d410 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`03b3b600 fffff800`02be078e : fffffa80`03c9c540 fffffa80`048ac890 00000000`00000000 fffffa80`048e19e0 : fltmgr!FltpDispatch+0xcf
fffff880`03b3b660 fffff800`028cf8b4 : 00000000`00000011 fffffa80`03c9c540 fffffa80`039e1f30 fffffa80`039ea7b0 : nt!IopDeleteFile+0x11e
fffff880`03b3b6f0 fffff800`028ba431 : fffffa80`03c9c540 00000000`00000002 00000000`00000000 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`03b3b750 fffff800`028bdd1c : 00000000`00000000 00000000`00000000 fffffa80`03cdf7f0 00000000`00000000 : nt!CcDeleteSharedCacheMap+0x2fd
fffff880`03b3b7c0 fffff800`028ad5d4 : fffffa80`03c7e000 fffff880`03b3b8a8 00000000`00000000 00000000`00000001 : nt!CcWriteBehind+0x5bc
fffff880`03b3b870 fffff800`02bc59f5 : fffffa80`03cce5d0 fffffa80`00000000 fffffa80`039e1f01 fffff800`02bbb700 : nt!CcWaitForUninitializeCacheMap+0x138
fffff880`03b3b920 fffff800`02bbb013 : fffff880`03b3bb80 00000000`00000000 00000000`00000000 fffff880`03b3bb78 : nt!MmCreateSection+0x529
fffff880`03b3bb30 fffff800`028c9993 : fffffa80`03c986d0 00000000`000ce258 fffff880`03b3bbc8 00000000`00000000 : nt!NtCreateSection+0x162
fffff880`03b3bbb0 00000000`776e01fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000ce238 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776e01fa


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsCommonClose+26f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff88003b3a9d0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonClose+26f

BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonClose+26f

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

Debug session time: Fri Nov 26 13:40:28.679 2010 (GMT-5)
System Uptime: 0 days 0:26:46.583
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002b98227, fffff880009d2ee0, 0}

Probably caused by : ntkrnlmp.exe ( nt!PspDereferenceQuotaBlock+17 )

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

3: 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: fffff80002b98227, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880009d2ee0, 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!PspDereferenceQuotaBlock+17
fffff800`02b98227 f0838108020000ff lock add dword ptr [rcx+208h],0FFFFFFFFh

CONTEXT:  fffff880009d2ee0 -- (.cxr 0xfffff880009d2ee0)
rax=0076000000000000 rbx=0076000000000000 rcx=0076000000000000
rdx=fffff80002860000 rsi=0000000000000000 rdi=fffffa8003a15080
rip=fffff80002b98227 rsp=fffff880009d38b0 rbp=fffffa8003abb490
 r8=fffff8a008c15930  r9=0000000000000000 r10=000000000000024c
r11=fffff880009d3988 r12=0000000000000000 r13=0000000000000000
r14=fffffa8003abb490 r15=0000000000000070
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!PspDereferenceQuotaBlock+0x17:
fffff800`02b98227 f0838108020000ff lock add dword ptr [rcx+208h],0FFFFFFFFh ds:002b:00760000`00000208=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  mscorsvw.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002b98227

STACK_TEXT:  
fffff880`009d38b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspDereferenceQuotaBlock+0x17


FOLLOWUP_IP: 
nt!PspDereferenceQuotaBlock+17
fffff800`02b98227 f0838108020000ff lock add dword ptr [rcx+208h],0FFFFFFFFh

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!PspDereferenceQuotaBlock+17

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff880009d2ee0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!PspDereferenceQuotaBlock+17

BUCKET_ID:  X64_0x3B_nt!PspDereferenceQuotaBlock+17

Followup: MachineOwner
---------
I found an almost guaranteed BSOD maker on your system.
Quote:
Code:
ASACPI.sys   Sun Mar 27 22:30:36 2005
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
I also find these two outdated drivers on your system. The one red font is quite obsolete. Update these drivers. Outdated drivers can and do cause memory corruption.
Quote:
nvlddmkm.sys Thu May 14 16:48:07 2009 - nVidia Video drivers. Drivers - Download NVIDIA Drivers

nvm62x64.sys Fri Oct 17 17:01:06 2008 - nVidia Ethernet Networking Driver (nForce chipset driver) Drivers - Download NVIDIA Drivers
Because of the error code 24, I suggest that you run Check Disk.
Quote:
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 Windows 7)

Copy/paste the results into your next post.

Next run Memtest to test your RAM following the instructions in this tutorial:
RAM - Test with Memtest86+. Let Memtest run for at least 7 passes. This will take 6-8 hours. Post back with your results.
My System SpecsSystem Spec
28 Nov 2010   #8
Asats

windows 7 64 bit
 
 

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 11/26/2010 6:05:25 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Newell-PC
Description:

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

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 3)...
73728 file records processed.
File verification completed.
67 large file records processed.
0 bad file records processed.
0 EA records processed.
44 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
106120 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
73728 file SDs/SIDs processed.
Cleaning up 44 unused index entries from index $SII of file 0x9.
Cleaning up 44 unused index entries from index $SDH of file 0x9.
Cleaning up 44 unused security descriptors.
Security descriptor verification completed.
16197 data files processed.
CHKDSK is verifying Usn Journal...
12203856 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
488282111 KB total disk space.
43748476 KB in 57348 files.
42360 KB in 16198 indexes.
0 KB in bad sectors.
167103 KB in use by the system.
65536 KB occupied by the log file.
444324172 KB available on disk.
4096 bytes in each allocation unit.
122070527 total allocation units on disk.
111081043 allocation units available on disk.
Internal Info:
00 20 01 00 56 1f 01 00 fc 41 02 00 00 00 00 00 . ..V....A......
12 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
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-11-26T23:05:25.000000000Z" />
<EventRecordID>1809</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Newell-PC</Computer>
<Security />
</System>
<EventData>
<Data>
Checking file system on C:
The type of the file system is NTFS.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 3)...
73728 file records processed.
File verification completed.
67 large file records processed.
0 bad file records processed.
0 EA records processed.
44 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
106120 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
73728 file SDs/SIDs processed.
Cleaning up 44 unused index entries from index $SII of file 0x9.
Cleaning up 44 unused index entries from index $SDH of file 0x9.
Cleaning up 44 unused security descriptors.
Security descriptor verification completed.
16197 data files processed.
CHKDSK is verifying Usn Journal...
12203856 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
488282111 KB total disk space.
43748476 KB in 57348 files.
42360 KB in 16198 indexes.
0 KB in bad sectors.
167103 KB in use by the system.
65536 KB occupied by the log file.
444324172 KB available on disk.
4096 bytes in each allocation unit.
122070527 total allocation units on disk.
111081043 allocation units available on disk.
Internal Info:
00 20 01 00 56 1f 01 00 fc 41 02 00 00 00 00 00 . ..V....A......
12 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
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>
My System SpecsSystem Spec
28 Nov 2010   #9
Asats

windows 7 64 bit
 
 

also latest bsod: internet was out for two days....didnt blue screen. internet comes up try to download warcraft bsod
My System SpecsSystem Spec
28 Nov 2010   #10
CarlTR6

Windows 7 Ultimate 32 bit
 
 

The good news is that your hard drive looks fine. Your latest dump blames a video driver, which is up to date. The dump indicates memory corruption. This is a Driver Verifier enabled dump blaming nvlddmkm.sys. Turn off Driver Verifier for now.

Did you run Memtest as suggested above? If not it is time to run it. RAM - Test with Memtest86+. Let Memtest run for at least 7 passes. This will take 6-8 hours. Post back with your results.

After testing your RAM, if there are no errors, test your video card with Furmark following the instructions in this tutorial: Video Card - Stress Test with Furmark. Post back with your results.
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02858000 PsLoadedModuleList = 0xfffff800`02a95e50
Debug session time: Sun Nov 28 11:47:13.609 2010 (GMT-5)
System Uptime: 0 days 2:34:41.545
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa80059d5030, ff00fa80059d5030, fffffa80059d5030}

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 : Pool_Corruption ( nt!ExDeferredFreePool+1175 )

Followup: Pool_corruption
---------

3: 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: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa80059d5030, the pool entry being checked.
Arg3: ff00fa80059d5030, the read back flink freelist value (should be the same as 2).
Arg4: fffffa80059d5030, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800029fb598 to fffff800028c8740

STACK_TEXT:  
fffff880`02ffd3c8 fffff800`029fb598 : 00000000`00000019 00000000`00000003 fffffa80`059d5030 ff00fa80`059d5030 : nt!KeBugCheckEx
fffff880`02ffd3d0 fffff880`049be79d : fffffa80`04614970 fffffa80`039f4000 00000000`4d52564e fffff880`4d52564e : nt!ExDeferredFreePool+0x1175
fffff880`02ffd480 fffffa80`04614970 : fffffa80`039f4000 00000000`4d52564e fffff880`4d52564e 00000000`00000010 : nvlddmkm+0x1b379d
fffff880`02ffd488 fffffa80`039f4000 : 00000000`4d52564e fffff880`4d52564e 00000000`00000010 fffff880`049c518c : 0xfffffa80`04614970
fffff880`02ffd490 00000000`4d52564e : fffff880`4d52564e 00000000`00000010 fffff880`049c518c fffffa80`04622610 : 0xfffffa80`039f4000
fffff880`02ffd498 fffff880`4d52564e : 00000000`00000010 fffff880`049c518c fffffa80`04622610 00000000`00000000 : 0x4d52564e
fffff880`02ffd4a0 00000000`00000010 : fffff880`049c518c fffffa80`04622610 00000000`00000000 fffffa80`04614970 : 0xfffff880`4d52564e
fffff880`02ffd4a8 fffff880`049c518c : fffffa80`04622610 00000000`00000000 fffffa80`04614970 fffffa80`05df6810 : 0x10
fffff880`02ffd4b0 fffffa80`04622610 : 00000000`00000000 fffffa80`04614970 fffffa80`05df6810 fffffa80`05df6810 : nvlddmkm+0x1ba18c
fffff880`02ffd4b8 00000000`00000000 : fffffa80`04614970 fffffa80`05df6810 fffffa80`05df6810 fffff880`04bf98f7 : 0xfffffa80`04622610


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+1175
fffff800`029fb598 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+1175

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_VRF_nt!ExDeferredFreePool+1175

BUCKET_ID:  X64_0x19_3_VRF_nt!ExDeferredFreePool+1175

Followup: Pool_corruption
---------

3: kd> lmtsn
          ^ Syntax error in 'lmtsn'
3: kd> lmtsmn
start             end                 module name
fffff880`03f23000 fffff880`03f61000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00f77000 fffff880`00fce000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02c22000 fffff880`02cac000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04375000 fffff880`0438b000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`01800000 fffff880`01815000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00ea4000 fffff880`00eaf000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`02df2000 fffff880`02dfa000   ASACPI   ASACPI.sys   Wed May 13 21:25:17 2009 (4A0B72FD)
fffff880`00e9b000 fffff880`00ea4000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00db0000 fffff880`00dda000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`0191c000 fffff880`01923000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`019c8000 fffff880`019d9000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`054e9000 fffff880`05507000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`007d0000 fffff960`007f7000   cdd      cdd.dll      unavailable (00000000)
fffff880`018bc000 fffff880`018e6000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00cf0000 fffff880`00db0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01856000 fffff880`01886000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c92000 fffff880`00cf0000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01146000 fffff880`011b9000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`04365000 fffff880`04375000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`05e12000 fffff880`05e20000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`02c00000 fffff880`02c1e000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`02de3000 fffff880`02df2000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01200000 fffff880`01216000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`05fdc000 fffff880`05ffe000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`05790000 fffff880`05799000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`05e20000 fffff880`05e2c000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`05799000 fffff880`057ac000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`05e06000 fffff880`05e12000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04222000 fffff880`04316000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`04316000 fffff880`0435c000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`010d4000 fffff880`010e8000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01088000 fffff880`010d4000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`013f6000 fffff880`01400000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`011b9000 fffff880`011f3000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0148b000 fffff880`014d5000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`0280f000 fffff800`02858000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`03eff000 fffff880`03f23000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`057ba000 fffff880`057d3000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`057d3000 fffff880`057db080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`057ac000 fffff880`057ba000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`05421000 fffff880`054e9000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`015eb000 fffff880`015f4000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`01815000 fffff880`01833000   i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01833000 fffff880`01842000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00bb6000 fffff800`00bc0000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`03e00000 fffff880`03e43000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`013cb000 fffff880`013e5000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01460000 fffff880`0148b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`05e00000 fffff880`05e05200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`05623000 fffff880`05638000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`05600000 fffff880`05623000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c71000 fffff880`00c7e000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`057e9000 fffff880`057f7000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`043ea000 fffff880`043f9000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`057dc000 fffff880`057e9000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00e81000 fffff880`00e9b000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`018e6000 fffff880`01913000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
fffff880`06932000 fffff880`06942000   MpNWMon  MpNWMon.sys  Sat Mar 20 01:58:00 2010 (4BA463E8)
fffff880`05507000 fffff880`0551f000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`0551f000 fffff880`0554c000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`0554c000 fffff880`0559a000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`0559a000 fffff880`055bd000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`01981000 fffff880`0198c000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fd7000 fffff880`00fe1000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`010e8000 fffff880`01146000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`02dd8000 fffff880`02de3000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`015d9000 fffff880`015eb000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`014e7000 fffff880`015d9000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`043af000 fffff880`043bb000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`043bb000 fffff880`043ea000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0573e000 fffff880`05753000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02d20000 fffff880`02d2f000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02cac000 fffff880`02cf1000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`0198c000 fffff880`0199d000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02dcc000 fffff880`02dd8000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02858000 fffff800`02e34000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01228000 fffff880`013cb000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01913000 fffff880`0191c000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`053e5000 fffff880`053e6180   nvBridge nvBridge.kmd Sat Oct 16 13:06:16 2010 (4CB9DB88)
fffff880`0480b000 fffff880`053e4a80   nvlddmkm nvlddmkm.sys Sat Oct 16 13:12:46 2010 (4CB9DD0E)
fffff880`03f61000 fffff880`03fb5080   nvmf6264 nvmf6264.sys Thu Aug 12 07:46:06 2010 (4C63DEFE)
fffff880`015f4000 fffff880`015ff000   nvsmu    nvsmu.sys    Thu Nov 12 09:43:42 2009 (4AFC1F1E)
fffff880`02cfa000 fffff880`02d20000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00e40000 fffff880`00e55000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e00000 fffff880`00e33000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e6a000 fffff880`00e71000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00e71000 fffff880`00e81000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013e5000 fffff880`013f6000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`06421000 fffff880`064c7000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`05753000 fffff880`05790000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c7e000 fffff880`00c92000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`0438b000 fffff880`043af000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04200000 fffff880`0421b000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`03fb6000 fffff880`03fd7000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`03fd7000 fffff880`03ff1000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`02d7b000 fffff880`02dcc000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`01966000 fffff880`0196f000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0196f000 fffff880`01978000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01978000 fffff880`01981000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0104c000 fffff880`01086000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`05638000 fffff880`05650000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`064c7000 fffff880`064d2000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`01842000 fffff880`0184e000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`02d2f000 fffff880`02d4c000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`014d5000 fffff880`014dd000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`06942000 fffff880`069b3000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
fffff880`0689c000 fffff880`06932000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`06511000 fffff880`06578000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`064d2000 fffff880`064ff000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`043f9000 fffff880`043fa480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`064ff000 fffff880`06511000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`019bb000 fffff880`019c8000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`0199d000 fffff880`019bb000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02d67000 fffff880`02d7b000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00570000 fffff960`0057a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`019d9000 fffff880`019ff000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`053e7000 fffff880`053f9000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`05e2c000 fffff880`05e2df00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`03eee000 fffff880`03eff000   usbehci  usbehci.sys  Sat Oct 24 00:27:33 2009 (4AE28235)
fffff880`056e4000 fffff880`0573e000   usbhub   usbhub.sys   Sat Oct 24 00:28:24 2009 (4AE28268)
fffff880`01216000 fffff880`01221000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`03e98000 fffff880`03eee000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`00e33000 fffff880`00e40000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01923000 fffff880`01931000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`05e34000 fffff880`05fdc000   viahduaa viahduaa.sys Tue Oct 20 23:30:30 2009 (4ADE8056)
fffff880`01931000 fffff880`01956000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00e55000 fffff880`00e6a000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01000000 fffff880`0104c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02d4c000 fffff880`02d67000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`01956000 fffff880`01966000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00ec4000 fffff880`00f68000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f68000 fffff880`00f77000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02cf1000 fffff880`02cfa000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00010000 fffff960`0031f000   win32k   win32k.sys   unavailable (00000000)
fffff880`0435c000 fffff880`04365000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00fce000 fffff880`00fd7000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)

Unloaded modules:
fffff880`01886000 fffff880`01894000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01894000 fffff880`018a0000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`018a0000 fffff880`018a9000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`018a9000 fffff880`018bc000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
My System SpecsSystem Spec
Reply

 BSOD




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 18:08.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App