Results 1 to 6 of 6

Thread: Oh Noes! BSOD!!

  1. #1

    Oh Noes! BSOD!!

    0x0000007A (0X00000003, 0xc0000005, 0x00000800)

    This page seems to suggest it's potentially a hard drive error given the 0x0000007A. But do any of those other three strings of numbers provide any additional clues I wonder?

  2. #2
    Senior Member nihil's Avatar
    Join Date
    Jul 2003
    Location
    United Kingdom: Bridlington
    Posts
    17,188
    Hi AK,

    We need some more information:

    1. What sort of hardware platform?
    2. what operating system (flavour of Windows)?
    3. What were you running at the time or trying to do?
    4. Using "Event Viewer" what messages are there in the system logs?



    The 0xc0000005 looks like it could be some sort of access violation or Registry problem.

  3. #3
    1. IBM T60 (there's no escaping these things )
    2. XP Pro SP2
    3. Don't know what the last thing the user had run, but it BSOD'ed a couple of times at bootup, then went back to normal. I'm assuming for now it's intermittent.
    4. Not much...Most errors I see don't look related. The only error I see that *may* have some relation around the same time period was a failure installing .NET Framework 2.0 SP1. It produced Event ID 10005, Source MsiInstaller.

    The 0xc0000005 looks like it could be some sort of access violation or Registry problem.
    The user is a Power User, not a local admin, so that would likely trigger any permissions-related errors.

    /edit --

    The MsiInstaller error and the reboot happened at almost the exact same time. The eventlog service started at bootup at 3:05, MsiInstaller error at 3:06.
    Last edited by AngelicKnight; December 7th, 2007 at 05:51 PM.

  4. #4
    Senior Member nihil's Avatar
    Join Date
    Jul 2003
    Location
    United Kingdom: Bridlington
    Posts
    17,188
    Well,

    I guess the first thing to try is running defrag and see if it will work. If there is anything wrong with the drive or file structure it will crap out with an error message.

    Then run chkdsk, and see if that will complete. Make sure that you get a report/log. Don't bother with a surface scan, the next step will handle that

    Then run the HDD manufacturer's diagnostics with a complete or full scan if that is an option.

    By the time you have done that we will know whether you have a hardware problem or it is Billy Windoze

    EDIT:

    Yes, the T60 is a rather popular businessman's laptop so it is hardly surprising.
    Last edited by nihil; December 7th, 2007 at 06:00 PM.

  5. #5
    Member
    Join Date
    Nov 2007
    Location
    Springfield, MO area
    Posts
    66
    sfc /scannow

    Thats worked for me on HP notebooks with that error before.

  6. #6
    Senior Member
    Join Date
    Oct 2003
    Location
    MA
    Posts
    1,052
    id do mfg hdd diags chkdsk then an inplace upgrade

Similar Threads

  1. IASTOR.SYS BSOD w/ Dell computers
    By Blunted One in forum Hardware
    Replies: 27
    Last Post: October 4th, 2006, 05:05 AM
  2. Can this program cause a BSOD?
    By The Texan in forum Operating Systems
    Replies: 5
    Last Post: August 16th, 2006, 02:45 AM
  3. xpsp2 BSOD "DRIVER_IRQ_NOT_LESS_OR_EQUAL"
    By cross in forum Hardware
    Replies: 19
    Last Post: June 3rd, 2005, 11:01 PM
  4. m$ BSOD *** STOP errors
    By phishphreek in forum General Computer Discussions
    Replies: 13
    Last Post: January 19th, 2005, 06:10 PM
  5. 31337 Bsod
    By White Scorpion in forum Microsoft Security Discussions
    Replies: 10
    Last Post: January 9th, 2005, 11:30 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •