pc problem

[fanboy]

okay so recently replaced motherboard in my uncles computer as it was faulty, it was an msi n1996 board, in it was q6600 quad core, 4gb ram 667, 650 wd hard drive sata.

when changed the board over i tried my hard drive in it as his was not available at that time, it worked fine no problems, when i tried his hard drive in it would start up and as soon as it says loading windows (7), and the colorful dots appear it blue screens and resets everytime. Now i tried his hard drive in my working machine and it works fine, i done defrag on it, cleaned up registry, anti virus, malware checker, then tried it back in his machine same problem blue screen reset.

This doesn't make sense to me, as both machines work perfect with my hard drive and his only works on mine properly, surely that tells me all his computer components are okay any help would be appreciated. thanks.

 

[fanboy]

bump

 

[Igorian]

Post the details of the blue screen.

 

[xr4x4]

Was it a like for like board replacement ?

 

[krisdorey]

Post the details of the blue screen.

What he said.

And despite being a mac advocate, a bsod tends to be easily fixed

 

[krisdorey]

Why do people like powerfulp give Mac users a bad name?

Mac OSX is a fairly restricted OS (based on free/netbsd) which works incredibly well because Apple then restrict the hardware that it works on. Yes you can hackintosh a dell netbook but the pain is not worth it for what you achieve.

Windows allows a far greater degree of hardware but then with this comes issues of compatibility. So you can have far better performance for less price but the whole thing requires more work and patience.

As a PC developer (actually IBM mainframe then midrange/then proper unix such as HPUX, AIX) of 15 years and now a Mac/iOS/RIM (I wonder how long that last one will be on my CV!) developer, I can say that Apple produce the best hardware / software integration but are also the hardest overseer's of code and standards.

An Android app submission goes through very little of that of an iOS app which is either good or bad depending on your viewpoint.

It's a shame that a mindless few Mac users tar it for the rest of us.

 

[fanboy]

the board isnt like for like its a new gigabyte board, and works fine with my hard drive on it, sorry i cannot post blue screen because it no longer shows now :S just as i say u see windows logo and it stutters thn resets, fed up!.

 

[Monsterminty]

why was my post deleted?
try changing the bios setting in the hdd section from Sata to IDE.
or maybe try a chkdsk.

 

[Monsterminty]

i have nothing against mac users at all. lovely filing system.
unfortunatly it seems that the only advice powerfulp ever gives is "get a mac" which is in no way on topic or helpful to the OP. In fact its counter productive as it just insites arguments on which is better......it dosen't matter. the OP ust wants the problem he has RIGHT NOW solved.

the otherthing you could do is put in the hdd that worked, with the one that won't and boot from the working one, the hdd might then recieve any drivers it is missing.

but try the chkdsk first, then the bios then the above.

 

[digdilem]

Changing a motherboard, unless it's a direct swap, will require a reinstall of Windows.

It's trying to use low level drivers for the wrong chipset, and unlike mac and linux, windows has always handled this ungracefully. Same thing when trying to transfer a hard drive with windows to another pc.

Note: Don't format first, just run the windows install dvd/cd. Chances are your files will still be there, but any programs may need to be reinstalled afterwards.

 

[Astra99]

To me it sounds like the old motherboard and the new one, even though they may be the same "part number" are different versions. This can mean there is a fundamental difference in things like the hard disk controller. As the BSOD occurs before Windows starts to load, the hard disk controller is likely to be the culprit. If the OP can post details of the numbers at the beginning of the BSOD, we may be able to narrow it down. As another poster has said, there is often a setting in the BIOS to change the way in which the motherboard accesses the hard drive. It might be worth tyring the alternatives on this. Failing that, boot from the Windows 7 CD and try doing a Repair, which may or may not pick up the correct hard disk controller and permit booting. If that fails, connect the drive as a slave in another PC, get any data off it, put it back in and do a full format and reinstall of Windows.