Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Puzzling BSOD error


  • Please log in to reply
2 replies to this topic

#1 BurghRocks

BurghRocks

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:10:22 AM

Posted 15 June 2011 - 02:24 PM

Hi all,

I'm a little stumped trying to troubleshoot a BSOD error and was hoping someone smarter than I could point me in the right direction. My neighbor has an old XP Dell computer which was running fine until the power went out this morning. When it boots back up now, it loads windows, goes to the desktop and then anywhere from 5-45 seconds moves to a BSOD error 0x0000008E (0xc0000005, 0x805787F8, 0xA880599C, 0x00000000). I can boot to safe mode, safe mode with networking (and surf the web), and safe mode command prompt all without receiving the error. As soon as I go back to a regular boot, it happens again. So far I have tried the following:
1. Ran quick and full tests on hdd using the WD hard drive diagnostics tool, came back clean.
2. Tested the memory by pulling out a pair and just running with half of it, then swapping with the other half, then changing the slots for each one, bios picks it up the change in memory every time and does not give me an issue.
3. Disabled the onboard lan in bios but did not seem to matter
4. System>Device Manger does not report any issues (in safe mode, cant get that far in normal boot without a bsod)
5. Performed a system restore to two days prior (Sunday, 6/12) and received the bsod after was told the restore was successful
6. Scanned the registry for errors and fixed what was found, had no effect.
7. unchecked all unnecessary programs in startup through msconfig and that did not have an effect
8. His virus definitions and scans were up to date but I still ran one in safe mode online using Housecall and it came back clean.
9. Ran memtest86 and tests came back fine.
Probably a few other things I cant recall at the moment.

I'd really like to determine if its hardware or software, then I could decide if I should try to blow away the hard drive and try for a reinstall. I'm puzzled because my thought was that it was software or driver related since it would work just fine in safe mode but as soon as I go back to a normal boot I get the error in under a minutes time. But if that were the case, why would a successful system restore to a few days ago not work?

It makes more sense that its hardware related since it occurred at the time of a loss of power and everything I have read regarding the x8E errors points mainly to hardware. If thats the case though, why isn't the hardware failing in safe mode?

I appreciate any input you might have. Many thanks in advance.
Burgh

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,723 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:22 AM

Posted 15 June 2011 - 03:04 PM

Let's try this.

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html .

Double-click BlueScreenView.exe file.

When scanning is done, click Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis

#3 BurghRocks

BurghRocks
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:10:22 AM

Posted 15 June 2011 - 04:14 PM

Hi Louis,
Thanks for the response. Here is the info from the last few errors:

Dump File : Mini061511-03.dmp
Crash Time : 6/15/2011 4:07:45 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x805787f8
Parameter 3 : 0xf750699c
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+a17f8
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647)
Processor : 32-bit
Crash Address : ntoskrnl.exe+a17f8
Stack Address 1 : ntoskrnl.exe+14105d
Stack Address 2 : ntoskrnl.exe+e7765
Stack Address 3 : ntoskrnl.exe+e7798
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061511-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 94,208
==================================================

==================================================
Dump File : Mini061511-02.dmp
Crash Time : 6/15/2011 11:05:38 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x805787f8
Parameter 3 : 0xf768699c
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+a17f8
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647)
Processor : 32-bit
Crash Address : ntoskrnl.exe+a17f8
Stack Address 1 : ntoskrnl.exe+14105d
Stack Address 2 : ntoskrnl.exe+e7765
Stack Address 3 : ntoskrnl.exe+e7798
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061511-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 94,208
==================================================

==================================================
Dump File : Mini061511-01.dmp
Crash Time : 6/15/2011 11:04:00 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x805787f8
Parameter 3 : 0xf769699c
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+a17f8
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647)
Processor : 32-bit
Crash Address : ntoskrnl.exe+a17f8
Stack Address 1 : ntoskrnl.exe+14105d
Stack Address 2 : ntoskrnl.exe+e7765
Stack Address 3 : ntoskrnl.exe+e7798
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061511-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 94,208



Looks like an OS reinstall? If so, would have assumed system restore would have fixed the kernal issue but perhaps not.

Thanks again,

Burgh




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users