Blue screen crashes

uriel556

uriel556

Member
Hi,

My laptop has been crashing for past year on and off... however now it seems to be crashing on a daily basis when I am doing nothing but browsing the internet.

When it started I thought it was just over heating and got a cooling pad , that solved the problem for a few months, then it starting crashing again because "an attempt to reset the display driver failed", I lowered my resolution, turned off most of the graphics and updated the display driver.

Now it is crashing because of BUGCODE_USB_DRIVER and a file system error :confused:

I am a complete noob and have no idea what this means I would be grateful for any help


oh and here are the details of the crashes that I got from bluescreenview

thanks again for any help!!!! :)

==================================================
Dump File : Mini101110-01.dmp
Crash Time : 11/10/2010 11:20:43 AM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 0x001904aa
Parameter 2 : 0x8b1674d4
Parameter 3 : 0x8b1671d0
Parameter 4 : 0x8467f3c8
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+1a316
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini101110-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6001
==================================================

==================================================
Dump File : Mini100510-02.dmp
Crash Time : 05/10/2010 1:51:52 PM
Bug Check String : BUGCODE_USB_DRIVER
Bug Check Code : 0x000000fe
Parameter 1 : 0x00000008
Parameter 2 : 0x00000006
Parameter 3 : 0x00000001
Parameter 4 : 0x92662000
Caused By Driver : usbhub.sys
Caused By Address : usbhub.sys+13d9d
File Description : Default Hub Driver for USB
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini100510-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6001
==================================================

==================================================
Dump File : Mini100510-01.dmp
Crash Time : 05/10/2010 8:20:50 AM
Bug Check String : BUGCODE_USB_DRIVER
Bug Check Code : 0x000000fe
Parameter 1 : 0x00000008
Parameter 2 : 0x00000006
Parameter 3 : 0x00000001
Parameter 4 : 0x90936000
Caused By Driver : usbhub.sys
Caused By Address : usbhub.sys+13d9d
File Description : Default Hub Driver for USB
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini100510-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6001
==================================================

==================================================
Dump File : Mini100310-01.dmp
Crash Time : 03/10/2010 11:58:31 AM
Bug Check String :
Bug Check Code : 0x00000116
Parameter 1 : 0x89468510
Parameter 2 : 0x8e815f40
Parameter 3 : 0x00000000
Parameter 4 : 0x00000002
Caused By Driver : nvlddmkm.sys
Caused By Address : nvlddmkm.sys+df40
File Description : NVIDIA Windows Kernel Mode Driver, Version 258.96
Product Name : NVIDIA Windows Kernel Mode Driver, Version 258.96
Company : NVIDIA Corporation
File Version : 8.17.12.5896
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini100310-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6001
 
Last edited:

My Computer

System One

sorry about that

attached everything to this post

- x86 (32-bit) or x64 ?
32

- the original installed OS on the system?
Yes


- an OEM or full retail version?

OEM

- What is the age of system (hardware)?

3 years

- What is the age of OS installation (have you re-installed the OS?)

reformatted the hard drive about a year ago
 

My Computer

System One

perfmon suggests that there's a problem with your Cyberlink service. Please uninstall the program that it belongs to (most likely HP Quick Play).

systeminfo.txt shows that you don't have SP2 installed.
Please update your drivers from the PC Manufacturer's website (or the motherboard manufacturer's website if it's a custom build).
Scan for malware
Then visit Windows Update and get SP2 and all subsequent updates.

It's going to take a while for all 39 dump reports to run, so I'll post back when they're done.
From what I've seen so far, this is most likely a hardware problem.
Please run these free diagnostics as time permits:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
Click to expand...

Then, if the above tests pass, I'd try these free stress tests:
FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
Click to expand...
Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
Click to expand...
Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.
Click to expand...
Click to expand...

39 memory dumps since 11 Jan 2010
 

My Computer

System One

39 memory dumps since 11 Jan 2010
6 different BSOD error codes
5 different causes blamed

18 are video related
7 are storage related
10 are related to your BitDefender (oldest errors)

Please run the diagnostics from above and we'll see what they have to say.

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
Click to expand...
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: Driver Reference ).
Please pay particular attention to any dated 2008 or earlier:
Code: 
349557b9.sys   Thu   2-Nov   04:31:39   2006 - Unknown driver - [url]http://www.carrona.org/dvrref.html#349557b9.sys[/url]
ATSwpDrv.sys   Wed   28-Mar   16:44:15   2007 -  Slide Fingerprint USB Driver - AuthenTec, Inc. - [url]http://www.carrona.org/dvrref.html#ATSwpDrv.sys[/url]
cpqbttn.sys   Wed   28-Jun   11:54:39   2006 - HP Tablet PC Key Button HID Driver - HP Quick Launch Buttons - [url]http://www.carrona.org/dvrref.html#cpqbttn.sys[/url]
eabfiltr.sys   Thu   30-Nov   11:24:57   2006 - HPQuick Launch Buttons  - [url]http://www.carrona.org/dvrref.html#eabfiltr.sys[/url]
NETw4v32.sys   Sun   25-Feb   09:13:57   2007 - Intel Wireless WiFi Link Driver - [url]http://www.carrona.org/dvrref.html#NETw4v32.sys[/url]
PxHelp20.sys   Fri   2-Feb   16:23:57   2007 - Sonic CD/DVD driver (used by many different CD/DVD programs) - [url]http://www.carrona.org/dvrref.html#PxHelp20.sys[/url]
rimmptsk.sys   Sat   24-Feb   00:42:21   2007 - Ricoh Memory Card Reader driver - [url]http://www.carrona.org/dvrref.html#rimmptsk.sys[/url]
rimsptsk.sys   Tue   23-Jan   02:40:19   2007 - Ricoh Memory Card Reader driver - [url]http://www.carrona.org/dvrref.html#rimsptsk.sys[/url]
rixdptsk.sys   Tue   23-Jan   03:03:27   2007 - Ricoh Memory Card Reader driver - [url]http://www.carrona.org/dvrref.html#rixdptsk.sys[/url]
RTKVHDA.sys   Mon   12-Mar   07:29:40   2007 - Realtek HD Audio Codec Driver - [url]http://www.carrona.org/dvrref.html#RTKVHDA.sys[/url]
Rtlh86.sys   Mon   5-Mar   08:28:50   2007 - Realtek 8101/8168/8169 Wired Network Driver - [url]http://www.carrona.org/dvrref.html#Rtlh86.sys[/url]
smserial.sys   Mon   9-Oct   12:47:55   2006 - Motorola SM56 voice modem driver - [url]http://www.carrona.org/dvrref.html#smserial.sys[/url]
SynTP.sys   Fri   12-Jan   16:06:00   2007 - Synaptics TouchPad driver - [url]http://www.carrona.org/dvrref.html#SynTP.sys[/url]

BSOD BUGCHECK SUMMARY
Code: 
[font=lucida console]
Built by: 6001.18488.x86fre.vistasp1_gdr.100608-0458
Debug session time: Sun Oct 10 17:15:36.779 2010 (UTC - 4:00)
System Uptime: 0 days 1:47:40.047
BugCheck 24, {1904aa, 8b1674d4, 8b1671d0, 8467f3c8}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCacheCoherencyFlush+51 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6001.18488.x86fre.vistasp1_gdr.100608-0458
Debug session time: Tue Oct  5 08:29:08.595 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:53.520
BugCheck FE, {8, 6, 1, 92662000}
Probably caused by : usbhub.sys ( usbhub!UsbhTrapFatalTimeout_x9f+1a )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6001.18488.x86fre.vistasp1_gdr.100608-0458
Debug session time: Tue Oct  5 08:18:35.089 2010 (UTC - 4:00)
System Uptime: 0 days 0:27:41.075
BugCheck FE, {8, 6, 1, 90936000}
Probably caused by : usbhub.sys ( usbhub!UsbhTrapFatalTimeout_x9f+1a )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6001.18488.x86fre.vistasp1_gdr.100608-0458
Debug session time: Sun Oct  3 11:57:05.958 2010 (UTC - 4:00)
System Uptime: 2 days 5:02:24.302
BugCheck 116, {89468510, 8e815f40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6001.18488.x86fre.vistasp1_gdr.100608-0458
Debug session time: Thu Sep 30 08:37:53.024 2010 (UTC - 4:00)
System Uptime: 3 days 2:18:18.761
BugCheck 116, {89b4b008, 8f00ff40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6001.18488.x86fre.vistasp1_gdr.100608-0458
Debug session time: Sun Sep 26 13:11:43.630 2010 (UTC - 4:00)
System Uptime: 3 days 22:18:29.533
BugCheck 116, {92c47468, 8f00ff40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Tue Sep 21 06:44:08.875 2010 (UTC - 4:00)
System Uptime: 0 days 22:35:26.528
BugCheck 116, {892e4510, 8ee9cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Mon Sep 20 08:08:09.964 2010 (UTC - 4:00)
System Uptime: 1 days 0:56:06.492
BugCheck 116, {88978158, 8e29cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Wed Sep 15 08:52:37.466 2010 (UTC - 4:00)
System Uptime: 1 days 1:14:52.295
BugCheck 116, {88f9d008, 8ee9cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Tue Sep 14 07:36:33.960 2010 (UTC - 4:00)
System Uptime: 2 days 13:22:09.646
BugCheck 116, {8889d200, 8ec9cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Sat Sep 11 18:13:40.855 2010 (UTC - 4:00)
System Uptime: 1 days 10:57:37.670
BugCheck 116, {a778c008, 8e49cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Thu Aug 26 00:12:43.380 2010 (UTC - 4:00)
System Uptime: 0 days 16:06:23.445
BugCheck 116, {865ba510, 8e29cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Wed Aug 25 08:05:35.865 2010 (UTC - 4:00)
System Uptime: 0 days 0:14:54.826
BugCheck 116, {99d48510, 8e62cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Wed Aug 25 07:49:53.178 2010 (UTC - 4:00)
System Uptime: 0 days 14:46:55.985
BugCheck 116, {88899510, 8e09cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Tue Aug 24 09:01:57.381 2010 (UTC - 4:00)
System Uptime: 4 days 15:36:13.029
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
BugCheck 8086, {0, 0, 0, 0}
Probably caused by : iaStor.sys ( iaStor+a44f )
BUGCHECK_STR:  0x8086
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Thu Aug 19 17:25:02.730 2010 (UTC - 4:00)
System Uptime: 0 days 8:39:56.418
BugCheck 116, {86a9d510, 8e49cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Thu Aug 19 08:44:17.374 2010 (UTC - 4:00)
System Uptime: 0 days 20:53:21.625
BugCheck 116, {864fd510, 8e29cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Wed Aug 18 11:50:11.399 2010 (UTC - 4:00)
System Uptime: 0 days 10:34:52.201
BugCheck 116, {87a94510, 8e29cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Wed Aug 18 01:14:32.965 2010 (UTC - 4:00)
System Uptime: 0 days 2:44:28.325
BugCheck 116, {8640d510, 8e69cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Tue Aug 17 22:29:17.257 2010 (UTC - 4:00)
System Uptime: 2 days 9:37:29.661
BugCheck 116, {86667510, 8e69cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Sun Jul 25 20:52:47.183 2010 (UTC - 4:00)
System Uptime: 0 days 12:31:20.768
BugCheck 116, {93ec4008, 8e49cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Sun Jul 25 08:20:49.005 2010 (UTC - 4:00)
System Uptime: 0 days 23:30:09.073
BugCheck 116, {87eaa510, 8de9cf40, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Tue Jul 13 09:10:12.901 2010 (UTC - 4:00)
System Uptime: 4 days 15:26:37.078
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
BugCheck 8086, {0, 0, 0, 0}
Probably caused by : iaStor.sys ( iaStor+a44f )
BUGCHECK_STR:  0x8086
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Tue Jun 29 09:04:44.582 2010 (UTC - 4:00)
System Uptime: 2 days 1:54:29.158
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
BugCheck 8086, {0, 0, 0, 0}
Probably caused by : iaStor.sys ( iaStor+a44f )
BUGCHECK_STR:  0x8086
PROCESS_NAME:  Idle
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Tue Jun 22 09:10:27.853 2010 (UTC - 4:00)
System Uptime: 0 days 14:39:46.738
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
BugCheck 8086, {0, 0, 0, 0}
Probably caused by : iaStor.sys ( iaStor+a44f )
BUGCHECK_STR:  0x8086
PROCESS_NAME:  Idle
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Tue Apr 27 09:07:14.350 2010 (UTC - 4:00)
System Uptime: 2 days 16:15:38.995
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
BugCheck 8086, {0, 0, 0, 0}
Probably caused by : iaStor.sys ( iaStor+a44f )
BUGCHECK_STR:  0x8086
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.16973.x86fre.vista_gdr.091208-0542
Debug session time: Tue Apr  6 12:14:03.681 2010 (UTC - 4:00)
System Uptime: 1 days 3:09:18.573
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
BugCheck 8086, {0, 0, 0, 0}
Probably caused by : iaStor.sys ( iaStor+a44f )
BUGCHECK_STR:  0x8086
PROCESS_NAME:  Idle
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.16901.x86fre.vista_gdr.090805-0102
Debug session time: Fri Jan 29 12:12:25.006 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:03.930
BugCheck D1, {a6c42000, 2, 0, 8e32bbc0}
*** WARNING: Unable to verify timestamp for bdselfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdselfpr.sys
*** WARNING: Unable to verify timestamp for PCTCore.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
Probably caused by : bdselfpr.sys ( bdselfpr+6bc0 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  TrustedInstalle
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.16901.x86fre.vista_gdr.090805-0102
Debug session time: Fri Jan 15 21:20:36.498 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:21.388
BugCheck D1, {9fbfe000, 2, 0, a0526428}
*** WARNING: Unable to verify timestamp for bdselfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdselfpr.sys
*** WARNING: Unable to verify timestamp for PCTCore.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
Probably caused by : bdselfpr.sys ( bdselfpr+6428 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  winlogon.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.16830.x86fre.vista_gdr.090302-1506
Debug session time: Fri Jan 15 15:41:40.792 2010 (UTC - 4:00)
System Uptime: 0 days 0:23:25.753
*** WARNING: Unable to verify timestamp for bdselfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdselfpr.sys
BugCheck 1000008E, {c0000005, 83084aa9, ab9cf5bc, 0}
*** WARNING: Unable to verify timestamp for PCTCore.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
Probably caused by : bdselfpr.sys ( bdselfpr+50d0 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  TrustedInstalle
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.16830.x86fre.vista_gdr.090302-1506
Debug session time: Thu Jan 14 17:28:50.639 2010 (UTC - 4:00)
System Uptime: 0 days 0:23:41.487
*** WARNING: Unable to verify timestamp for bdselfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdselfpr.sys
BugCheck 1000008E, {c0000005, 82c84aa9, ab26f5bc, 0}
*** WARNING: Unable to verify timestamp for PCTCore.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
Probably caused by : bdselfpr.sys ( bdselfpr+50d0 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  TrustedInstalle
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.16830.x86fre.vista_gdr.090302-1506
Debug session time: Thu Jan 14 12:32:17.984 2010 (UTC - 4:00)
System Uptime: 0 days 15:56:50.091
*** WARNING: Unable to verify timestamp for bdselfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdselfpr.sys
BugCheck 1000008E, {c0000005, 82c84aa9, a94675bc, 0}
*** WARNING: Unable to verify timestamp for PCTCore.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
Probably caused by : bdselfpr.sys ( bdselfpr+50d0 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  TrustedInstalle
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.16830.x86fre.vista_gdr.090302-1506
Debug session time: Wed Jan 13 13:17:00.451 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:51.326
BugCheck D1, {9e9ea000, 2, 0, 9f726428}
*** WARNING: Unable to verify timestamp for bdselfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdselfpr.sys
*** WARNING: Unable to verify timestamp for PCTCore.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
Probably caused by : bdselfpr.sys ( bdselfpr+6428 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  winlogon.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Debug session time: Wed Jan 13 13:09:25.115 2010 (UTC - 4:00)
System Uptime: 0 days 0:18:15.080
*** WARNING: Unable to verify timestamp for bdselfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdselfpr.sys
BugCheck 1000008E, {c0000005, 828848f9, 95e475bc, 0}
*** WARNING: Unable to verify timestamp for PCTCore.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
Probably caused by : bdselfpr.sys ( bdselfpr+50d0 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  TrustedInstalle
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Debug session time: Wed Jan 13 12:50:23.365 2010 (UTC - 4:00)
System Uptime: 0 days 0:16:52.313
*** WARNING: Unable to verify timestamp for bdselfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdselfpr.sys
BugCheck 1000008E, {c0000005, 824848f9, 9e2ff5bc, 0}
*** WARNING: Unable to verify timestamp for PCTCore.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
Probably caused by : bdselfpr.sys ( bdselfpr+50d0 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  TrustedInstalle
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Debug session time: Tue Jan 12 07:17:37.682 2010 (UTC - 4:00)
System Uptime: 0 days 4:59:38.860
*** WARNING: Unable to verify timestamp for bdselfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdselfpr.sys
BugCheck 1000008E, {c0000005, 820848f9, a1a535bc, 0}
*** WARNING: Unable to verify timestamp for PCTCore.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
Probably caused by : bdselfpr.sys ( bdselfpr+50d0 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  TrustedInstalle
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Debug session time: Mon Jan 11 21:33:41.210 2010 (UTC - 4:00)
System Uptime: 0 days 4:52:06.713
*** WARNING: Unable to verify timestamp for bdselfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdselfpr.sys
BugCheck 1000008E, {c0000005, 820848f9, 9e6ab5bc, 0}
*** WARNING: Unable to verify timestamp for PCTCore.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
Probably caused by : bdselfpr.sys ( bdselfpr+50d0 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  TrustedInstalle
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Debug session time: Mon Jan 11 16:40:53.887 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:07.813
*** WARNING: Unable to verify timestamp for bdselfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdselfpr.sys
BugCheck 1000008E, {c0000005, 820848f9, a687b5bc, 0}
*** WARNING: Unable to verify timestamp for PCTCore.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
Probably caused by : bdselfpr.sys ( bdselfpr+50d0 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  TrustedInstalle
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Debug session time: Mon Jan 11 16:18:08.722 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:49.643
*** WARNING: Unable to verify timestamp for bdselfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdselfpr.sys
BugCheck 1000008E, {c0000005, 820848f9, a20435bc, 0}
*** WARNING: Unable to verify timestamp for PCTCore.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
Probably caused by : bdselfpr.sys ( bdselfpr+50d0 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  TrustedInstalle
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]
 

My Computer

System One

Thanks for the advice
So far I've removed HP Quick play and installed SP2.

I ran the Memory Diagnostic test for 7 passes all with no error.

The HD Diagnostic just ended and gave me a message that my dipostition code was 0x00 (?????)

The FurMark Test.... I wasn't sure how long to leave it running .... I know in your reply it said to more or less leave it until something goes wrong, but the temperature rose from 54 to 73 and pretty much stayed at 73 for about 30 minutes.
Let me know if you need me to run it again .


Prime95 ran for 8 hours with no errors


I'll try to update the drivers next....
 

My Computer

System One

This driver concerns me: 349557b9.sys
Can you locate it in C:\Windows\System32\drivers?
If so:
- please right click on it and select Properties, then select the Details tab and see if that gives any clue as to the maker.
- go to the free Jotti's malware scan and submit the driver for scanning there.
 

My Computer

System One

That's OK. If you have time, search the entire computer for it. Sometimes "non-standard" drivers launch from different places - so it may be elsewhere on the system. I checked the MSINFO32 report and the last memory dump and that driver isn't there - so I wouldn't spend a lot of time looking for it.

Continue updating the drivers and let us known if you get another BSOD. If you do, please zip it up and upload it with your next post.
 

My Computer

System One

Thanks usasma. Well everything has been running fine so far, no BSOD but my laptop freezes up when Bitdefender is doing... anything.... so I may uninstall it.
The only other problem I have had is that since updating the Realtek HD Audio Codec Driver the audio has problems switching from headphones to the speakers.
Do you have nay advice or should I ask for help in another forum about this?
:)
 

My Computer

System One

There is a RollBack feature in Drivers tab of the device properties in Device Manager.
Give that a try.

As for the BitDefender:
Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the BitDefender from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of BitDefender using this free tool: How to uninstall BitDefender
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
Click to expand...
 

My Computer

System One

ok so there was another crash :( .
wasn't doing anything at that time, I had left it on and when I came back it had restarted and there was a notification that there was an unexpected shutdown.
I have zipped up the files and attached them.
 

My Computer

System One

The dump file blames bthusb.sys - a Windows file that works with the USB ports.
It's not likely that there's a problem with a Windows file - so we start with other drivers that are associated with your USB ports.

You have very little free memory, which probably makes your system run very, very slowly. I would suggest that you use Autoruns to eliminate some of the unnecessary startup items.

What do you have connected to your USB ports?
Do you have a webcam, media card reader, fingerprint reader, or other built in device?
For example, there is a MagicJack loading in your startups.

Also, please remove or update these older drivers that were loaded at the time of the crash (please note that many of them were included in my last BSOD analysis). Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
Click to expand...

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: Driver Reference ).
Please pay particular attention to any dated 2008 or earlier:
Code: 
[font=lucida console]
PxHelp20.sys Fri Feb 02 16:23:57 2007 (45C3ABED)
 - Sonic CD/DVD driver (used by many different CD/DVD programs)
 - [url=http://www.carrona.org/dvrref.html#PxHelp20.sys]Driver Reference[/url]

rixdptsk.sys Tue Jan 23 03:03:27 2007 (45B5C14F)
 - Ricoh Memory Card Reader driver
 - [url=http://www.carrona.org/dvrref.html#rixdptsk.sys]Driver Reference[/url]

HpqKbFiltr.sys Mon Jun 18 18:12:03 2007 (46770333)
 - HP Quick Launch Buttons HpqKbFiltr Keyboard Filter driver
 - [url=http://www.carrona.org/dvrref.html#HpqKbFiltr.sys]Driver Reference[/url]

NETw5v32.sys Mon Nov 17 10:40:18 2008 (49219062)
 - Intel Wireless WiFi Link Driver
 - [url=http://www.carrona.org/dvrref.html#NETw5v32.sys]Driver Reference[/url]

Rtlh86.sys   Mon Mar 05 08:28:50 2007 (45EC1B12)
 - Realtek 8101/8168/8169 Wired Network Driver
 - [url=http://www.carrona.org/dvrref.html#Rtlh86.sys]Driver Reference[/url]

rimmptsk.sys Sat Feb 24 00:42:21 2007 (45DFD03D)
 - Ricoh Memory Card Reader driver
 - [url=http://www.carrona.org/dvrref.html#rimmptsk.sys]Driver Reference[/url]

rimsptsk.sys Tue Jan 23 02:40:19 2007 (45B5BBE3)
 - Ricoh Memory Card Reader driver
 - [url=http://www.carrona.org/dvrref.html#rimsptsk.sys]Driver Reference[/url]

cpqbttn.sys  Mon Apr 14 15:39:04 2008 (4803B2D8)
 - HP Tablet PC Key Button HID Driver - HP Quick Launch Buttons
 - [url=http://www.carrona.org/dvrref.html#cpqbttn.sys]Driver Reference[/url]

ATSwpDrv.sys Wed Mar 28 16:44:15 2007 (460AD39F)
 - Slide Fingerprint [COLOR=Red]USB[/COLOR] Driver - AuthenTec, Inc.
 - [url=http://www.carrona.org/dvrref.html#ATSwpDrv.sys]Driver Reference[/url]

[/font]

BSOD BUGCHECK SUMMARY
Code: 
[font=lucida console]
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Sun Oct 24 11:01:28.559 2010 (UTC - 4:00)
System Uptime: 4 days 9:23:32.058
Probably caused by : BTHUSB.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
Bugcheck code 0000009F
Arguments 00000003 941de030 941d6328 87d51290
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]
 

My Computer

System One

usasma said:
What do you have connected to your USB ports?
Do you have a webcam, media card reader, fingerprint reader, or other built in device?
For example, there is a MagicJack loading in your startups.
Click to expand...

The only thing that is always connected to a USB port is the cooling pad, which just draws power. I also have a built in webcam and fingerprint reader (that I never use.) The magic jack was not connected at the time of the crash though.....
 

My Computer

System One

It doesn't matter if it's connected or not - Windows loads it's driver "just in case" it's needed.

Please download fresh copies of the drivers for the Bluetooth, webcam, MagicJack and fingerprint reader.
Also download a fresh set of chipset drivers (for the USB port drivers).
Then uninstall the current drivers for the above devices.
Then install the freshly downloaded drivers
Then monitor for further BSOD's
 

My Computer

System One

You must log in or register to reply here.
Back
Top