Computer reboots on shut down.

darklord17ed · Joined: Dec 09, 2003 Posts: 94

This is a AMD 2.2 Ghz, 1Gig pc 3200 ram. on a Biostar M7NCD PRO MOBO. This box is Running WindowsXP media center 2005. The changes are it is a new MOBO. Could not do a direct replacement to the old one.

On shut down the box just reboots. Disabled auto restart to get the error code . They are as follows.

STOP: 0x0000007E (0xC0000005,0xF78BDDAB,0x78F29B0,0x78F26AC)

nv_agp.sys - Address F78BBAB base at F78BB000, Datestamp 3d7903e1

I have tried to update the driver for this MOBO, but get the same Error code.

As allways Thank you in advance for all your suggestions.

Ed

zlim · Joined: Mar 11, 2005 Posts: 2422

just looking at nv_agp tells me it has to to with your Nvidia card.
I'll search later for a 7E error - right now my computer isn't doing any searching - all search sites refuse to load.

found this

Quote:

when i try to shut my pc off it gives me a post error 0x0000007e
when it gives me the error it also points to nv_agp.sys

my mobo is an a7n8x dlx which has nforce 2 onboard sound model

i tried reading up some and most people think thats the nforce 2 isnt compatible with the mobo it comes on (how much sense does that make?)

so nvidia has a new patch that is suppose to fix it but i tried installing patch and still gives me error

so i tried to uninstall nforce altogether and it didnt give me the error so it must have been the nforce drivers

Do you have nvidia onboard sound on the new mobo?

and I found this

Quote:

when i try to shut my pc off it gives me a post error 0x0000007e
when it gives me the error it also points to nv_agp.sys

my mobo is an a7n8x dlx which has nforce 2 onboard sound model

i tried reading up some and most people think thats the nforce 2 isnt compatible with the mobo it comes on (how much sense does that make?)

so nvidia has a new patch that is suppose to fix it but i tried installing patch and still gives me error

so i tried to uninstall nforce altogether and it didnt give me the error so it must have been the nforce drivers

Before you downgrade drivers, check if nVidia has drivers for the chip on your motherboard. It may not have shipped with the latest drivers.

darklord17ed · Joined: Dec 09, 2003 Posts: 94

thanks zlim,
I'll try that as soon as I get home this evening. If that fails, do you have any other thoughts?

Thanks,

Ed

zlim · Joined: Mar 11, 2005 Posts: 2422

Sorry, no. I don't know anything about different motherboards and what works and doesn't work with each. I just google for your errors to see if anyone had the same problem.

User: inactive Posts:

The LAW, written or unwritten, is that you cannot change motherboards on Windows XP unless they are EXACT duplicates.

Windows senses that you've moved the OS to a different computer and will fail, in one way or another, to operate properly.

There are ways to fake out the OS to accept the new motherboard, but for the life of me, I don't have that information here.

However it's been written up many times on the internet.

Good Luck,
Shadow Cool

darklord17ed · Joined: Dec 09, 2003 Posts: 94

Shadow,
That would imply that a reload from the D:\ portion of the drive would fail also. Correct?
I do not have the recovery disks to this particular computer.

Thanks,

Ed

User: inactive Posts:

The recovery disk will have the specific drivers for the original mobo.
NOT the new one. Same problem. Once you change the mobo, you just as well use that original disk for a drink coaster.

Touche'

A clean install from a fresh Windows CD may be required if you don't use one of those Work-Arounds I was eluding to.

Then burn a Ghost Image of your new setup to a DVD for a new Restore Disk.

Good Luck,
Shadow Cool

darklord17ed · Joined: Dec 09, 2003 Posts: 94

Ok,
ya'll can close this tread. I relented and did a fresh format and install of Windows XP Pro.

Thanks to all that posted.

Ed

User: inactive Posts:

Earlier this year I built a new PC to test out Vista.

When my old PC started getting 'funky and weird' on me, a few months ago, I retired it and made the new one my main PC running Windows XP-Pro/SP2.

Knowing I couldn't just move the HD from the old mobo to the new one, I did this:

First I cloned the old HD to a new one that I put into the new PC as my backup drive. Then I installed XP on a brand new 200 gig SATA2 drive, as my new main drive.

When I wanted some data or utilities from the old system I just copied them from the backup drive. I have now migrated everything I need, from the clone of the old HD to my new one and I've reformatted the backup drive and set it to FAT-32, for all my backups, Ghost Images, etc.

I finally found the problem in the old computer. It was a failing HD.
Seagate sent me a new one and with a Ghost Restore from April, the old PC is back and running at 100% efficiency.

If my new PC pulls a "Mt St. Helens" on me, I've got my old PC to fall back on.

Cheers Mates!
Shadow Cool

darklord17ed · Joined: Dec 09, 2003 Posts: 94

Ok,
I'm not sure at what point but, the reformat and load of a clean Windows XP Pro install is producing the same error. I have and have loaded the original drivers for this MOBO. Any thoughts? Any?

Thanks in advance as always.

Ed

zlim · Joined: Mar 11, 2005 Posts: 2422

Are these the drivers as well as the BIOS you are using?
http://www.biostar-usa.com/mbdownloads.asp?model=M7NCD%20PRO

http://www.biostar-usa.com/knowledgespec.asp?faqid=99990
http://www.biostar-usa.com/knowledgespec.asp?faqid=99979

darklord17ed · Joined: Dec 09, 2003 Posts: 94

darklord17ed · Joined: Dec 09, 2003 Posts: 94

zlim · Joined: Mar 11, 2005 Posts: 2422

There was a BIOS update in 2007 but I'm very reluctant to tell anyone to update the BIOS because if something goes wrong, you have a doorstop. A working computer that reboots is way better than one that does nothing.
If there is a text file with the BIOS update, usually a log after you put the BIOS on a floppy or CD, read that but don't do the BIOS update. If you see anything in the log that seems to address the problem you are having, then you have to decide if you want to do a BIOS update.
Some newer BIOS updates backup the old BIOS so if something goes wrong, you can flash it back to the older BIOS. I don't know if this update does that.

Download M7NCDPRObios.pdf that explains the BIOS settings.
Read thru page 15 in the pdf which goes thru the agp settings. That seems to be where the problem lies because the error has agp in it.
Write down the current settings then just start changing one at a time to see if you can stop the reboot.

At this point, I'm out of any ideas of further things to try.

If it were me, I'd try the settings but let the BIOS update alone. (That said, I successfully updated the BIOS on an old micron notebook last week but I was sweating bullets wondering if it would work out okay). I also had to flash the BIOS on an HP notebook several years ago. I was told to do this by HP so I didn't have a choice. That also went okay but I was lucky. I've read horror stories.

darklord17ed · Joined: Dec 09, 2003 Posts: 94

I have also heard the stories of bad Flashes. And almost had one myself. but thanks to a backup got it cleared up.

I feel more comfortable messing around with the registry than the
BIOS.

I'll take a look at file you suggest and see if it makes any difference and report back ASAP.

darklord17ed · Joined: Dec 09, 2003 Posts: 94

Sorry for taking so long to post back. The solution was to back the full driver pack out and then use the install the drivers one at a time feature till I found the one that was the problem. And wala It's up and running.

Thanks as always for the thoughts and suggestions.