Hi,
I just bough a laptop Acer aspire for 2 days and the BSOD is starting to appear when I hibernate my laptop. I wonder whether the problem is according to my used or the store where I bought this.
I try to use the debug analysis to analyze my problem and it said that the problem probably cause by ntoskrnl.exe.
I upload my mini dump file here so could any body help me analyze my situation and give me the solution please.
Looking forward for your replying.
Thank you!!
Several Problems
1-sptd.sys. Used in Daemon tools and Alcohol, it is a huge cause of BSOD'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-Macaffee. Remove and replace with Microsoft Security Essentials
How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)
http://www.microsoft.com/security_essentials/
3-nvstusb.sys (Nvidia 3d driver) caused the most recent crash. It should be re-installed with the most recent driver using the below instructions.
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\022611-32791-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba2730?
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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0301a000 PsLoadedModuleList = 0xfffff800`03257e50
Debug session time: Sat Feb 26 16:08:25.451 2011 (GMT-5)
System Uptime: 0 days 3:18:06.996
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8008f4b060, fffff80000ba2748, fffffa80052948c0}
*** WARNING: Unable to verify timestamp for nvstusb.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstusb.sys
Probably caused by : nvstusb.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8008f4b060, Physical Device Object of the stack
Arg3: fffff80000ba2748, Functional Device Object of the stack
Arg4: fffffa80052948c0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa80052948c0
DEVICE_OBJECT: fffffa8008f7baf0
DRIVER_OBJECT: fffffa8008f474f0
IMAGE_NAME: nvstusb.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c7efa6d
MODULE_NAME: nvstusb
FAULTING_MODULE: fffff88008fe5000 nvstusb
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: mcshield.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800030f9273 to fffff8000308a740
STACK_TEXT:
fffff800`00ba26f8 fffff800`030f9273 : 00000000`0000009f 00000000`00000003 fffffa80`08f4b060 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`0309629e : fffff800`00ba2830 fffff800`00ba2830 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00ba27a0 fffff800`03095dd6 : fffffa80`09a39778 fffffa80`09a39778 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00ba2810 fffff800`030964be : 0000001b`ad33c564 fffff800`00ba2e88 00000000`000ba07e fffff800`03208248 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`03095cb7 : fffffa80`07815dc3 fffffa80`000ba07e 00000000`00000000 00000000`0000007e : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`03090865 : 00000000`00000000 fffffa80`0779c270 00000000`00000000 fffffa80`075f80f0 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`0309067c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`091a1be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_IMAGE_nvstusb.sys
BUCKET_ID: X64_0x9F_IMAGE_nvstusb.sys
Followup: MachineOwner
---------
Quote