Laptop BSOD and unannounced restart, USB_driver

VinceL · 05 Jan 2011

Hi,

I've just bought a new Dell Laptop, and have had a string of BSOD and restarts over the two months since I've got it.

Dell Studio 1747 (BIOS A13 up-to-date)
Windows 7 Home Premium 64-bit (build 7600)
Intel Core i7 CPU Q840 @ 1.87GHz
8 GB memory (2 x 4 GB)

The first sign of error was just a few days after I got the laptop, it gave me some mouse driver conflict(I bought a wireless mouse for it) and wanted me to uninstall the synaptics driver for the touchpad, I did(stupidly), then I realised what it was, went back, uninstalled the mouse driver, reinstalled the synaptics driver from dell, then reinstalled the mouse driver and have left it like that since.
The original service techie I talked to when I first saw the driver uninstall prompt and my own ideas were simply that the wireless mouse probably wasn't 100% compatible with the win7 OS or with the laptop (it is a Microsoft intelllipoint mouse), so I ignored some of the earlier BSODs however with the continous string of BSODs and sudden unexplained restarts I'm not so sure anymore, how can I go about fixing this problem?

Attached are the BSOD_jcgriff2 and diagnostic report.
Thanks to anyone in advance.

VinceL · 05 Jan 2011

Just to add:

From what I have read up/googled myself and the diagnostic report I can see that it is a USB driver related problem, I'm just not sure if it would be solved as simply as buying a new /better mouse(which is what I orignally thought) or is it hardware related with the USB controller...

TonyTiger2004 · 05 Jan 2011

Hello VinceL, Welcome to Sevenforums!

While im looking over your files run Verifier, obviously this is some driver issue from what i have noticed thus far.
Driver Verifier - Enable and Disable

Once you run that if it is a driver issue as i suspect it will BSOD remember what it says when it BSOD upload new dump file it creates.

- Tony

VinceL · 06 Jan 2011

Thanks, I'll do that.
I just went out, came back, turned it on and I got a blue screen right after power on.

Wdf01000.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
STOP: 0x1000007e....

I've attached this new mini dump

I created the restore point, but I think I'll go do a backup too, the previous backup disks I had got damaged and I never got around to doing another one.
I'll come back tomorrow after I got everything backed up, just in case.

yowanvista · 06 Jan 2011

VinceL said:

Thanks, I'll do that.
I just went out, came back, turned it on and I got a blue screen right after power on.

Wdf01000.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
STOP: 0x1000007e....

I've attached this new mini dump

I created the restore point, but I think I'll go do a backup too, the previous backup disks I had got damaged and I never got around to doing another one.
I'll come back tomorrow after I got everything backed up, just in case.

This was caused by Synaptics Touch pad device driver
Uninstall the current driver then download a fresh copy
Drivers | Synaptics

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff88000e5c704, fffff88003385708, fffff88003384f70}

Unable to load image \SystemRoot\system32\DRIVERS\SynTP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
Probably caused by : SynTP.sys ( SynTP+dfe0 )

VinceL · 10 Jan 2011

Ok, I un-installed the Synaptics driver, re-installed an older version of the driver from the dell support site, and gave it several days to see if any problems would occur. So far it's being 3 days and no blue screens yet, but had an sudden restart this morning, so immediately ran driver verifier, and everything started up fine, no system halts etc.

The perfmon system diagnostic still reports 1 fail count in plug and play device configured(out of 215), so something is still failing, can I assume it is something else or is it too early to say and I should just wait and see...

VinceL · 11 Jan 2011

Fingers crossed, today I got this while shutting down:

DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe

STOP: 0x0000009f

mini-dump attached.