Mike73059
asked on
Windows 7 Blue Screen. Boot issues.
I'm running a custom built Windows 7 machine.
i7 920, EVGA SLI LE, Dual EVGA 260GTX, Raid 10 Configuration with 4 500g HDD's. The OS is installed on a 64g SSD Patriot Torx drive.
The computer started blue screening on boot after the windows loading screen about a month ago. it has gotten worse over time (more frequent). But this is quite intermittent. it will boot sometimes just on reboot after blue screen. Also after this blue screen occurs the windows restore console comes up, so i'm not quite sure what exactly is occurring that it wants to restore.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: d1
BCP1: FFFFF88010E00140
BCP2: 000000000000000E
BCP3: 0000000000000001
BCP4: FFFFF8800498412E
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\122209 -14312-01. dmp
C:\Users\Mike\AppData\Loca l\Temp\WER -23718-0.s ysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\ erofflps.t xt
-------------------------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- -----
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: d1
BCP1: FFFFF88010E00140
BCP2: 000000000000000E
BCP3: 0000000000000001
BCP4: FFFFF8800499112E
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\010110 -14640-01. dmp
C:\Users\Mike\AppData\Loca l\Temp\WER -27921-0.s ysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\ erofflps.t xt
Please help me solve this problem =)
i7 920, EVGA SLI LE, Dual EVGA 260GTX, Raid 10 Configuration with 4 500g HDD's. The OS is installed on a 64g SSD Patriot Torx drive.
The computer started blue screening on boot after the windows loading screen about a month ago. it has gotten worse over time (more frequent). But this is quite intermittent. it will boot sometimes just on reboot after blue screen. Also after this blue screen occurs the windows restore console comes up, so i'm not quite sure what exactly is occurring that it wants to restore.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: d1
BCP1: FFFFF88010E00140
BCP2: 000000000000000E
BCP3: 0000000000000001
BCP4: FFFFF8800498412E
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\122209
C:\Users\Mike\AppData\Loca
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\
--------------------------
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: d1
BCP1: FFFFF88010E00140
BCP2: 000000000000000E
BCP3: 0000000000000001
BCP4: FFFFF8800499112E
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\010110
C:\Users\Mike\AppData\Loca
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\
Please help me solve this problem =)
ASKER
They all refer to your NVidia drivers (nvlddmkm.sys).
As a first means, I'd suggest to completely uninstall the present drivers, and then update to the newest version.
As a first means, I'd suggest to completely uninstall the present drivers, and then update to the newest version.
Here's the analysis:
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c40e50
Debug session time: Fri Jan 1 22:49:16.906 2010 (GMT+1)
System Uptime: 0 days 0:00:14.000
Loading Kernel Symbols
...................................................................................................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff88010e00140, e, 1, fffff8800499112e}
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 : nvlddmkm.sys ( nvlddmkm+15112e )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff88010e00140, memory referenced
Arg2: 000000000000000e, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800499112e, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cab0e0
fffff88010e00140
CURRENT_IRQL: e
FAULTING_IP:
nvlddmkm+15112e
fffff880`0499112e 44890c88 mov dword ptr [rax+rcx*4],r9d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9c250 -- (.trap 0xfffff80000b9c250)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88010e00000 rbx=fffffa800863e1b0 rcx=0000000000000050
rdx=fffffa800863e1b0 rsi=0000000000000001 rdi=fffff880049f22bf
rip=fffff8800499112e rsp=fffff80000b9c3e8 rbp=fffffa8007bb2010
r8=0000000000000140 r9=0000000000000000 r10=fffff80002bede80
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nvlddmkm+0x15112e:
fffff880`0499112e 44890c88 mov dword ptr [rax+rcx*4],r9d ds:0055:fffff880`10e00140=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a74469 to fffff80002a74f00
STACK_TEXT:
fffff800`00b9c108 fffff800`02a74469 : 00000000`0000000a fffff880`10e00140 00000000`0000000e 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c110 fffff800`02a730e0 : 00000018`00000000 00000000`00000000 0000057f`f83a0cc8 fffffa80`05a28000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c250 fffff880`0499112e : fffff880`04d15828 00000000`00000001 00000000`00000000 fffff800`02bede80 : nt!KiPageFault+0x260
fffff800`00b9c3e8 fffff880`04d15828 : 00000000`00000001 00000000`00000000 fffff800`02bede80 fffff880`04987db0 : nvlddmkm+0x15112e
fffff800`00b9c3f0 00000000`00000001 : 00000000`00000000 fffff800`02bede80 fffff880`04987db0 ffffffff`40c00288 : nvlddmkm+0x4d5828
fffff800`00b9c3f8 00000000`00000000 : fffff800`02bede80 fffff880`04987db0 ffffffff`40c00288 fffff800`02bede80 : 0x1
fffff800`00b9c400 fffff800`02bede80 : fffff880`04987db0 ffffffff`40c00288 fffff800`02bede80 fffff880`04085760 : 0x0
fffff800`00b9c408 fffff880`04987db0 : ffffffff`40c00288 fffff800`02bede80 fffff880`04085760 fffff800`02bede80 : nt!KiInitialPCR+0x180
fffff800`00b9c410 ffffffff`40c00288 : fffff800`02bede80 fffff880`04085760 fffff800`02bede80 fffff800`00b9cc58 : nvlddmkm+0x147db0
fffff800`00b9c418 fffff800`02bede80 : fffff880`04085760 fffff800`02bede80 fffff800`00b9cc58 fffffa80`0863e1b0 : 0xffffffff`40c00288
fffff800`00b9c420 fffff880`04085760 : fffff800`02bede80 fffff800`00b9cc58 fffffa80`0863e1b0 00000000`00000001 : nt!KiInitialPCR+0x180
fffff800`00b9c428 fffff800`02bede80 : fffff800`00b9cc58 fffffa80`0863e1b0 00000000`00000001 fffff880`049c27d3 : afd!AfdTimerWheel+0x40
fffff800`00b9c430 fffff800`00b9cc58 : fffffa80`0863e1b0 00000000`00000001 fffff880`049c27d3 00000000`00000000 : nt!KiInitialPCR+0x180
fffff800`00b9c438 fffffa80`0863e1b0 : 00000000`00000001 fffff880`049c27d3 00000000`00000000 00000000`00000000 : 0xfffff800`00b9cc58
fffff800`00b9c440 00000000`00000001 : fffff880`049c27d3 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffffa80`0863e1b0
fffff800`00b9c448 fffff880`049c27d3 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff880`04987db0 : 0x1
fffff800`00b9c450 00000000`00000000 : 00000000`00000000 00000000`00000001 fffff880`04987db0 00000000`090013c0 : nvlddmkm+0x1827d3
fffff800`00b9c458 00000000`00000000 : 00000000`00000001 fffff880`04987db0 00000000`090013c0 ffffffff`ff676980 : 0x0
fffff800`00b9c460 00000000`00000001 : fffff880`04987db0 00000000`090013c0 ffffffff`ff676980 fffffa80`07986000 : 0x0
fffff800`00b9c468 fffff880`04987db0 : 00000000`090013c0 ffffffff`ff676980 fffffa80`07986000 fffff800`02bf0080 : 0x1
fffff800`00b9c470 00000000`090013c0 : ffffffff`ff676980 fffffa80`07986000 fffff800`02bf0080 fffff800`02bfbc40 : nvlddmkm+0x147db0
fffff800`00b9c478 ffffffff`ff676980 : fffffa80`07986000 fffff800`02bf0080 fffff800`02bfbc40 fffffa80`079061b0 : 0x90013c0
fffff800`00b9c480 fffffa80`07986000 : fffff800`02bf0080 fffff800`02bfbc40 fffffa80`079061b0 fffffa80`07bb2010 : 0xffffffff`ff676980
fffff800`00b9c488 fffff800`02bf0080 : fffff800`02bfbc40 fffffa80`079061b0 fffffa80`07bb2010 fffff880`049f7f33 : 0xfffffa80`07986000
fffff800`00b9c490 fffff800`02bfbc40 : fffffa80`079061b0 fffffa80`07bb2010 fffff880`049f7f33 fffffa80`079061b0 : nt!KiInitialPCR+0x2380
fffff800`00b9c498 fffffa80`079061b0 : fffffa80`07bb2010 fffff880`049f7f33 fffffa80`079061b0 fffffa80`07bb2010 : nt!KiInitialThread
fffff800`00b9c4a0 fffffa80`07bb2010 : fffff880`049f7f33 fffffa80`079061b0 fffffa80`07bb2010 fffffa80`079061b0 : 0xfffffa80`079061b0
fffff800`00b9c4a8 fffff880`049f7f33 : fffffa80`079061b0 fffffa80`07bb2010 fffffa80`079061b0 fffffa80`05ad6980 : 0xfffffa80`07bb2010
fffff800`00b9c4b0 fffffa80`079061b0 : fffffa80`07bb2010 fffffa80`079061b0 fffffa80`05ad6980 ffffffff`ff676980 : nvlddmkm+0x1b7f33
fffff800`00b9c4b8 fffffa80`07bb2010 : fffffa80`079061b0 fffffa80`05ad6980 ffffffff`ff676980 00000000`00000000 : 0xfffffa80`079061b0
fffff800`00b9c4c0 fffffa80`079061b0 : fffffa80`05ad6980 ffffffff`ff676980 00000000`00000000 fffffa80`05ad6df0 : 0xfffffa80`07bb2010
fffff800`00b9c4c8 fffffa80`05ad6980 : ffffffff`ff676980 00000000`00000000 fffffa80`05ad6df0 fffff880`04069151 : 0xfffffa80`079061b0
fffff800`00b9c4d0 ffffffff`ff676980 : 00000000`00000000 fffffa80`05ad6df0 fffff880`04069151 00000000`00000000 : 0xfffffa80`05ad6980
fffff800`00b9c4d8 00000000`00000000 : fffffa80`05ad6df0 fffff880`04069151 00000000`00000000 fffff880`04987db0 : 0xffffffff`ff676980
fffff800`00b9c4e0 fffffa80`05ad6df0 : fffff880`04069151 00000000`00000000 fffff880`04987db0 00000000`00000102 : 0x0
fffff800`00b9c4e8 fffff880`04069151 : 00000000`00000000 fffff880`04987db0 00000000`00000102 fffff880`043b7698 : 0xfffffa80`05ad6df0
fffff800`00b9c4f0 fffff800`02a80fa6 : fffff800`00b9c678 00000000`00000005 00000000`00000000 00000000`00000000 : afd!AfdTimerWheelHandler+0x141
fffff800`00b9c570 fffff800`02a80326 : fffffa80`08631400 00000000`00000380 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02a80e7e : 00000000`08583b00 fffff800`00b9cc58 00000000`00000380 fffff800`02bf1288 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02a80697 : 00000000`0252ccc8 00000000`00000380 00000000`0252cc1e 00000000`00000080 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02a7d6fa : fffff800`02bede80 fffff800`02bfbc40 00000000`00000000 fffff880`0168ac50 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+15112e
fffff880`0499112e 44890c88 mov dword ptr [rax+rcx*4],r9d
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nvlddmkm+15112e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4abfff56
FAILURE_BUCKET_ID: X64_0xD1_W_nvlddmkm+15112e
BUCKET_ID: X64_0xD1_W_nvlddmkm+15112e
Followup: MachineOwner
---------
0: kd> .trap 0xfffff80000b9c250
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88010e00000 rbx=fffffa800863e1b0 rcx=0000000000000050
rdx=fffffa800863e1b0 rsi=0000000000000001 rdi=fffff880049f22bf
rip=fffff8800499112e rsp=fffff80000b9c3e8 rbp=fffffa8007bb2010
r8=0000000000000140 r9=0000000000000000 r10=fffff80002bede80
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nvlddmkm+0x15112e:
fffff880`0499112e 44890c88 mov dword ptr [rax+rcx*4],r9d ds:0055:fffff880`10e00140=????????
0: kd> kb
*** Stack trace for last set context - .thread/.cxr resets it
RetAddr : Args to Child : Call Site
fffff880`04d15828 : 00000000`00000001 00000000`00000000 fffff800`02bede80 fffff880`04987db0 : nvlddmkm+0x15112e
00000000`00000001 : 00000000`00000000 fffff800`02bede80 fffff880`04987db0 ffffffff`40c00288 : nvlddmkm+0x4d5828
00000000`00000000 : fffff800`02bede80 fffff880`04987db0 ffffffff`40c00288 fffff800`02bede80 : 0x1
fffff800`02bede80 : fffff880`04987db0 ffffffff`40c00288 fffff800`02bede80 fffff880`04085760 : 0x0
fffff880`04987db0 : ffffffff`40c00288 fffff800`02bede80 fffff880`04085760 fffff800`02bede80 : nt!KiInitialPCR+0x180
ffffffff`40c00288 : fffff800`02bede80 fffff880`04085760 fffff800`02bede80 fffff800`00b9cc58 : nvlddmkm+0x147db0
fffff800`02bede80 : fffff880`04085760 fffff800`02bede80 fffff800`00b9cc58 fffffa80`0863e1b0 : 0xffffffff`40c00288
fffff880`04085760 : fffff800`02bede80 fffff800`00b9cc58 fffffa80`0863e1b0 00000000`00000001 : nt!KiInitialPCR+0x180
fffff800`02bede80 : fffff800`00b9cc58 fffffa80`0863e1b0 00000000`00000001 fffff880`049c27d3 : afd!AfdTimerWheel+0x40
fffff800`00b9cc58 : fffffa80`0863e1b0 00000000`00000001 fffff880`049c27d3 00000000`00000000 : nt!KiInitialPCR+0x180
fffffa80`0863e1b0 : 00000000`00000001 fffff880`049c27d3 00000000`00000000 00000000`00000000 : 0xfffff800`00b9cc58
00000000`00000001 : fffff880`049c27d3 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffffa80`0863e1b0
fffff880`049c27d3 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff880`04987db0 : 0x1
00000000`00000000 : 00000000`00000000 00000000`00000001 fffff880`04987db0 00000000`090013c0 : nvlddmkm+0x1827d3
00000000`00000000 : 00000000`00000001 fffff880`04987db0 00000000`090013c0 ffffffff`ff676980 : 0x0
00000000`00000001 : fffff880`04987db0 00000000`090013c0 ffffffff`ff676980 fffffa80`07986000 : 0x0
fffff880`04987db0 : 00000000`090013c0 ffffffff`ff676980 fffffa80`07986000 fffff800`02bf0080 : 0x1
00000000`090013c0 : ffffffff`ff676980 fffffa80`07986000 fffff800`02bf0080 fffff800`02bfbc40 : nvlddmkm+0x147db0
ffffffff`ff676980 : fffffa80`07986000 fffff800`02bf0080 fffff800`02bfbc40 fffffa80`079061b0 : 0x90013c0
fffffa80`07986000 : fffff800`02bf0080 fffff800`02bfbc40 fffffa80`079061b0 fffffa80`07bb2010 : 0xffffffff`ff676980
0: kd> lmnt
start end module name
fffff800`00bad000 fffff800`00bb7000 kdcom kdcom.dll Tue Jul 14 03:31:07 2009 (4A5BDFDB)
fffff800`02a03000 fffff800`02fe0000 nt ntkrnlmp.exe Tue Jul 14 01:40:48 2009 (4A5BC600)
fffff800`02fe0000 fffff800`03029000 hal hal.dll Tue Jul 14 03:27:36 2009 (4A5BDF08)
fffff880`00c04000 fffff880`00c48000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 03:29:10 2009 (4A5BDF66)
fffff880`00c48000 fffff880`00c5c000 PSHED PSHED.dll Tue Jul 14 03:32:23 2009 (4A5BE027)
fffff880`00c5c000 fffff880`00cba000 CLFS CLFS.SYS Tue Jul 14 01:19:57 2009 (4A5BC11D)
fffff880`00cba000 fffff880`00d7a000 CI CI.dll Tue Jul 14 03:32:13 2009 (4A5BE01D)
fffff880`00d7a000 fffff880`00dd6000 volmgrx volmgrx.sys Tue Jul 14 01:20:33 2009 (4A5BC141)
fffff880`00e00000 fffff880`00e4c000 Rt64win7 Rt64win7.sys Tue Nov 17 18:01:19 2009 (4B02D6DF)
fffff880`00e55000 fffff880`00ef9000 Wdf01000 Wdf01000.sys Tue Jul 14 01:22:07 2009 (4A5BC19F)
fffff880`00ef9000 fffff880`00f08000 WDFLDR WDFLDR.SYS Tue Jul 14 01:19:54 2009 (4A5BC11A)
fffff880`00f08000 fffff880`00f5f000 ACPI ACPI.sys Tue Jul 14 01:19:34 2009 (4A5BC106)
fffff880`00f5f000 fffff880`00f68000 WMILIB WMILIB.SYS Tue Jul 14 01:19:51 2009 (4A5BC117)
fffff880`00f68000 fffff880`00f72000 msisadrv msisadrv.sys Tue Jul 14 01:19:26 2009 (4A5BC0FE)
fffff880`00f72000 fffff880`00fa5000 pci pci.sys Tue Jul 14 01:19:51 2009 (4A5BC117)
fffff880`00fa5000 fffff880`00fb2000 vdrvroot vdrvroot.sys Tue Jul 14 02:01:31 2009 (4A5BCADB)
fffff880`00fb2000 fffff880`00fc7000 partmgr partmgr.sys Tue Jul 14 01:19:58 2009 (4A5BC11E)
fffff880`00fc7000 fffff880`00fdc000 volmgr volmgr.sys Tue Jul 14 01:19:57 2009 (4A5BC11D)
fffff880`00fdc000 fffff880`00ff6000 mountmgr mountmgr.sys Tue Jul 14 01:19:54 2009 (4A5BC11A)
fffff880`01000000 fffff880`01014000 fileinfo fileinfo.sys Tue Jul 14 01:34:25 2009 (4A5BC481)
fffff880`01014000 fffff880`01072000 msrpc msrpc.sys Tue Jul 14 01:21:32 2009 (4A5BC17C)
fffff880`01082000 fffff880`011a0000 iaStorV iaStorV.sys Wed Apr 08 18:57:17 2009 (49DCD76D)
fffff880`011a0000 fffff880`011ab000 amdxata amdxata.sys Tue May 19 19:56:59 2009 (4A12F2EB)
fffff880`011ab000 fffff880`011f7000 fltmgr fltmgr.sys Tue Jul 14 01:19:59 2009 (4A5BC11F)
fffff880`01200000 fffff880`01224000 rasl2tp rasl2tp.sys Tue Jul 14 02:10:11 2009 (4A5BCCE3)
fffff880`0123b000 fffff880`013de000 Ntfs Ntfs.sys Tue Jul 14 01:20:47 2009 (4A5BC14F)
fffff880`013de000 fffff880`013f8000 ksecdd ksecdd.sys Tue Jul 14 01:20:54 2009 (4A5BC156)
fffff880`01400000 fffff880`0143a000 fvevol fvevol.sys Tue Jul 14 01:22:15 2009 (4A5BC1A7)
fffff880`0143a000 fffff880`01450000 disk disk.sys Tue Jul 14 01:19:57 2009 (4A5BC11D)
fffff880`01450000 fffff880`01480000 CLASSPNP CLASSPNP.SYS Tue Jul 14 01:19:58 2009 (4A5BC11E)
fffff880`0148e000 fffff880`014ac000 tdx tdx.sys Tue Jul 14 01:21:15 2009 (4A5BC16B)
fffff880`014ac000 fffff880`014bc000 aswTdi aswTdi.SYS Wed Nov 25 00:49:09 2009 (4B0C70F5)
fffff880`014bc000 fffff880`014c8000 ndistapi ndistapi.sys Tue Jul 14 02:10:00 2009 (4A5BCCD8)
fffff880`014cb000 fffff880`0153e000 cng cng.sys Tue Jul 14 01:49:40 2009 (4A5BC814)
fffff880`0153e000 fffff880`0154f000 pcw pcw.sys Tue Jul 14 01:19:27 2009 (4A5BC0FF)
fffff880`0154f000 fffff880`01559000 Fs_Rec Fs_Rec.sys Tue Jul 14 01:19:45 2009 (4A5BC111)
fffff880`01559000 fffff880`015a5000 volsnap volsnap.sys Tue Jul 14 01:20:08 2009 (4A5BC128)
fffff880`015a5000 fffff880`015df000 rdyboost rdyboost.sys Tue Jul 14 01:34:34 2009 (4A5BC48A)
fffff880`015df000 fffff880`015f5000 AgileVpn AgileVpn.sys Tue Jul 14 02:10:24 2009 (4A5BCCF0)
fffff880`01600000 fffff880`0162b000 ksecpkg ksecpkg.sys Tue Jul 14 01:50:34 2009 (4A5BC84A)
fffff880`0162b000 fffff880`01675000 fwpkclnt fwpkclnt.sys Tue Jul 14 01:21:08 2009 (4A5BC164)
fffff880`01675000 fffff880`01685000 vmstorfl vmstorfl.sys Tue Jul 14 01:42:54 2009 (4A5BC67E)
fffff880`01689000 fffff880`0177b000 ndis ndis.sys Tue Jul 14 01:21:40 2009 (4A5BC184)
fffff880`0177b000 fffff880`017db000 NETIO NETIO.SYS Tue Jul 14 01:21:46 2009 (4A5BC18A)
fffff880`017db000 fffff880`017e3000 spldr spldr.sys Mon May 11 18:56:27 2009 (4A0858BB)
fffff880`017e3000 fffff880`017f5000 mup mup.sys Tue Jul 14 01:23:45 2009 (4A5BC201)
fffff880`017f5000 fffff880`017fe000 hwpolicy hwpolicy.sys Tue Jul 14 01:19:22 2009 (4A5BC0FA)
fffff880`01800000 fffff880`019fd000 tcpip tcpip.sys Tue Jul 14 01:25:34 2009 (4A5BC26E)
fffff880`02c00000 fffff880`02c11000 Npfs Npfs.SYS Tue Jul 14 01:19:48 2009 (4A5BC114)
fffff880`02c11000 fffff880`02c1e000 TDI TDI.SYS Tue Jul 14 01:21:18 2009 (4A5BC16E)
fffff880`02c1e000 fffff880`02c25000 lmimirr lmimirr.sys Wed Apr 11 00:32:45 2007 (461C108D)
fffff880`02c25000 fffff880`02c60000 mafw mafw.sys Wed Jul 29 23:26:58 2009 (4A70BEA2)
fffff880`02d58000 fffff880`02d82000 cdrom cdrom.sys Tue Jul 14 01:19:54 2009 (4A5BC11A)
fffff880`02d82000 fffff880`02d8b000 Null Null.SYS Tue Jul 14 01:19:37 2009 (4A5BC109)
fffff880`02d8b000 fffff880`02d92000 Beep Beep.SYS Tue Jul 14 02:00:13 2009 (4A5BCA8D)
fffff880`02d92000 fffff880`02da0000 vga vga.sys Tue Jul 14 01:38:47 2009 (4A5BC587)
fffff880`02da0000 fffff880`02dc5000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 01:38:51 2009 (4A5BC58B)
fffff880`02dc5000 fffff880`02dd5000 watchdog watchdog.sys Tue Jul 14 01:37:35 2009 (4A5BC53F)
fffff880`02dd5000 fffff880`02dde000 RDPCDD RDPCDD.sys Tue Jul 14 02:16:34 2009 (4A5BCE62)
fffff880`02dde000 fffff880`02de7000 rdpencdd rdpencdd.sys Tue Jul 14 02:16:34 2009 (4A5BCE62)
fffff880`02de7000 fffff880`02df0000 rdprefmp rdprefmp.sys Tue Jul 14 02:16:35 2009 (4A5BCE63)
fffff880`02df0000 fffff880`02dfb000 Msfs Msfs.SYS Tue Jul 14 01:19:47 2009 (4A5BC113)
fffff880`04000000 fffff880`0400c000 nsiproxy nsiproxy.sys Tue Jul 14 01:21:02 2009 (4A5BC15E)
fffff880`0400c000 fffff880`04017000 mssmbios mssmbios.sys Tue Jul 14 01:31:10 2009 (4A5BC3BE)
fffff880`04017000 fffff880`04026000 discache discache.sys Tue Jul 14 01:37:18 2009 (4A5BC52E)
fffff880`04026000 fffff880`04064000 1394ohci 1394ohci.sys Tue Jul 14 02:07:12 2009 (4A5BCC30)
fffff880`04068000 fffff880`040f2000 afd afd.sys Tue Jul 14 01:21:40 2009 (4A5BC184)
fffff880`040f2000 fffff880`040fb000 aswRdr aswRdr.SYS Wed Nov 25 00:48:59 2009 (4B0C70EB)
fffff880`040fb000 fffff880`04140000 netbt netbt.sys Tue Jul 14 01:21:28 2009 (4A5BC178)
fffff880`04140000 fffff880`04149000 wfplwf wfplwf.sys Tue Jul 14 02:09:26 2009 (4A5BCCB6)
fffff880`04149000 fffff880`0416f000 pacer pacer.sys Tue Jul 14 02:09:41 2009 (4A5BCCC5)
fffff880`0416f000 fffff880`0417e000 netbios netbios.sys Tue Jul 14 02:09:26 2009 (4A5BCCB6)
fffff880`0417e000 fffff880`04199000 wanarp wanarp.sys Tue Jul 14 02:10:21 2009 (4A5BCCED)
fffff880`04199000 fffff880`041ad000 termdd termdd.sys Tue Jul 14 02:16:36 2009 (4A5BCE64)
fffff880`041ad000 fffff880`041fe000 rdbss rdbss.sys Tue Jul 14 01:24:09 2009 (4A5BC219)
fffff880`04200000 fffff880`04246000 dxgmms1 dxgmms1.sys Tue Jul 14 01:38:32 2009 (4A5BC578)
fffff880`04246000 fffff880`0429c000 USBPORT USBPORT.SYS Tue Jul 14 02:06:31 2009 (4A5BCC07)
fffff880`0429c000 fffff880`042c0000 HDAudBus HDAudBus.sys Tue Jul 14 02:06:13 2009 (4A5BCBF5)
fffff880`042c0000 fffff880`042cf000 kbdclass kbdclass.sys Tue Jul 14 01:19:50 2009 (4A5BC116)
fffff880`042cf000 fffff880`042dc000 GEARAspiWDM GEARAspiWDM.sys Mon May 18 14:17:04 2009 (4A1151C0)
fffff880`042dc000 fffff880`0435f000 csc csc.sys Tue Jul 14 01:24:26 2009 (4A5BC22A)
fffff880`0435f000 fffff880`0437d000 dfsc dfsc.sys Tue Jul 14 01:23:44 2009 (4A5BC200)
fffff880`0437d000 fffff880`0438e000 blbdrive blbdrive.sys Tue Jul 14 01:35:59 2009 (4A5BC4DF)
fffff880`0438e000 fffff880`043aa000 aswSP aswSP.SYS Wed Nov 25 00:50:24 2009 (4B0C7140)
fffff880`043aa000 fffff880`043d0000 tunnel tunnel.sys Tue Jul 14 02:09:37 2009 (4A5BCCC1)
fffff880`043d0000 fffff880`043e6000 intelppm intelppm.sys Tue Jul 14 01:19:25 2009 (4A5BC0FD)
fffff880`043e6000 fffff880`043ef000 wmiacpi wmiacpi.sys Tue Jul 14 01:31:02 2009 (4A5BC3B6)
fffff880`043ef000 fffff880`043ff000 CompositeBus CompositeBus.sys Tue Jul 14 02:00:33 2009 (4A5BCAA1)
fffff880`04800000 fffff880`0480d000 usbuhci usbuhci.sys Tue Jul 14 02:06:27 2009 (4A5BCC03)
fffff880`0480d000 fffff880`0481e000 usbehci usbehci.sys Tue Jul 14 02:06:30 2009 (4A5BCC06)
fffff880`0481e000 fffff880`0483c000 i8042prt i8042prt.sys Tue Jul 14 01:19:57 2009 (4A5BC11D)
fffff880`04840000 fffff880`05303a80 nvlddmkm nvlddmkm.sys Mon Sep 28 02:12:06 2009 (4ABFFF56)
fffff880`05304000 fffff880`05305180 nvBridge nvBridge.kmd Mon Sep 28 01:46:14 2009 (4ABFF946)
fffff880`05306000 fffff880`053fa000 dxgkrnl dxgkrnl.sys Fri Oct 02 03:00:14 2009 (4AC5509E)
fffff880`05800000 fffff880`0585a000 usbhub usbhub.sys Tue Jul 14 02:07:09 2009 (4A5BCC2D)
fffff880`0585a000 fffff880`0586f000 NDProxy NDProxy.SYS Tue Jul 14 02:10:05 2009 (4A5BCCDD)
fffff880`0586f000 fffff880`058cb000 HdAudio HdAudio.sys Tue Jul 14 02:06:59 2009 (4A5BCC23)
fffff880`058d8000 fffff880`05907000 ndiswan ndiswan.sys Tue Jul 14 02:10:11 2009 (4A5BCCE3)
fffff880`05907000 fffff880`05922000 raspppoe raspppoe.sys Tue Jul 14 02:10:17 2009 (4A5BCCE9)
fffff880`05922000 fffff880`05943000 raspptp raspptp.sys Tue Jul 14 02:10:18 2009 (4A5BCCEA)
fffff880`05943000 fffff880`0595d000 rassstp rassstp.sys Tue Jul 14 02:10:25 2009 (4A5BCCF1)
fffff880`0595d000 fffff880`05968000 rdpbus rdpbus.sys Tue Jul 14 02:17:46 2009 (4A5BCEAA)
fffff880`05968000 fffff880`05977000 mouclass mouclass.sys Tue Jul 14 01:19:50 2009 (4A5BC116)
fffff880`05977000 fffff880`05978480 swenum swenum.sys Tue Jul 14 02:00:18 2009 (4A5BCA92)
fffff880`05979000 fffff880`059bc000 ks ks.sys Tue Jul 14 02:00:31 2009 (4A5BCA9F)
fffff880`059bc000 fffff880`059ce000 umbus umbus.sys Tue Jul 14 02:06:56 2009 (4A5BCC20)
fffff880`06c00000 fffff880`06c3d000 portcls portcls.sys Tue Jul 14 02:06:27 2009 (4A5BCC03)
fffff880`06c3d000 fffff880`06c5f000 drmk drmk.sys Tue Jul 14 03:01:25 2009 (4A5BD8E5)
fffff880`06c5f000 fffff880`06c64200 ksthunk ksthunk.sys Tue Jul 14 02:00:19 2009 (4A5BCA93)
fffff880`06c65000 fffff880`06c71000 Dxapi Dxapi.sys Tue Jul 14 01:38:28 2009 (4A5BC574)
fffff880`06c71000 fffff880`06c7f000 crashdmp crashdmp.sys Tue Jul 14 02:01:01 2009 (4A5BCABD)
fffff880`06c7f000 fffff880`06d9d000 dump_iaStorV dump_iaStorV.sys Wed Apr 08 18:57:17 2009 (49DCD76D)
fffff880`06d9d000 fffff880`06db8000 USBSTOR USBSTOR.SYS Tue Jul 14 02:06:34 2009 (4A5BCC0A)
fffff880`06db8000 fffff880`06db9f00 USBD USBD.SYS Tue Jul 14 02:06:23 2009 (4A5BCBFF)
fffff880`06dba000 fffff880`06dcd000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 01:21:51 2009 (4A5BC18F)
fffff960`00020000 fffff960`0032f000 win32k win32k.sys unavailable (00000000)
Unloaded modules:
fffff880`01480000 fffff880`0148e000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fffff880`02c27000 fffff880`02d45000 dump_iaStorV
Timestamp: unavailable (00000000)
Checksum: 00000000
fffff880`02d45000 fffff880`02d58000 dump_dumpfve
Timestamp: unavailable (00000000)
Checksum: 00000000
ASKER
Thank you for the responses. I have reinstalled the driver's. I'm going to run some stress test and give it a day or two of reboots and see where i'm at.
Thanks everyone.
- Mike
Thanks everyone.
- Mike
Hi there;
It seems a video card issue:
So, no conflicting devices in devices manager? Maybe a CAM driver?
Apart from drivers:
Sure your graphics card is not overheating?
Display Props>settings>advanced>nv idia>temps
(If you may not have integrated thermal sutff in your settings, download Everest or SisoftSandra)
50 to 60degreeCelcius is optimum, above than those values could be an issue.
Also, when does it occur more frequent? While playing some game?
It could be a directX issue too. If above driver update fails, you may reinstall directX.
Best regards.
It seems a video card issue:
So, no conflicting devices in devices manager? Maybe a CAM driver?
Apart from drivers:
Sure your graphics card is not overheating?
Display Props>settings>advanced>nv
(If you may not have integrated thermal sutff in your settings, download Everest or SisoftSandra)
50 to 60degreeCelcius is optimum, above than those values could be an issue.
Also, when does it occur more frequent? While playing some game?
It could be a directX issue too. If above driver update fails, you may reinstall directX.
Best regards.
ASKER
No conflicting drivers or devices. Don't think its a DirectX issue. it occurs more frequent when i don't boot it for a few days. doesn't seem to create a pattern with games. (which i don't really play much of).
Temperatures:
Motherboard 32 °C (90 °F)
CPU 29 °C (84 °F)
CPU #1 / Core #1 42 °C (108 °F)
CPU #1 / Core #2 42 °C (108 °F)
CPU #1 / Core #3 40 °C (104 °F)
CPU #1 / Core #4 40 °C (104 °F)
North Bridge 29 °C (84 °F)
VRM 45 °C (113 °F)
GPU1: GPU 56 °C (133 °F)
GPU1: GPU Memory 48 °C (118 °F)
GPU1: GPU Ambient 48 °C (118 °F)
GPU2: GPU 48 °C (118 °F)
GPU2: GPU Memory 40 °C (104 °F)
GPU2: GPU Ambient 42 °C (108 °F)
Temperatures:
Motherboard 32 °C (90 °F)
CPU 29 °C (84 °F)
CPU #1 / Core #1 42 °C (108 °F)
CPU #1 / Core #2 42 °C (108 °F)
CPU #1 / Core #3 40 °C (104 °F)
CPU #1 / Core #4 40 °C (104 °F)
North Bridge 29 °C (84 °F)
VRM 45 °C (113 °F)
GPU1: GPU 56 °C (133 °F)
GPU1: GPU Memory 48 °C (118 °F)
GPU1: GPU Ambient 48 °C (118 °F)
GPU2: GPU 48 °C (118 °F)
GPU2: GPU Memory 40 °C (104 °F)
GPU2: GPU Ambient 42 °C (108 °F)
The temp seems pretty normal to me. Are there any CAM driver installed?
ASKER
Only the logmein driver. No cam.
ok...may sound cheesy but if you re-uninstalled and re-reinstalled the driver, but this time before uninstalling it, write down the driver names, uninstall the driver, then check for the files you have written, delete them manually (if-any), then reboot the system and then reinstall the driver.
Also please write dxdiag to your search bar and check for notes part.
Another thing, could you run sisoft sandra or everest tests on your card?
Finally, I can say, please do a system restore (if you have any) prior of this problem.
Best regards.
Also please write dxdiag to your search bar and check for notes part.
Another thing, could you run sisoft sandra or everest tests on your card?
Finally, I can say, please do a system restore (if you have any) prior of this problem.
Best regards.
All 3 dumps do have a bugcheck = 0xd1 and name NVIDIA as the probable cause. However. . .
Update your LogMeIn software installation - it is from April 2007 and I believe that NVIDIA may be getting the probable cause blame when the system is transitioning from user mode into kernel code territory and interacting with the LogMeIn kernel mode drivers. I have seen many BSODs caused by older LogMeIn program installation under both Vista SP2 & now Windows 7.
https://secure.logmeinresc ue.com/US/ HelpDesk/S upport.asp x
Regards. . .
jcgriff2
Update your LogMeIn software installation - it is from April 2007 and I believe that NVIDIA may be getting the probable cause blame when the system is transitioning from user mode into kernel code territory and interacting with the LogMeIn kernel mode drivers. I have seen many BSODs caused by older LogMeIn program installation under both Vista SP2 & now Windows 7.
https://secure.logmeinresc
Regards. . .
jcgriff2
Apologies - I mesnt to include this in last post - the LogMeIn driver -
0: kd> lmvm lmimirr
start end module name
fffff880`02c1e000 fffff880`02c25000 lmimirr (deferred)
Image path: \SystemRoot\system32\DRIVE RS\lmimirr .sys
Image name: lmimirr.sys
Timestamp: Tue Apr 10 18:32:45 2007 (461C108D)
CheckSum: 0000A04C
ImageSize: 00007000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm lmimirr
start end module name
fffff880`02c1e000 fffff880`02c25000 lmimirr (deferred)
Image path: \SystemRoot\system32\DRIVE
Image name: lmimirr.sys
Timestamp: Tue Apr 10 18:32:45 2007 (461C108D)
CheckSum: 0000A04C
ImageSize: 00007000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
ASKER
That's interesting considering the computer was built within the last 2 months. I will upgrade the driver and post results. But none the less, interesting.
I was suspecting from a CAM driver, yet it could be a driver of LogMeIn.
Also, if you are using virtualization softwares, try to disable their network adapter.
Best regards.
Also, if you are using virtualization softwares, try to disable their network adapter.
Best regards.
ASKER
So far the newest version of the NVIDIA driver has shown hope. I also updated the Logmein Driver. Ill give it a day or so more to see where it sits and then accept a solution.
Thank you everyone, ill keep you updated.
- Mike
Thank you everyone, ill keep you updated.
- Mike
ASKER
Ok, so its been a couple days now. The blue screen came back.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: d1
BCP1: FFFFF88011C00000
BCP2: 000000000000000E
BCP3: 0000000000000000
BCP4: FFFFF880100306DE
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\010510 -15328-01. dmp
C:\Users\Mike\AppData\Loca l\Temp\WER -27187-0.s ysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\ erofflps.t xt
010510-15328-01.dmp
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: d1
BCP1: FFFFF88011C00000
BCP2: 000000000000000E
BCP3: 0000000000000000
BCP4: FFFFF880100306DE
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\010510
C:\Users\Mike\AppData\Loca
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\
010510-15328-01.dmp
It still is the nvlddmkm.sys, like before.
Asking Google you will get a host of hits all referring to this driver and BSODs or similar disturbances, and you also find an infinite amount of users claiming to have solved the problem. But this is mostly concerned with Vista and 8800GT.
Maybe we should start considering a defective graphics card?
Asking Google you will get a host of hits all referring to this driver and BSODs or similar disturbances, and you also find an infinite amount of users claiming to have solved the problem. But this is mostly concerned with Vista and 8800GT.
Maybe we should start considering a defective graphics card?
ASKER
Both graphics cards are new GTX 260's. One was defective from the manufacture. I sent it in a got one with a new serial already. I would be slightly disturbed if i had two defective cards in a row. But it could be worth considering.
ASKER
Any other ideas? Steps I should consider following before I call the manufacture to have them test the cards?
a. Maybe try underclocking your video cards for a while. I don't know what tool to recommend, maybe eVGA Precision: http://www.evga.com/precision/
b. Try this registry tweak I found on the AMD forums (it was originally used for getting rid of Vista BSOD's, but should be expected to also work for Win7 - if it actually addresses the issue:
1) open your vista registry editor
2) go to the key : HKLM\System\CurrentControl Set\Contro l\Graphics Drivers\
3) highlight it then right click on this key
4) Add DWORD TdrDelay
5) Set value of TdrDelay to the number of seconds you allow your GPU to run with no feedback to the system (ie Timeout watchdog..)
personally I've set this value to 8 seconds (from the default 2s) so that it leaves plenty of time to the GPU to perform overcomplicated computing intensive kernel without having Vista considering a fault and hence "recovering the device"
(source: http://forums.amd.com/devforum/messageview.cfm?FTVAR_FORUMVIEWTMP=Threaded&catid=328&threadid=100142)
b. Try this registry tweak I found on the AMD forums (it was originally used for getting rid of Vista BSOD's, but should be expected to also work for Win7 - if it actually addresses the issue:
1) open your vista registry editor
2) go to the key : HKLM\System\CurrentControl
3) highlight it then right click on this key
4) Add DWORD TdrDelay
5) Set value of TdrDelay to the number of seconds you allow your GPU to run with no feedback to the system (ie Timeout watchdog..)
personally I've set this value to 8 seconds (from the default 2s) so that it leaves plenty of time to the GPU to perform overcomplicated computing intensive kernel without having Vista considering a fault and hence "recovering the device"
(source: http://forums.amd.com/devforum/messageview.cfm?FTVAR_FORUMVIEWTMP=Threaded&catid=328&threadid=100142)
ok, that may sound cheesy, but what about a format of 7 and reinstalling it?
Best regads.
Best regads.
ASKER
Lol, sorry I didnt respond quicker. I came down with the flu. Underclocking did nothing. As for a format and reinstall. I'm not really in a situation where that is an easy option. =( I would really hate to resort to that and have this problem continue. I have found a consistency though. Temperature. When the computer is cold (first boot of the day) it will blue screen. after it gets a minute under its belt. It boots perfectly.
Did you try the registry tweak I posted above?
Also, your recent discovery about the cold computer makes me remind something:
It could be an issue with the motherboard. My mb, for instance, will let the computer freeze on first boot after it has been disconnected completely from electric power for a while. It seems to be known for this kind of behaviour. Since I usually only power down, but don't switch off the plugs, I don't particularly care.
Also, your recent discovery about the cold computer makes me remind something:
It could be an issue with the motherboard. My mb, for instance, will let the computer freeze on first boot after it has been disconnected completely from electric power for a while. It seems to be known for this kind of behaviour. Since I usually only power down, but don't switch off the plugs, I don't particularly care.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Could you send us those dmp files or could you view those files with the http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
or you can follow the steps to view it.
http://support.microsoft.com/kb/315263
after viewing it, could you post the result here, so experts can work on that.
Best regards.