BSOD After Universal Restore ATIH 2010
After upgrading to a new machine (motherboard, cpu, memory and 1 TB HDD) I backed up my existing 80 GB HDD and using the universal restore moved my data to the new drive. Old machine had a DVI monitor that came with an AGP card and dvi port. New motherboard doesn't have an AGP slot but does have an on board DVI port. Since monitor worked perfect on old machine I figured it should work on new one.
When booting after restore I get the BSOD with stop: 0X0000007E (0XC0000005, 0X00000000, 0XB4A4CB0BC, 0XBA4CADB8). No hardware mentioned. The only way I can boot is by pressing F8 and selecting VGA Mode even after installing the monitor driver and chipset drivers. My OS is Win XP Pro. SP 3 (Student Ver) Monitor is a Samsung 940B LS19HABKBJ/XAA. MY question is: What does stop: 0X0000007E (0XC0000005, 0X00000000, 0XB4A4CB0BC, 0XBA4CADB8) translate to in english? Is not a DVI port a DVI port? Will I also have to upgrade to another monitor?
Thanx for any advice with my problem.


- Log in to post comments

I responded to this duplicate post here http://forum.acronis.com/forum/18372.
- Log in to post comments

Hi Pat L
Thanks for your reply. MIcrosoft debugger sounds like just the thing I need. However, I must not be doing something right. After installing the software and rebooting to capture the blue screen nothing happens. No new dump files in the minidump folder. Any Ideas or would it be better to contact the the author of the thread that tells the what and how of this process?
thanks Bob
- Log in to post comments

In COmputer properties > Advanced > Startup and Recovery > make sure you have all boxes checked under System Failure, and select minidump (64k)
- Log in to post comments

Pat L wrote:In COmputer properties > Advanced > Startup and Recovery > make sure you have all boxes checked under System Failure, and select minidump (64k)
All boxes are checked under System Failure and minidump (64k) selected. Still no dumps. Current that is. I do show a list of previous dumps going back to 04. Never knew they were even there. Oh the pain I suffered trying to figure out what caused those stops. : )
- Log in to post comments

Any chance it is somewhere else? There is a directory path under these checkboxes. When you copy this into a run command, does it open the expected directory?
Do you see anything in the event viewer about the failure or dump creation?
bummer...
- Log in to post comments

[quote=Pat L]
Any chance it is somewhere else? There is a directory path under these checkboxes. When you copy this into a run command, does it open the expected directory?
Do you see anything in the event viewer about the failure or dump creation?
Lots of stuff in event viewer.....don't clear it very often. However did clear it and re-booted. I attached a disc warning I found in system. Don't know if its relevant. Don't know what I looking for. I could capture the whole list. Not too long
Attachment | Size |
---|---|
56099-93874.jpg | 63.99 KB |
56099-93877.jpg | 63.99 KB |
- Log in to post comments

Normally the dump is done on the disk and then a flag is put on the paging file. When the computer boots back on, Windows finds the flag and tells you "your computer has recovered from a serious error, blah, blah".
This warning doesn't look like it is serious.
OK. It looks like this debug path is going nowhere on your system since you don't get the mini dumps. Weird...
Some things your do to eliminate possibilities:
- run memtest86 on a reboot, to verify your memory is OK.
- make sure that the resolution and refresh rate setting of your display is supported by both your graphics card and your monitor,
- uninstall any graphics driver that has been installed by Windows, and point the device manager to drivers provided by your motherboard manufacturer.
- Log in to post comments

Pat L wrote:Normally the dump is done on the disk and then a flag is put on the paging file. When the computer boots back on, Windows finds the flag and tells you "your computer has recovered from a serious error, blah, blah".
This warning doesn't look like it is serious.OK. It looks like this debug path is going nowhere on your system since you don't get the mini dumps. Weird...
Some things your do to eliminate possibilities:
- run memtest86 on a reboot, to verify your memory is OK.
- make sure that the resolution and refresh rate setting of your display is supported by both your graphics card and your monitor,
- uninstall any graphics driver that has been installed by Windows, and point the device manager to drivers provided by your motherboard manufacturer.
Been reading everything I can find on BSOD 0x0000007e most common causes seem to be memory and video. I haven't done the memtest yet, it takes a lot of time, which I'm short on but will try to get it done.
My money is on the video. After running universal restore I uninstalled the video drivers and accessory items from old video and installed new drivers for new motherboard. Using a program called Regdet (Registry Detective) I searched the registry for leftover previous video card. Found a boatload of stuff. I deleted everything I could. However, some items refused to be deleted. Namely, driver files called "PCI\VEN_1002&DEV_4153&SUBSYS_04021002&REV_00\4&b5fb279&0&0008" Also "PCI\VEN_1002&DEV_4173&SUBSYS_04031002&REV_00\4&b5fb279&0&0108" These registery items are listed under the old video card model. Don't know how I can remove them. Sent an email to the mfg (Radeon) asking if they had some kind of script or uninstaller to remove them but haven"t heard from them yet.
One article I researched said when you view the bluescreen, after giving the stop error windows, will also say it is saving info to a minidump file. My bluescreen does not say that. So, that is probably why I'm not getting any dmp files.
- Log in to post comments