Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Random BSOD's


  • Please log in to reply

#1
ejf

ejf

    Member

  • Member
  • PipPip
  • 22 posts
Crashes happening for over a week now.

Clean XP install. Malware/virus eliminated as likely culprit



whocrashed:

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.



On Fri 10/30/2009 17:28:08 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000008E (0xC0000005, 0x3F800B82, 0xB5B17CE4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware




On Fri 10/30/2009 0:48:32 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000008E (0xC0000005, 0x3F800B82, 0xB8147CE4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware




On Wed 10/28/2009 15:47:10 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0xB8340D70, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 10/27/2009 21:09:04 your computer crashed
This was likely caused by the following module: kmixer.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x7C90100B, 0xB4707CCC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\kmixer.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Audio Mixer
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 10/27/2009 18:04:52 your computer crashed
This was likely caused by the following module: hidusb.sys
Bugcheck code: 0x100000D1 (0x383B2E1E, 0x2, 0x8, 0x383B2E1E)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\hidusb.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Miniport Driver for Input Devices
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 10/27/2009 15:28:22 your computer crashed
This was likely caused by the following module: unknown_image
Bugcheck code: 0x1000008E (0xC0000005, 0x54162C, 0xB3D47CF0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on unknown_image





On Tue 10/27/2009 15:25:13 your computer crashed
This was likely caused by the following module: unknown_image
Bugcheck code: 0x1000008E (0xC0000005, 0x541634, 0xB8317CF0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on unknown_image
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program
  • 0

#3
ejf

ejf

    Member

  • Topic Starter
  • Member
  • PipPip
  • 22 posts
==================================================
Dump File : Mini103009-02.dmp
Crash Time : 10/30/2009 20:40:52
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x804fb1b9
Parameter 3 : 0xba51fcb8
Parameter 4 : 0xba51f9b4
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+241b9
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_qfe.090206-1316)
Processor : 32-bit
==================================================

==================================================
Dump File : Mini103009-01.dmp
Crash Time : 10/30/2009 13:28:04
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x3f800b82
Parameter 3 : 0xb5b17ce4
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+376c
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5756 (xpsp_sp3_qfe.090209-1316)
Processor : 32-bit
==================================================

==================================================
Dump File : Mini102909-01.dmp
Crash Time : 10/29/2009 20:48:29
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x3f800b82
Parameter 3 : 0xb8147ce4
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+376c
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5756 (xpsp_sp3_qfe.090209-1316)
Processor : 32-bit
==================================================

==================================================
Dump File : Mini102809-02.dmp
Crash Time : 10/28/2009 14:15:06
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x00541633
Parameter 3 : 0xb3e27cf0
Parameter 4 : 0x00000000
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
==================================================

==================================================
Dump File : Mini102809-01.dmp
Crash Time : 10/28/2009 11:47:05
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x1000007f
Parameter 1 : 0x00000008
Parameter 2 : 0xb8340d70
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6a7e5
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_qfe.090206-1316)
Processor : 32-bit
==================================================

==================================================
Dump File : Mini102709-04.dmp
Crash Time : 10/27/2009 17:08:58
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x7c90100b
Parameter 3 : 0xb4707ccc
Parameter 4 : 0x00000000
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
==================================================

==================================================
Dump File : Mini102709-03.dmp
Crash Time : 10/27/2009 14:04:49
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x383b2e1e
Parameter 2 : 0x00000002
Parameter 3 : 0x00000008
Parameter 4 : 0x383b2e1e
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+6fda
File Description : USB 1.1 & 2.0 Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5778 (xpsp_sp3_qfe.090318-1347)
Processor : 32-bit
==================================================

==================================================
Dump File : Mini102709-02.dmp
Crash Time : 10/27/2009 11:28:18
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x0054162c
Parameter 3 : 0xb3d47cf0
Parameter 4 : 0x00000000
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
==================================================

==================================================
Dump File : Mini102709-01.dmp
Crash Time : 10/27/2009 11:25:07
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x00541634
Parameter 3 : 0xb8317cf0
Parameter 4 : 0x00000000
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
==================================================
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Clean install with a Genuine Microsoft XP installation disk?
  • 0

#5
ejf

ejf

    Member

  • Topic Starter
  • Member
  • PipPip
  • 22 posts
I tried that too. Actually, this is the third clean install (one xp home, one xp pro [giving me two licenses for my two computers] and this "custom").

This happens on all so I don't think it's the build. If you see something to indicate it might be unique to this build, I'll try one of the others again.


Edit: It may help to know that I also ran memtest overnight (completed 13 iterations) without a reported error.

Edited by ejf, 30 October 2009 - 04:50 PM.

  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, unfortunately, you're out of luck, because Toshiba doesn't provide any diagnostic tool.

Thanks to Broni for the instructions
  • 0

#7
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
When done with the above please do the following....

Go to
Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Let me know if this fixes the problem
  • 0

#8
The Skeptic

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
I would suggest, in addition, a RAM test. The randomness of the crashes could indicate to a faulty RAM module. Please download memtest from my list of links below and create a bootable CD. Boot with the new CD and run the program for at least 1 complete cycle. There shouldn't be any errors (red lines) during the test.
  • 0

#9
ejf

ejf

    Member

  • Topic Starter
  • Member
  • PipPip
  • 22 posts
Ran memtest a few nights ago and it completed 13 iterations without reporting an error.

Chkdsk /r ran last night, and Seatools for windows didn't report any errors when I ran the HD diagnostics.

I hadn't had a crash for a while (36 hours) then had a crash shortly after getting online this morning.
  • 0

#10
ejf

ejf

    Member

  • Topic Starter
  • Member
  • PipPip
  • 22 posts
Well, maybe I had a crash while sleeping too... something also seems to have messed with my system clock so the times are screwy.

On Sun 11/1/2009 13:09:27 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000008E (0xC0000005, 0x3F800B82, 0xB5967CE4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Sat 10/31/2009 0:40:57 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xC0000005, 0x804FB1B9, 0xBA51FCB8, 0xBA51F9B4)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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/30/2009 17:28:08 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000008E (0xC0000005, 0x3F800B82, 0xB5B17CE4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware
  • 0

Advertisements


#11
delaorden

delaorden

    New Member

  • Member
  • Pip
  • 6 posts
hello my friend. I would suggest to make a complete check of all your hardware drivers, i.e., update them. After that, as suggested above, I would make a nice clean. Unplug ram modules, use the old good eraser. I use a dryer hair in cold position to undust inside the box. Never pointing directly to cpu fan. Use small paint brush, those used by artists, to clean your mobo and parts. The brush can't be made of plastic or artificial . The best are made from wooden and animal bristle to avoid statics. And last, check if your power supply is actually supporting all your hardware. It seems weird but if your power supply is under capacity, this can make system hault and show a terrible BSOD.
Thank you my friend...
  • 0

#12
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Keeping time problems is normally a indication of a low cmos battery.
What version of memtest did you use and was it a windows based version?
HD diagnostics within windows is not as complete as running outside of windows.
  • 0

#13
ejf

ejf

    Member

  • Topic Starter
  • Member
  • PipPip
  • 22 posts
My experience is that the time is usually set back to some point when the battery is running low, but I'll look into it.

Memtest 4.00 from bootable CD

I'll run the Seatools again from bootable CD too then.


400W power supply for minimal hardware. I imagine they can go bad after a while. Any way to test their output to make sure it's clean? Inside of the case also got a good cleaning after the problem started.

Edited by ejf, 31 October 2009 - 08:24 AM.

  • 0

#14
ejf

ejf

    Member

  • Topic Starter
  • Member
  • PipPip
  • 22 posts
One more question... Since the power supply was mentioned as an issue, is there any possibility that a dirty power source between the house's circuit panel and the computer's power supply could be causing these crashes? I don't know how to test that though.
  • 0

#15
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
The crash at least last night indicates a OS problem.
In post 4 I asked:

Sorry for the delay, I'm reviewing your topic now. This request will be closed, everyone else please start a new topic.
This is an automated reply

Your answer suggests you reinstalled but not clear on if you used a Genuine Original Microsoft disk or was it a copy?
Also let's try this:



Go Start and then to Run ("Start Search" in Vista),
Type in: sfc /scannow
Click OK (Enter in Vista).
Have Windows CD/DVD handy.
If System File Checker (sfc) finds any errors, it may ask you for the CD/DVD.
If sfc does not find any errors in Windows XP, it will simply quit, without any message.
In Vista you will receive the following message: "Windows resource protection did not find any integrity violations".

For Vista users ONLY: Navigate to C:\Windows\Logs\CBS folder. You'll see CBS.log file.
Usually, it's pretty big file, so upload it to Flyupload, and post download link.


If you don't have Windows CD....
This applies mostly to Windows XP, since Vista rarely requires use of its DVD while running "sfc"
Note This method will not necessarily work as well, as when using Windows CD, because not always ALL system files are backed up on your hard drive. Also, backed up files may be corrupted as well.

Go Start and then Run
type in regedit and click OK


Navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup

You will see various entries Values on the right hand side.

The one we want is called: SourcePath

It probably has an entry pointing to your CD-ROM drive, usually D and that is why it is asking for the XP CD.
All we need to do is change it to: C:
Now, double click the SourcePatch setting and a new box will pop up.
Change the drive letter from your CD drive to your root drive, usually C:
Close Registry Editor.

Now restart your computer and try sfc /scannow again!


Thanks to Broni for the instructions
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP