New
#1
BSOD windows 7 64 bit
These are happening randomly. I've gotten 3 in 2 hours now. EVerything was fine yesterday. DMP file is attatched
BSOD windows 7 64 bit
-
-
New #2
Several problems
1-sptd.sys used in daemon tools and alcohol. A huge cause of BDOS's
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview
2- AVG sometimes causes bsod's as well remove and replace with Microsoft security essentials.
AVG - Download tools
http://www.microsoft.com/security_essentials/
3-Your video driver caused this crash.
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\022311-33119-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e4ae50 Debug session time: Wed Feb 23 17:41:55.805 2011 (GMT-5) System Uptime: 0 days 0:43:47.319 Loading Kernel Symbols ............................................................... ................................................................ ................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {ff8d9, b, 1, fffff880048b29e8} 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+a79e8 ) 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: 00000000000ff8d9, memory referenced Arg2: 000000000000000b, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff880048b29e8, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb50e0 00000000000ff8d9 CURRENT_IRQL: b FAULTING_IP: nvlddmkm+a79e8 fffff880`048b29e8 4881c1f00f0000 add rcx,0FF0h CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff80000b9bf90 -- (.trap 0xfffff80000b9bf90) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff880037de818 rbx=0000000000000000 rcx=0000000000000818 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880048b29e8 rsp=fffff80000b9c120 rbp=fffffa8005c79890 r8=00000000037de824 r9=0000000000001e00 r10=fffff88004f711d0 r11=fffff80000b9c358 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac po cy nvlddmkm+0xa79e8: fffff880`048b29e8 4881c1f00f0000 add rcx,0FF0h Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002c7e469 to fffff80002c7ef00 STACK_TEXT: fffff800`00b9be48 fffff800`02c7e469 : 00000000`0000000a 00000000`000ff8d9 00000000`0000000b 00000000`00000001 : nt!KeBugCheckEx fffff800`00b9be50 fffff800`02c7d0e0 : 00000000`00000004 fffffa80`06119be0 fffff880`0196e9a0 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff800`00b9bf90 fffff880`048b29e8 : fffffa80`03c89030 fffff800`00b9c138 fffffa80`05c79890 00000000`00000000 : nt!KiPageFault+0x260 fffff800`00b9c120 fffffa80`03c89030 : fffff800`00b9c138 fffffa80`05c79890 00000000`00000000 00000000`00000000 : nvlddmkm+0xa79e8 fffff800`00b9c128 fffff800`00b9c138 : fffffa80`05c79890 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`03c89030 fffff800`00b9c130 fffffa80`05c79890 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`00b9c138 fffff800`00b9c138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`05c79890 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+a79e8 fffff880`048b29e8 4881c1f00f0000 add rcx,0FF0h SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nvlddmkm+a79e8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c8b048a FAILURE_BUCKET_ID: X64_0xD1_nvlddmkm+a79e8 BUCKET_ID: X64_0xD1_nvlddmkm+a79e8 Followup: MachineOwner ---------
Quote
Related Discussions