Groups

    PC Help Please..

    I have just fired up the family pc and have the 'Blue screen of Death' showing. No matter how I boot up - safe mode etc - it eventually goes back to the error screen.

    I am now on the lappy and have searched the net - seems like you can download Regcure.. Is this product any good. Are there better ones??


    It would also be fine if I had an internet connection on the other system.. no such luck - just the blue screen...

    How do I transfer the recovery repair files and boot up? Indeed, do I want to be doing this or is it some other problem. I have a memory stick.

    Any suggestions or help greatly appreciated from the techies...

    Thanks

    29 Comments

    You must write down the STOP code that is presented with the BSOD.

    -- [edit]

    It'll be something like this though the numbers will be different - *** STOP: 0x0000008E (0xC00000005, 0x804EF844, 0xF89463FC,0x00000000)

    Your need a copy of Windows XP or Vista CD to do a repair ! :thumbsup:

    Original Poster

    abomination;3148899

    You must write down the STOP code that is presented with the BSOD.



    And do what with it please?? I see the code. It is not always the same error message. Sometimes it says disable antivirus etc, sometimes it is disable bios (??) sometimes it says dumping physical memory..

    I am not technical at all I am afraid..:-(

    Original Poster

    Mecoconuts;3148908

    Your need a copy of Windows XP or Vista CD to do a repair ! :thumbsup:



    I have an 'old' copy - came installed from factory on this pc though

    as abomination says you need the stop code and the filename causing the issue.
    once you have that you may be able to use something like ebcd to boot the system from cd to repair ir or more likely do an install over the top (repair)

    Original Poster

    abomination;3148899

    You must write down the STOP code that is presented with the BSOD.-- … You must write down the STOP code that is presented with the BSOD.-- [edit]It'll be something like this though the numbers will be different - *** STOP: 0x0000008E (0xC00000005, 0x804EF844, 0xF89463FC,0x00000000)



    ***STOP:0x0000007E (0XC0000005,0xF7705079,0xF7A1D7DC,0xF7A1D4D8)

    If you can boot it from dos, via a boot cd or floppy, and type chkdsk /r it might fix the issue, but it takes a while ie 1-2 hrs

    Original Poster

    happy donkey;3148983

    If you can boot it from dos, via a boot cd or floppy, and type chkdsk /r … If you can boot it from dos, via a boot cd or floppy, and type chkdsk /r it might fix the issue, but it takes a while ie 1-2 hrs



    yeah - can get to the command prompt - do I just type CHKDSK /r at the end of the line or go to the C:

    Again apologies - I am in unknown territory

    What version of Windows are we talking about?

    Original Poster

    abomination;3149013

    What version of Windows are we talking about?



    its XP

    Banned

    press del, f2 or whatever it is when starting your comp to get to your CMOS screen

    check the boot order and make sure that cd-rom is first

    insert your windows cd and reboot computer

    when the option is available select 'repair' :thumbsup:

    hope this helps

    I take it you've tried selecting "Last Known Good Configuration" in the boot options (F8).

    If so do you have access to the Windows Setup CD or did it come preinstalled on the computer without reinstallation media.

    Original Poster

    abomination;3149065

    I take it you've tried selecting "Last Known Good Configuration" in the … I take it you've tried selecting "Last Known Good Configuration" in the boot options (F8).If so do you have access to the Windows Setup CD or did it come preinstalled on the computer without reinstallation media.



    Yeah tried last known good etc. Preinstalled with no reinstallation media. Great eh? I have an older copy of XP but dont want to overwrite

    Rockhound;3149011

    yeah - can get to the command prompt - do I just type CHKDSK /r at the … yeah - can get to the command prompt - do I just type CHKDSK /r at the end of the line or go to the C:Again apologies - I am in unknown territory


    sorry just type into box at the end of the line, if I remeber right, its been like 10mths since I did it.

    The first parts go quick but be patient with the last stage,

    microsoft.com

    CHKDSKchkdsk drive /p /rThe chkdsk command checks the specified drive and … CHKDSKchkdsk drive /p /rThe chkdsk command checks the specified drive and repairs or recovers the drive if the drive requires it. The command also marks any bad sectors and it recovers readable information.You can use the following options:/p Does an exhaustive check of the drive and corrects any errors./r Locates bad sectors and recovers readable information.Note If you specify the /r option, the /p option is implied. When you specify the chkdsk command without arguments, the command checks the current drive with no options in effect.



    Report back after completing the check as h/donkey outlined :).

    Banned

    you try that? it wont overwrite anything, it will just repair the system files

    Original Poster

    abomination;3149147

    Report back after completing the check as h/donkey outlined :).



    ok thanks guys - the pc has stayed alice long enough for chkdsk to start Will report soion I hope.

    according to MS that error relates to a firewire isue.
    try going into the bios and disabling firewire or removing the card if it not onboard

    Original Poster

    looks like this is going to take a while....

    Original Poster

    wolf359;3149334

    according to MS that error relates to a firewire isue.try going into the … according to MS that error relates to a firewire isue.try going into the bios and disabling firewire or removing the card if it not onboard



    sorry wolf - please translate for the uninitiated. I do not have anything connected by firewire. Just take out all usb connections?? What is a bios..??

    Rockhound;3149218

    ok thanks guys - the pc has stayed alice long enough for chkdsk to start … ok thanks guys - the pc has stayed alice long enough for chkdsk to start Will report soion I hope.



    If its BSOD'ing at random times, it could be a hardware failure (most likely broken\slow fan on cpu) that might be causing the PC to overheat - I'd advise taking the side of the case of and checking the fan is spinning on the CPU (or you can look in bios to see what heat the CPU is at and what speed the fan is running - you should see a temperature well be 60C, anything higher and overheating is probably the problem...)

    The bios is the first thing that loads when you turn the computer on before the 'Windows XP' screen is shown - and it has a setup menu (usually entered by pressing F2, F10 or ESC on boot-up). If you look carefully on the screen when you turn on it will usually say something like 'Press F2 to enter setup' - and when you do it will take you to a set of menus (usually on a blue background!). One of the menus normally displays the current temperature of the CPU, speed of the fan(s) and the often the voltages from the PSU.

    Original Poster

    jah128;3149361

    If its BSOD'ing at random times, it could be a hardware failure (most … If its BSOD'ing at random times, it could be a hardware failure (most likely broken\slow fan on cpu) that might be causing the PC to overheat - I'd advise taking the side of the case of and checking the fan is spinning on the CPU (or you can look in bios to see what heat the CPU is at and what speed the fan is running - you should see a temperature well be 60C, anything higher and overheating is probably the problem...)



    No this problem is new and fan is going round. Just 'happened' tonight. Pc just did not boot up right and got the blue screen. Pc not been on long enough to overheat (i dont think)

    Rockhound;3149375

    No this problem is new and fan is going round. Just 'happened' tonight. … No this problem is new and fan is going round. Just 'happened' tonight. Pc just did not boot up right and got the blue screen. Pc not been on long enough to overheat (i dont think)



    You'ld be surprised how quick they overheat if the fan fails (or heatsink gets clogged up) but doesn't sound like the problem in this case. Next time it BSODs have a quick look in the bios to see how hot it is, just so you can rule that out for sure...

    I forgot to ask, is a file mentioned along side the STOP code?

    Anything like "random-name.sys"? Also did you update Windows previously before booting up today, SP3 for example? Any new hardware added (not just internal, new external devices etc)? Lastly, do you have any USB peripherals connected?

    Original Poster

    abomination;3149420

    I forgot to ask, is a file mentioned along side the STOP code?Anything … I forgot to ask, is a file mentioned along side the STOP code?Anything like "random-name.sys"? Also did you update Windows previously before booting up today, SP3 for example? Any new hardware added (not just internal, new external devices etc)? Lastly, do you have any USB peripherals connected?



    No file name mentioned. I have tried several times to do CHKDSK but after a while the blue screen comes up. It is not the same message or error code on each screen.

    It said there were updates ready - may have been one of the kids clicked install I didnt!

    No new hardware or devices in last month anyway.

    Usb - things like printers etc - yes - disconnect??

    You're running CHKDSK from the Recovery Console and not from within Windows, correct? Or am I a little bit ahead of myself, *it happens* :).

    you wouldn't need to have anything connected by firewre. if the driver corrupts it will BSOD whether you're using it or not.
    the BIOS is the first screen you see when you turn the computer on. you usually press delete or one of the F keys to enter it. once in there you'd be looking for something like "integrated peripherals" inside there you can disable the firewire. if MS is correct then you'd be up & running

    Original Poster

    abomination;3149549

    You're running CHKDSK from the Recovery Console and not from within … You're running CHKDSK from the Recovery Console and not from within Windows, correct? Or am I a little bit ahead of myself, *it happens* :).



    correct - it isnt playing ball though. I have also tried the disk reboot - only it is for XP Pro - I have XP home so doesnt seem to like it!

    Original Poster

    guys - i think this looks a bit beyond me - will need to take it to a pro.:-(

    Thanks very much for all your advice and help....:thumbsup:
    Post a comment
    Avatar
    @
      Text
      Top Discussions
      1. Surprise! The HUKD Summer Flamedeer Hunt 2017 **OFFICIAL THREAD** (trading …4672205
      2. What is there free to do in your town?2544
      3. Back to school: what's your views on your kids uniform and piercing rules e…27121
      4. Sky Fibre Max44

      See more discussions