[Demjuicies]

Hello, I've tried to go into as much detail as I can below. I'm not sure on some specs and the age of my system, sorry.

BSOD 1: A few months ago I started getting a BSOD everytime I tried to connect an external monitor to my laptop, I don't know what the actual error message was as I stopped using an external monitor and completely forgot about it until this forum reminded me. I do recall it started happening after installing some windows updates. Sorry I can't be anymore detailed than that.

BSOD 2: Recently I started getting multiple BUGCODE_USB_DRIVER BSOD's whilst cleaning my laptop for malware etc. I don't know if it was a coincidence that they started happening at that time, but I never had them prior to running any of the scans in the Virus/Trojan/Spyware forum. I have finished cleaning up the malware now (thanks to the help of the other forum) and there doesn't appear to be any remaining malware left on my laptop.

My built in webcam kept crashing not too long ago (it's been on the blink for a while but i've never really used it) I disabled it, but I've bluescreened since with the same error. It's listed as a USB device, so I wonder if that could have something to do with it.

BSOD 3: DRIVER IRQL.. (I didn't catch the rest) it only happened once at the same time I started getting the bugcode BSODs, I haven't had one since.

· OS - Vista/ Windows 7 ?
- Windows 7
· x86 (32-bit) or x64 ?
-x64
· What was original installed OS on system?
-Windows 7
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
-came pre-installed on system
· Age of system (hardware)
-Not sure
· Age of OS installation - have you re-installed the OS?
-Not sure again
-Haven't re-installed the OS
· CPU
Intel(R) Core(TM) i3 CPU M350 @2.27 GHz
· Video Card
· MotherBoard
· Power Supply - brand & wattage
-Not sure on any of these 3
· System Manufacturer
-ASUS
· Exact model number (if laptop, check label on bottom)
-K52F-SX065V

 

[makinu1der2]

Hello,


Try checking the ASUS Support site for an update for the Elantech touchpad.

Try with an external mouse connected disabling the touchpad to see if you still get the BSOD's

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`02c4a000 PsLoadedModuleList = 0xfffff800`02e8e670
Debug session time: Sun Apr  7 13:46:38.881 2013 (UTC - 4:00)
System Uptime: 0 days 0:56:00.267
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa8605f27260, 2, 0, fffff88004c2cbc5}

*** WARNING: Unable to verify timestamp for ETD.sys
*** ERROR: Module load completed but symbols could not be loaded for ETD.sys
Probably caused by : ETD.sys ( ETD+ebc5 )

Followup: MachineOwner
---------

2: 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: fffffa8605f27260, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004c2cbc5, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef8100
GetUlongFromAddress: unable to read from fffff80002ef81c0
 fffffa8605f27260 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
ETD+ebc5
fffff880`04c2cbc5 408ab44bec000000 mov     sil,byte ptr [rbx+rcx*2+0ECh]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f8b980 -- (.trap 0xfffff88002f8b980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=00000002fffffffa
rdx=fffffa8006aa3010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004c2cbc5 rsp=fffff88002f8bb10 rbp=fffffa8006aa3010
 r8=00000000fffffffe  r9=fffff88002f8bcd8 r10=0000000000000000
r11=fffffa8005e46dc0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
ETD+0xebc5:
fffff880`04c2cbc5 408ab44bec000000 mov     sil,byte ptr [rbx+rcx*2+0ECh] ds:00000006`000000e0=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cbf1e9 to fffff80002cbfc40

STACK_TEXT:  
fffff880`02f8b838 fffff800`02cbf1e9 : 00000000`0000000a fffffa86`05f27260 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f8b840 fffff800`02cbde60 : fffffa80`05ea2270 fffff880`04c0c360 00000000`0000001a fffffa80`05f27180 : nt!KiBugCheckDispatch+0x69
fffff880`02f8b980 fffff880`04c2cbc5 : fffffa80`05ea2270 fffff880`04c0c468 00000000`00000054 fffff880`04c013a4 : nt!KiPageFault+0x260
fffff880`02f8bb10 fffffa80`05ea2270 : fffff880`04c0c468 00000000`00000054 fffff880`04c013a4 00000000`00000053 : ETD+0xebc5
fffff880`02f8bb18 fffff880`04c0c468 : 00000000`00000054 fffff880`04c013a4 00000000`00000053 fffff880`04c0116f : 0xfffffa80`05ea2270
fffff880`02f8bb20 00000000`00000054 : fffff880`04c013a4 00000000`00000053 fffff880`04c0116f 00000000`00000008 : i8042prt!ntoskrnl_NULL_THUNK_DATA+0x908
fffff880`02f8bb28 fffff880`04c013a4 : 00000000`00000053 fffff880`04c0116f 00000000`00000008 fffff880`02f8bba0 : 0x54
fffff880`02f8bb30 fffff880`02f8bbd0 : fffffa80`05eb1b40 00000000`00000008 fffff880`02f67f40 00000000`00000001 : i8042prt!WPP_RECORDER_SF_+0x94
fffff880`02f8bb70 fffffa80`05eb1b40 : 00000000`00000008 fffff880`02f67f40 00000000`00000001 00000000`00000000 : 0xfffff880`02f8bbd0
fffff880`02f8bb78 00000000`00000008 : fffff880`02f67f40 00000000`00000001 00000000`00000000 fffffa80`06aa3028 : 0xfffffa80`05eb1b40
fffff880`02f8bb80 fffff880`02f67f40 : 00000000`00000001 00000000`00000000 fffffa80`06aa3028 fffffa80`05f27180 : 0x8
fffff880`02f8bb88 00000000`00000001 : 00000000`00000000 fffffa80`06aa3028 fffffa80`05f27180 fffffa80`05f27030 : 0xfffff880`02f67f40
fffff880`02f8bb90 00000000`00000000 : fffffa80`06aa3028 fffffa80`05f27180 fffffa80`05f27030 fffff880`02f8bcd8 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ETD+ebc5
fffff880`04c2cbc5 408ab44bec000000 mov     sil,byte ptr [rbx+rcx*2+0ECh]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  ETD+ebc5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ETD

IMAGE_NAME:  ETD.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ad6ea06

FAILURE_BUCKET_ID:  X64_0xD1_ETD+ebc5

BUCKET_ID:  X64_0xD1_ETD+ebc5

Followup: MachineOwner

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02e45670
Debug session time: Thu Apr 11 00:43:04.857 2013 (UTC - 4:00)
System Uptime: 0 days 1:14:21.309
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {8, 6, 5, fffffa8004eacb20}

Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent
Arg4: fffffa8004eacb20, TimeoutContext - PortData

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88005f23a60 to fffff80002c77c00

STACK_TEXT:  
fffff880`033cbc18 fffff880`05f23a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`033cbc20 fffff800`02f6fd73 : fffffa80`04e9f050 00000000`00000001 ffffffff`dc3a58a0 fffff800`02e1d2d8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`033cbc80 fffff800`02c81251 : fffff800`02e1d200 fffff800`02f6fd01 fffffa80`03b66600 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`033cbcb0 fffff800`02f15ede : 00000000`00000001 fffffa80`03b66660 00000000`00000080 fffffa80`03b4f450 : nt!ExpWorkerThread+0x111
fffff880`033cbd40 fffff800`02c68906 : fffff880`031d3180 fffffa80`03b66660 fffff880`031ddfc0 00000000`00000090 : nt!PspSystemThreadStartup+0x5a
fffff880`033cbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`05f23a60 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  usbhub!UsbhHubProcessChangeWorker+ec

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbhub

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c15

FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

Followup: MachineOwner

 

[Demjuicies]

I've had my touchpad disabled since your last post and haven't had a bluescreen since. I've just got around to installing new touchpad drivers, they were about 6years out of date! So far so good, but I can't be sure until a couple of days pass without a blue screen..

 

[makinu1der2]

Continue to use the PC as you normally would for a few days to be sure the BSOD's are gone. If any arise please post back in this thread.

 

[Demjuicies]

Looks like updating the mousepad drivers did the job!

I still have a problem connecting an external monitor to my laptop, I get a SYSTEM_SERVICE_EXCEPTION blue screen upon connecting it.

 

[makinu1der2]

Glad to hear the good news about the Touchpad.

Can you upload the new dumps you received when connecting the monitor?

Are you connecting to the VGA or HDMI port?

 

[Demjuicies]

Sorry for the slow response, I got caught up in some stuff.

It's the VGA port, it instantly bluescreens.

I think the attached is what you're asking for, I got it from windows > minidump on the date it happened.

 

[makinu1der2]

Try updating the graphics driver (VGA) from the ASUS site.

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e44670
Debug session time: Thu Apr 18 12:41:49.212 2013 (UTC - 4:00)
System Uptime: 2 days 0:36:41.519
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000094, fffff88004a40de8, fffff880098a5650, 0}

Probably caused by : igdkmd64.sys ( igdkmd64+9de8 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000094, Exception code that caused the bugcheck
Arg2: fffff88004a40de8, Address of the instruction which caused the bugcheck
Arg3: fffff880098a5650, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: 
igdkmd64+9de8
fffff880`04a40de8 f7f1            div     eax,ecx

CONTEXT:  fffff880098a5650 -- (.cxr 0xfffff880098a5650)
rax=0000000000096000 rbx=fffff8a00d088000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000001
rip=fffff88004a40de8 rsp=fffff880098a6030 rbp=fffffa8005f4b000
 r8=0000000000000015  r9=fffff88004a37000 r10=fffff8a005655000
r11=0000000000000015 r12=fffff8a00d088000 r13=fffff880098a6180
r14=fffff880098a6450 r15=0000000000000001
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
igdkmd64+0x9de8:
fffff880`04a40de8 f7f1            div     eax,ecx
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88004a40de8

STACK_TEXT:  
fffff880`098a6030 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : igdkmd64+0x9de8


FOLLOWUP_IP: 
igdkmd64+9de8
fffff880`04a40de8 f7f1            div     eax,ecx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  igdkmd64+9de8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f0cbb79

STACK_COMMAND:  .cxr 0xfffff880098a5650 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_igdkmd64+9de8

BUCKET_ID:  X64_0x3B_igdkmd64+9de8

Followup: MachineOwner

 

[Demjuicies]

Awesome, that cleared it up!

Just as I thought it was over, I got another BUGCODE_USB_DRIVER bluescreen shortly after restarting my laptop.. I noticed a few dumps in the folder when I was getting you the dump for my monitor bsod, but I don't recall bluescreening so I guess I was AFK when they happened or something..

I've attached the last dump I got before installing new touchpad drivers, then the new dumps I got 10-14 days later.. I haven't had anything inbetween those dates (besides the monitor bsod)

 

[makinu1der2]

Check the ASUS site for an updated Chipet driver.

 

[Demjuicies]

Updated the chipset driver but I've bluescreened since.