New mobo leads to stop err, but not in safe mode

Discussion in 'Software' started by jf38081, Jul 20, 2007.

  1. jf38081

    jf38081 Private E-2

    After replacing a sock A (bad caps) with an new AM2 setup, I can boot to windows in safe mode and used the mobo and video cd's to install all the drivers onto the previous installation. In other words, I have not formatted, or reinstalled XP. The system seems to run fine in safe mode, but not in normal or diagnostic. Stop error is 0x0000007E

    Any way to salvage w/o having to reinstall XP?
     
  2. studiot

    studiot MajorGeek

    You are lucky that windows hasn't wanted reactivation (although its not all that scary for the legit).

    We really need some more detailed system info to help though.
    Also details of you resources in the way of windows disk, service packs loaded, and knowledge of msconfig.
    Since you can get to safe mode I expect a driver is amiss and should shouls be able to track it down using msconfig in diagnostic mode.

    If your stop error produces a minidump (enable debugging at the F8 options), rename it to .txt and post it here. Perhaps it will identify the culprit.
     
  3. jf38081

    jf38081 Private E-2

    Yes - thank you. We have the XP retail upgrade disc. The pc was updated with sp2 prior to the mobo upgrade. Also, yes, I am familiar with msconfig. Diagnostic mode was causing the same bsod as normal boot-up, but safe mode seems to work. I will try to find and post the mini-dump. If possible we can avoid reinstalling!
     
  4. studiot

    studiot MajorGeek

    Particularly important to fix it in your case then. A windows XP repair install (from an older XP disk) will fail if tried on a system that has subsequently been upgraded to SP2. You have to go for a clean install. Hopefully you can also start with a previous windows if it ever comes to that.

    Look for .dmp files for example mini122507.dmp is xmas day 2007 minidump.
     
  5. jf38081

    jf38081 Private E-2

    I ran a search for *.dmp on it only found EasyShare.dmp. Probably not the right one, eh?

    Any other ideas, short of a clean install?
     
  6. studiot

    studiot MajorGeek

    Don't let the minidump distract you it is not necessary, just might save a deal of effort on your part.

    If you boot to the options screen by tapping F8 as you start you will see that one of the options is
    enable debugging
    Choose this and it will boot normally to the stop error. At the stop error a minidump file is written to C:\windows\minidump.

    But you can boot to safe mode and run msconfig in diagnostic mode, selectively enabling drivers until you hit the culprit.

    You can try short cutting by suspecting the video driver (not used in safe mode) and roll back the driver in device manager or see if you can get an update from the graphics manufacturers or mobo website.
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds