Welcome! Register for a free account (or login) > How does it work?
|
|
![]() ![]() |
Oct 27 2009, 11:29 AM
Post
#1
|
|
|
Authentic Member ![]() ![]() Group: Authentic Member Posts: 53 Joined: 23-March 05 Member No.: 28,421 Operating System: XP |
Stop: 0X0000008E usbscan.sys - address B5453AE2 base at B5451000, datestamp 480254ce Could you provide some help here?? Thanks, Dave |
|
|
|
Oct 27 2009, 04:54 PM
Post
#2
|
|
![]() Advanced Member Group: Tech Team Posts: 813 Joined: 10-March 05 From: Key West Member No.: 27,393 Operating System: Win 7_64 Ultimate |
|
|
|
|
Oct 27 2009, 11:07 PM
Post
#3
|
|
|
Authentic Member ![]() ![]() Group: Authentic Member Posts: 53 Joined: 23-March 05 Member No.: 28,421 Operating System: XP |
Hi, here is the analysis from the tool. I appreciate your help. What do you suggest now?
Dave -------------------------------------------------------------------------------- Welcome to WhoCrashed Home Edition 1.01 -------------------------------------------------------------------------------- This program checks for drivers which have been crashing your computer. Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice. This program does post-mortem crash dump analysis with the single click of a button. To obtain technical support visit www.resplendence.com/support To check if a newer version of this program is available, click here. Just click the Analyze button for a comprehensible report ... -------------------------------------------------------------------------------- Home Edition notice -------------------------------------------------------------------------------- This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis. -------------------------------------------------------------------------------- Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Tue 10/27/2009 3:32:50 PM your computer crashed This was likely caused by the following module: usbscan.sys Bugcheck code: 0x1000008E (0xC0000005, 0xB5453AE2, 0x9D460B78, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\drivers\usbscan.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB Scanner Driver The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified. On Sun 10/25/2009 11:56:14 PM your computer crashed This was likely caused by the following module: usbscan.sys Bugcheck code: 0x1000008E (0xC0000005, 0xBA586AE2, 0x9B766B78, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\drivers\usbscan.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB Scanner Driver The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified. On Thu 10/22/2009 1:14:12 PM your computer crashed This was likely caused by the following module: usbscan.sys Bugcheck code: 0x1000008E (0xC0000005, 0xBA576AE2, 0x9BD4DB78, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\drivers\usbscan.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB Scanner Driver The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified. On Thu 10/22/2009 12:38:17 PM your computer crashed This was likely caused by the following module: usbscan.sys Bugcheck code: 0x1000008E (0xC0000005, 0xB9CA1AE2, 0x9BEA2B78, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\drivers\usbscan.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB Scanner Driver The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified. On Wed 10/21/2009 5:40:58 PM your computer crashed This was likely caused by the following module: usbscan.sys Bugcheck code: 0x1000008E (0xC0000005, 0xB9CA5AE2, 0x9CD37B78, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\drivers\usbscan.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB Scanner Driver The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified. On Fri 10/16/2009 4:12:52 PM your computer crashed This was likely caused by the following module: usbscan.sys Bugcheck code: 0x1000008E (0xC0000005, 0xB9CB1AE2, 0x9C20FB78, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\drivers\usbscan.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB Scanner Driver The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified. On Fri 10/16/2009 2:29:00 PM your computer crashed This was likely caused by the following module: igxpdv32.dll Bugcheck code: 0xEA (0x872BDB30, 0x89FA7BA8, 0x8A2E30A8, 0x1) Error: THREAD_STUCK_IN_DEVICE_DRIVER file path: C:\WINDOWS\system32\igxpdv32.dll product: Intel Graphics Accelerator Drivers for Windows NT® company: Intel Corporation description: Component GHAL Driver On Fri 10/16/2009 7:04:53 AM your computer crashed This was likely caused by the following module: pci.sys Bugcheck code: 0x1000008E (0x80000004, 0x806ECADD, 0x9BBC9704, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\drivers\pci.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Plug and Play PCI Enumerator The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified. On Fri 10/16/2009 6:32:09 AM your computer crashed This was likely caused by the following module: usbscan.sys Bugcheck code: 0x1000008E (0xC0000005, 0xB9CA5AE2, 0xA2FC5B78, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\drivers\usbscan.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB Scanner Driver The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified. On Sun 10/11/2009 3:55:56 AM your computer crashed This was likely caused by the following module: usbscan.sys Bugcheck code: 0x1000008E (0xC0000005, 0xB9CA1AE2, 0x9CFD1B78, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\drivers\usbscan.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB Scanner Driver The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 10 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. |
|
|
|
Oct 27 2009, 11:18 PM
Post
#4
|
|
![]() Advanced Member Group: Tech Team Posts: 813 Joined: 10-March 05 From: Key West Member No.: 27,393 Operating System: Win 7_64 Ultimate |
What is the make and model of the computer?
Appears to be an Intel graphics driver. If you knowingly have a third party graphics card please advise. |
|
|
|
Oct 27 2009, 11:29 PM
Post
#5
|
|
|
Authentic Member ![]() ![]() Group: Authentic Member Posts: 53 Joined: 23-March 05 Member No.: 28,421 Operating System: XP |
Hi, it's a Dell Vostro 1510 laptop. I don't have a special graphics card in it. I do have an HP Laserjet M1522nf that required drivers for the scanner... I'm wondering if it's the culprit.
|
|
|
|
Oct 27 2009, 11:35 PM
Post
#6
|
|
![]() Advanced Member Group: Tech Team Posts: 813 Joined: 10-March 05 From: Key West Member No.: 27,393 Operating System: Win 7_64 Ultimate |
Appears likely.
Is this a new problem? Did this scanner work previously? http://support.dell.com/support/downloads/...tid=&impid= |
|
|
|
Oct 28 2009, 10:33 AM
Post
#7
|
|
|
Authentic Member ![]() ![]() Group: Authentic Member Posts: 53 Joined: 23-March 05 Member No.: 28,421 Operating System: XP |
It's been happening for a couple of months. The scanner seems to work, but is a problem from time to time.
Thanks for the URL... but I don't know what to do with it. |
|
|
|
Oct 28 2009, 06:00 PM
Post
#8
|
|
![]() Advanced Member Group: Tech Team Posts: 813 Joined: 10-March 05 From: Key West Member No.: 27,393 Operating System: Win 7_64 Ultimate |
Sorry for not clarifying but I was just posting the driver link to your laptop.
I should have pointed out the Printer/Scanner drivers from HP: http://h20000.www2.hp.com/bizsupport/TechS...mp;swEnvOID=228 I would try and load the latest firmware: http://h20000.www2.hp.com/bizsupport/TechS...Item=ma-70811-2 If the issue persists then I would load/reload the latest driver. Note the driver is either USB or Serial port depending on how your device is connected. |
|
|
|
Oct 28 2009, 07:28 PM
Post
#9
|
|
|
Authentic Member ![]() ![]() Group: Authentic Member Posts: 53 Joined: 23-March 05 Member No.: 28,421 Operating System: XP |
Thanks Jephree, I just loaded the firmware and drivers. I'll see if the issue persists. Your help is greatly appreciated!!!
Dave |
|
|
|
![]() ![]() |
Similar Topics
| Topic Title | Replies | Topic Starter | Views | Last Action | |||
|---|---|---|---|---|---|---|---|
![]() |
12 | km1234 | 208 | 16th March 2010 - 11:41 PM Last post by: Tomk |
|||
![]() |
86 | connemara22 | 3,685 | 8th January 2010 - 03:02 AM Last post by: oldman960 |
|||
![]() |
45 | Psymin1 | 2,524 | 18th December 2009 - 08:30 PM Last post by: LDTate |
|||
![]() |
4 | kart7ny | 402 | 10th December 2009 - 09:39 AM Last post by: CatByte |
|||
|
Time is now: 22nd March 2010 - 09:00 AM |