Announcement

Collapse
No announcement yet.

BSOD pain

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    BSOD pain

    My PC has once again decided to give me hassle again.
    This morning I switched it on only for it to BSOD every time at the same point just after the Windows logo screen and the OS loading up (the user password screen)

    I rebooted about 15 times, but it's always the same. I ran the windows memory test (in command prompt) and it said no problems detected. I'm assuming it's not the motherboard or CPU since it wouldn't even get to the pre windows loading screen.

    It seems to say this error code every time, *** STOP: 0x000000F4 0x00000003...

    Any ideas?

    #2
    I got good advice for my BSOD woes:


    Specifically, download a program called BlueScreenView and see which driver is causing the blue screen. Then we can get closer to a fix.

    Comment


      #3
      Also, in future have a copy of Linux lying around on CD (e.g. ubuntu or mint) and then if that works, you know it's not memory or other hardware causing the issue.

      Comment


        #4
        Almost always hardware in my exp. When it isn't its generally a driver or corrupt OS. Nailing it can be tough tho. Can you get into safe mode. If you can, go to event viewer and have a look at System and application in particular.

        If you can't boot to safe mode then it could be any of the things you have listed or the HDD. If thats the case, try a repair as this won't overwrite anything other than required sys files
        Last edited by NemesiS; 31-01-2011, 18:28.

        Comment


          #5
          It also BSODs in safe mode too at the same point. It's impossible to check any software as the OS refuses to load every single boot.
          Searching the internet seems to give no answer at all other than it could be anything.

          How do you do a repair?
          I booted from the Windows 7 disc and it game some options, but not repair option. Even when I pressed 'r' in the install Windows screen it took me to another screen with no repair option.

          Comment


            #6
            No no no. Use this guide as its very easy to follow and easier than me typing it off pat: http://www.sevenforums.com/tutorials...up-repair.html

            Tbh tho, if i were you and if you have access to another machine, i would whip out the HDD and connect it to another machine via internally or into a caddy and backup all your data and then plonk it back into your PC or laptop and format it and reinstall Win7. You'll probably find this will work if the issue isn't hardware related (fingers crossed), and you'll have a nice clean PC

            Comment


              #7
              Right,

              I backed up some data then reinstalled Win 7 without touching any hardware.
              So far it seems to be working fine on a fresh install.
              Though can software really cause BSODs as serious as I had?

              Also, if it wasn't software causing the problem, perhaps the main HDD might have bad sectors which corrupt after time?

              Just weird.

              Comment


                #8
                [quote=Supergoal;1806092]

                Though can software really cause BSODs as serious as I had?

                Also, if it wasn't software causing the problem, perhaps the main HDD might have bad sectors which corrupt after time?

                [quote]

                Yes, software can and does cause BSoD's. Usually when the OS gets screwed or corrupted or a driver has been installed which overwrites system dll's (tho you could attribute that to HW i suppose).

                In most cases tho, it is HW related with HDD, RAM or CPU/GPU (overheating) being the main culprits. Glad you sorted it anyway

                Comment


                  #9
                  Yeah cheers.

                  No doubt it will screw up soon again.

                  Comment


                    #10
                    quite often a crappy driver will overwrite a portion of memory that it's not supposed to - at which point windows will BSOD to prevent corruption (yes, the BSOD is to prevent corruption).

                    If you want to REALLY trap the driver that's causing the error (or anything else) then you can use the verifier option. If anyone wants to know more then ping me a PM and I'll go through it - you will still get a BSOD, but in windbg it'll tell you straight away what is causing the issue.

                    Comment

                    Working...
                    X