New
#1
BSOD after small oc
S! I've got a bsod after a 10% oc, even if temperatures were quiet low. Any suggestion?
Thanks.
S! I've got a bsod after a 10% oc, even if temperatures were quiet low. Any suggestion?
Thanks.
This one was caused by your Atheros network driver. Not much more info because the DMP is corrupt from an invalid process attach from the OC.
Also you have SPTD.SYS running. It is used by daemon tools and alcohol and is a huge cause of BSOD's remove and replace.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\041611-17924-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0x82e50000 PsLoadedModuleList = 0x82f9a850 Debug session time: Sat Apr 16 10:34:03.493 2011 (GMT-4) System Uptime: 0 days 0:16:44.960 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ...... 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INVALID_PROCESS_ATTACH_ATTEMPT (5) Arguments: Arg1: 84e3ca50 Arg2: 85222030 Arg3: 00000000 Arg4: 00000001 Debugging Details: ------------------ Unable to load image \SystemRoot\system32\DRIVERS\l160x86.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for l160x86.sys *** ERROR: Module load completed but symbols could not be loaded for l160x86.sys CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x5 PROCESS_NAME: firefox.exe CURRENT_IRQL: 2 LOCK_ADDRESS: 82fb7fa0 -- (!locks 82fb7fa0) Resource @ nt!PiEngineLock (0x82fb7fa0) Available WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted. WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted. 1 total locks PNP_TRIAGE: Lock address : 0x82fb7fa0 Thread Count : 0 Thread address: 0x00000000 Thread wait : 0x0 LAST_CONTROL_TRANSFER: from 82eebdf0 to 82f2ef20 STACK_TEXT: 8078a9dc 82eebdf0 00000005 84e3ca50 85222030 nt!KeBugCheckEx+0x1e 8078aa08 83074ee9 84e3ca50 8078aa30 84fea938 nt!KeStackAttachProcess+0x3f 8078aa4c 830962ee 84e3ca50 89e01ca0 84fea938 nt!ObpDecrementHandleCount+0x125 8078aa94 8309602e 89e01ca0 a192b7e0 84e3ca50 nt!ObpCloseHandleTableEntry+0x203 8078aac4 830963c8 84e3ca50 00000000 8078ab68 nt!ObpCloseHandle+0x7f 8078aae0 82e8e1ea 800033f0 8078abf0 82e8bb4d nt!NtClose+0x4e 8078aae0 82e8bb4d 800033f0 8078abf0 82e8bb4d nt!KiFastCallEntry+0x12a 8078ab5c 8304a7db 800033f0 8078acec 00000058 nt!ZwClose+0x11 8078abf0 8304ac8a 85b9a6e8 00000001 83066eb0 nt!PiGetDeviceRegistryProperty+0xb2 8078ac84 8301f390 85b9a6e8 00000007 00000058 nt!IoGetDeviceProperty+0x2ae 8078adb0 8301f676 85b9a6e8 00000002 c2000000 nt!IopOpenOrCreateDeviceRegistryKey+0x15d 8078adc8 892b6552 85b9a6e8 00000002 c2000000 nt!IoOpenDeviceRegistryKey+0x18 8078adec 8924d56d 8078ae1c 8078ae54 8611e430 ndis!NdisOpenConfiguration+0x9d 8078ae24 91b6c165 8078ae48 8078ae54 86338fbe ndis!NdisOpenConfigurationEx+0x1a4 WARNING: Stack unwind information not available. Following frames may be wrong. 8078ae5c 91b6c5a8 863384b0 0030002e 91b70550 l160x86+0x6165 8078ae84 91b6c8e3 863384b0 00000004 863384b0 l160x86+0x65a8 8078ae9c 91b6ca82 863384b0 00000000 863387b4 l160x86+0x68e3 8078aeb8 91b6cc26 00100006 00000000 00000001 l160x86+0x6a82 8078aed8 91b679a9 863384b0 8078af20 8929089a l160x86+0x6c26 8078aee4 8929089a 863384b0 00000000 8078af10 l160x86+0x19a9 8078af20 8923ba0f 86356664 00356650 00000000 ndis!ndisMiniportDpc+0xe2 8078af48 82ec81b5 86356664 86356650 00000000 ndis!ndisInterruptDpc+0xaf 8078afa4 82ec8018 82f7bd20 84fea938 00000000 nt!KiExecuteAllDpcs+0xf9 8078aff4 82ec77dc a3047ce4 00000000 00000000 nt!KiRetireDpcList+0xd5 8078aff8 a3047ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c 82ec77dc 00000000 0000001a 00d6850f bb830000 0xa3047ce4 STACK_COMMAND: kb FOLLOWUP_IP: l160x86+6165 91b6c165 ?? ??? SYMBOL_STACK_INDEX: e SYMBOL_NAME: l160x86+6165 FOLLOWUP_NAME: MachineOwner MODULE_NAME: l160x86 IMAGE_NAME: l160x86.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a3b8f40 FAILURE_BUCKET_ID: 0x5_l160x86+6165 BUCKET_ID: 0x5_l160x86+6165 Followup: MachineOwner ---------
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 DuplexSecure - Downloads
when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.
AND LAST AVAST. Also a known cause of BSOD's
remove and replace with Microsoft Security Essentials.
http://files.avast.com/files/eng/aswclear5.exe
http://www.microsoft.com/security_essentials/