[2457]

so, here is a computer, friend asked me to take a look.
Nothing fancy, Pata drives, VIA K8T800 + VIA VT8237 on the mobo, old sempron 2800+ in the socet, samsung memory 512/400 , geforce mx4000 vga in the AGP slot.


Heat is low, 25-28 at idle, after finishing xp install 32-35.
Chipset temp. is normal, cold to touch. (about handwarm. but did try to add a fan there) case is open, vga card is cold too..


xp installs fine, first boot is fine into the system, everything works properly. At next start windows trys to load up, then gives a blue screen of death, and restarts.

From this point, no boot into safe mode, or anything..
DID try to install various flavors of XP, non slip streamed, sp1, and sp2 slipped, no luck.
Did even make a special disk with its own drivers wich WAS used on the computer.

Things have been runing for years, it was just a maintainance re-install.
No hardware changes, no nothing.

I did try different memory, and VGA.
HDD is errorfree, I did check it. (80 Gbyte seagate, did not take too long)
the mobo was working too,
I just can't figure out why does it go to BSOD.
power supply is O.K. , 450 watt mercury (I know its a cheap crap, but it did work fine).

the computer is used as basicly a media player...
no heavy loads, no nothing.
Only xvid-avi-mp3..

BIOS settings are correct, boot procedure is normal, POST does not find any error, the memoryand vga card works in other computers.

No mather what I do, I can install the thing, but if I shut it off next start windows boot just gives a BSOD and restarts. And no way to boot in safemode or any other..

//linux live disc DSL is booting with out any error..

Any.. hints?
When I saw thing like this, the mobo had problems with the voltage regualtors, but these are O.K..

[spearfish]

Whoops, double post.

This post has been edited by spearfish: 11 May 2008 - 05:04 PM

[spearfish]

DSL is a life saver. The fact that it boots without problem, however, doesn't mean much since it requires I believe 8 mb of RAM.

Hmm... As for your problem...

This + this > This

[2457]

the problem is hardware related, but thanks.
I'm not looking to substitude windows. (the guy wants to actualy USE the computer to other things than reading linux forums and asking for help with every single thing)

I need to find out why is install and first boot O.K., and why does it go BSOD at secund...

[ferrari12508]

What error is reported on the BSOD?

[ccrasherdeb]

I would suggest testing the MB first. Turn off the system and unplug the power cable. If you have the manual for the MB, pull the battery and reset the CMOS via the jumper pins. You can get the manual online if you dont have it for that MB. Then boot into BIOS and set the time etc set the proper boot device and set anything else needed. Then reinstall windows.
You might also want to try writing 0's to the HD and then with the same program format the drive before you install windows. This will ensure that your HD sectors are all good and the HD is clean. A windows format/install does not usually correct or repair bad sectors. You can get the HD utility program(s) free from the HD manufacturer.
Also make sure that you get and install all the windows updates and install a good AV/aspyware and run it before you restart the system.

If you leave and media in the drives after an install, they can and many times will cause problems upon the second bootup if the BIOS are not configured properly. This happens quite often on a proprietary system with a proprietary windows OS. If your using a proprietary OS, get all the proper drivers from the manufacturer of the computer for their version of windows and get them installed before rebooting the system. Check for any BIOS updates for that MB and find out what any newer BIOS problems are addressed.

Make sure that there is no CD or floppy in the drives. Many times, any media in the drives or a flash drive installed on bootup can cause a BSOD.

[2457]

I suggest a motherboard problem too.
Bios have been resetted.

full zero wrte to a 10 Gbyte partition is done.
Thats where I install.

The installation finished, and I can boot the system once.
But no more. No bootable media was left at the optical drive.
I boot from hard drive.

BSOD error code is just a blink.

Other I could be aware of is some sorth of (?) driver incompatibility, wich would be strange, couse I do not install any driver.

NO un needed stuff is even connected.
the USB on the front panel is disconnected, so is every single thing I don't need.

For safety I replaced the ribbon cables, and mesure voltage levels on the run, no spike or drop.

Will try with a nother hard disk drive, I happen to have laying around one, but I bet the drive is o.k..

I'm afraid that its the motherboard gone byby..

[2457]

solved.
Xp have some built in drivers for this chipset.
And becouse of them its not working properly.

I donloaded fresh drivers, and integrated them into an xp install disc.
Works like a charm.

Never had the idea of this kind of problem.
Anyways, it has been solved.

Thanks for the suggestions.

too bad there is no option in the forum to change the title, or at least indicate that this topic is closed, becouse it has been solved.

[calvinthedestroyer]

Hmm, how did you integrate the new drivers into the windows XP install?

Also, is there any way to tell what drivers are causing the BSOD?

[Nykc]

This post has been edited by Nykc: 15 April 2010 - 10:38 AM

[calvinthedestroyer]

screw you man, it was the third result on the list when I did a search on the issue that I was having with a PC. If (Dream in Code) does not allow for the revival of older topics, then Dream In Code should state that in there user policy and or close the topics once they get old (i.e. in computer years an old topic would be one that is over three seconds old)

PS. did you even read the post or did you just see the date and decide to be a dick?

[Tom9729]

calvinthedestroyer, on 15 April 2010 - 01:27 PM, said:

screw you man, it was the third result on the list when I did a search on the issue that I was having with a PC. If (Dream in Code) does not allow for the revival of older topics, then Dream In Code should state that in there user policy and or close the topics once they get old (i.e. in computer years an old topic would be one that is over three seconds old)

PS. did you even read the post or did you just see the date and decide to be a dick?

It's general forum courtesy to not revive old threads. There are a lot of things not in the user policy that would still be unacceptable to do on here or any forum.

Chances are this guy is long gone, if you have a question you should start a new topic (possibly with a reference to this one).

By the way this is probably what you're looking for.
http://www.google.co...ial+add+drivers

[no2pencil]

calvinthedestroyer, on 15 April 2010 - 12:27 PM, said:

If (Dream in Code) does not allow for ...

It's really just proper netiquette & common sense mixing with common courtesy.

calvinthedestroyer, on 15 April 2010 - 12:27 PM, said:

PS. did you even read the post or did you just see the date and decide to be a dick?

If I know NYKC, he probably just went right for the dick.

[raziel_]

goto bios stop your SATA connection to your HDD use IDE and start it again it may help you