BSOD - help going through BF2 withdrawl!!!

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

    #1

    BSOD - help going through BF2 withdrawl!!!

    Okay the quick run down. I lost power at the house for 4 days last week. When it finally came back on my computer turned on fine (Awesome Surge Protector helps!) and then the next day the PC would not power on. I called tech support for my Power Supply and they said PSU was dead, so I did an RMA exchange (gotta love 3 year warranties). The new Power Supply finally arrived last night. I installed the beast, and when I booted I got all the way to the desktop and then BSOD. 0x000000FC!!! It would only last about 30 seconds once turned on until the Stop error occurred. Also my Copperhead mouse was not powering on, but my Tarantula keyboard was fine!

    Anyone ever have this issue?? Anyone know a fix for this issue?
    Microsoft help page did not offer much in the resolution area.

    The computer was working fine before the power went out, and it was actually turned off the day I lost power. Don't know if the PSU going bad had anything to do with it??

    All my drivers are current since I was having severe Crash to Desktops, so I updated everything not long ago. Only new additions to the computer were a Tarantula keyboard and a Barracuda headset, but thouse were working fine on PC for 3 weeks prior to this issue.

    Thanks for any suggestions!!! I really want to get back to playing BF2!!!

    PC Specs:
    Thermaltake Tsunami Case
    Ausus A8N-SLI Deluxe
    AMD FX-55 Clawhammer
    Zalman 7000B CPU Fan
    Ultra X Connects 500W modular PSU
    2Gb Corsair Platinum Matched Twins
    2 Segate 120Gb HD in RAID0
    Ausus nVidia 6800
    SB Audigy 2 Gamer
    Razer Copperhead mouse
    Razer Tarantula keyboard
    Razer Barracuda headset
    Saitek Cyborg Evo joystick
    Powered 7 Port USB Hub
  • Stormy{CAN}
    Member
    • Apr 2007
    • 958

    #2
    Re: BSOD - help going through BF2 withdrawl!!!

    Have a read here,

    Comment

    • kulamonster3

      #3
      Re: BSOD - help going through BF2 withdrawl!!!

      Thanks Stormy!!

      Unfortunately I have already been to that Microsoft page, and my system does not contain a legacy hardware DVD decoder needing the Mpegport.sys driver! Hence my puzzlement at getting this STOP error.

      And I already have the DEP (data execution prevention) set to alwaysoff!!
      {this was because of an nVidia dll causing my CTDs, and turning off the DEP was how Microsoft recommended to solve that issue} So it is not that either.....SIGH!! The system was built over 2 years ago with XP Pro SP2 so it never had to upgrade to SP2 and this Microsoft support page talks about the error occuring after you install XP SP2??

      As stated above the system was perfectly fine before: losing power, my PSU dying and me installing the new Power Supply. I also just ran a full PC-Check and all hardware - Passed!! So when the Power Supply died it did not take any other hardware with it. Also the Computer will boot using BART PE, so it has to be a Windows or a driver (other than Mpegport.sys) problem!!!

      But why now?? If this was a driver issue it should have been happening prior to now?? Putting in a new PSU has nothing to do with drivers!!!

      I will try a RESTORE rollback to last month, before I installed the Tarantula keyboard and Barracuda headset to see if that solves this BSOD / driver mess!!

      Any other suggestions are more than welcome at this point!!

      Comment

      • camper.
        Member
        • Dec 2006
        • 3459

        #4
        Re: BSOD - help going through BF2 withdrawl!!!

        Boot up in safe mode, first of all. That should show whether it's a driver or startup program. If it works in safe mode, boot up in clean boot mode (google it). If it still works, you have a dodgy startup program.

        Comment

        • kulamonster3

          #5
          Re: BSOD - help going through BF2 withdrawl!!!

          Just to let everyone know, the Registry Roleback worked!!! I am up and running again. I had to reinstall the Tarantual drivers, but all seems to be stable now (or at least as stable as it was before this SNAFU....lol) So it had to be something screwy with a driver, I didn't narrow it down to which one, but as long as I can play BF2 again.....I'm happy!!!!!!

          Comment

          Working...