New
#1
BSOD on sleep mode
I'm receiving a BSOD whenever I use the sleep function on my laptop.
Attached is the SF file. Please help!
I'm receiving a BSOD whenever I use the sleep function on my laptop.
Attached is the SF file. Please help!
Welcome to Seven Forums.
Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.
Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.
Your BSOD was caused by Killer Wireless-N 1100 Series LAN device driver Driver Reference Table
Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program:
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa8006cbe860, fffff800047e83d8, fffffa800cd89c60} Probably caused by : pci.sys Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time (usually 10 minutes). Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: fffffa8006cbe860, Physical Device Object of the stack Arg3: fffff800047e83d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack Arg4: fffffa800cd89c60, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: pci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f MODULE_NAME: pci FAULTING_MODULE: fffff88000f98000 pci CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 TAG_NOT_DEFINED_c000000f: FFFFF800047EEFB0 STACK_TEXT: fffff800`047e8388 fffff800`02f37992 : 00000000`0000009f 00000000`00000003 fffffa80`06cbe860 fffff800`047e83d8 : nt!KeBugCheckEx fffff800`047e8390 fffff800`02ed294c : fffff800`047e84c0 fffff800`047e84c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0 fffff800`047e8430 fffff800`02ed27e6 : fffff800`03078f20 00000000`0010d4bd 00000000`00000000 fffff880`0869e743 : nt!KiProcessTimerDpcTable+0x6c fffff800`047e84a0 fffff800`02ed26ce : 00000028`10778e32 fffff800`047e8b18 00000000`0010d4bd fffff800`03047a28 : nt!KiProcessExpiredTimerList+0xc6 fffff800`047e8af0 fffff800`02ed24b7 : 00000008`fa889dc1 00000008`0010d4bd 00000008`fa889dfa 00000000`000000bd : nt!KiTimerExpiration+0x1be fffff800`047e8b90 fffff800`02ebf94a : fffff800`03043e80 fffff800`03051cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277 fffff800`047e8c40 00000000`00000000 : fffff800`047e9000 fffff800`047e3000 fffff800`047e8c00 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_3_Ak27x64_IMAGE_pci.sys BUCKET_ID: X64_0x9F_3_Ak27x64_IMAGE_pci.sys Followup: MachineOwner --------- 0: kd> !irp fffffa800cd89c60 Irp is active with 5 stacks 3 is current (= 0xfffffa800cd89dc0) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. cmd flg cl Device File Completion-Context [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 >[ 16, 2] 0 0 fffffa8009b0b050 00000000 00000000-00000000 Unable to load image \SystemRoot\system32\DRIVERS\Ak27x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Ak27x64.sys *** ERROR: Module load completed but symbols could not be loaded for Ak27x64.sys \Driver\Ak27x64 Args: 00014400 00000001 00000004 00000002 [ 16, 2] 0 e1 fffffa8009ad7040 00000000 00000000-00000000 pending \Driver\vwifibus Args: 00014400 00000001 00000004 00000002 [ 0, 0] 0 0 00000000 00000000 00000000-fffffa800ba3e9a0 Args: 00000000 00000000 00000000 00000000 0: kd> lmvm Ak27x64 start end module name fffff880`07a04000 fffff880`07d61000 Ak27x64 T (no symbols) Loaded symbol image file: Ak27x64.sys Image path: \SystemRoot\system32\DRIVERS\Ak27x64.sys Image name: Ak27x64.sys Timestamp: Tue Jul 10 02:41:13 2012 (4FFB41E9) CheckSum: 0033FBA4 ImageSize: 0035D000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4