It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hello, fellow gogers.
Last weekend I moved into São Paulo and took most of my things, leaving the rest in Campinas at my girlfriend’s. I brought my PC, but left all my DVDs.
Anyway, yesterday I tried to start my desktop PC for the first time since the move and after going into Win Vista, it crashed with a blue screen of death before finishing loading the last startup programs (though it reached the desktop screen). Every subsequent boot failed, BSODing before reaching the desktop.
I booted into safe mode and set up a scandisk for the next boot. The next boot, win runs disk checks on both my HDs and reboots after ending. Next boot, BSOD again.
Tried to enter safe mode again and it locked up loading crcdisks.sys and after some time, rebooted by itself.
Now… here comes some explanations about my setup: I have an Asus extreme gamer motherboard and two HDs: A sata drive with windows installed in it (my drive C) and an IDE drive (drive D).
For some reason I don’t quite understand, I had to set up Drive D as primary slave so that the computer would boot. Otherwise, I have to have a Win Vista DVD on my DVD drive to boot the machine.
So… next attempt: I entered the bios setup and removed my drive D from primary slave. After that, windows wouldn’t load: boot failure.
So, I get back into setup and re add drive D as primary slave, but… it still fails to boot with the same boot failure error.
Finally, I ask you guys: what on God’s Earth is wrong with my machine and is there a way to fix it up without loosing everything I have in both HDs?
This question / problem has been solved by dawveeimage
More than likely your motherboard is treating the SATA as the primary IDE channel, a lot of boards did that when SATA was relatively new, you might be able to change that in the BIOS somewhere
As for the BSODs, my instinct says driver (if it comes up with an error mentioning a file) or damaged ram (if it comes up with something like error at 0x0000004a or something similarly cryptic)
One way or the other I'd defkinitely recommend getting Memtest86 and letting that run overnight to test the ram thoroughly. The ISO is the best option since you're already having trouble keeping your OS stable, better to use the bootable CD version
I apologize if this isn't helpful, but after a move my first thought is something just got knocked loose, like a hard drive cable. Have you checked in the case to make sure all the cables are seated correctly?
The BSoDs always come up mentioning possible new hardware not properly installed. Tonight I shall open the PC and check for loose stuff.
A friend of mine thinks my Drive D passed away. I just hope he's not right.
I agree about some stuff coming loose.
What type of cpu cooler do you have?
If you have a tower cooler (tall one), that could be your issue.
Take it off, re-apply thermal paste, and re-attach it.
If you are ever moving a machine with a tower cpu cooler for any distance, it is best to take it off, move the case, and re-attach again, as you can actually damage the cpu if you dont.
Look for loose power connection and cables.
Take out your cards and re-seat them also.
IIRC, Creative cards give the error of new hardware found when they are un-seated.
Asus Zonar sound cards can also give the error of new hardware when they go bad.
Yesterday's night I opened the PC and checked the HDs for loose cables. I found none. I still couldn't boot properly so I used a WIn XP CD a friend had given me back yesterday to help me boot.
I hit another BSoD, so I tried safe mode again and it worked. I used CCleaner to clean the machine and everything, then I backed up some stuff and finally, I deactivated my Wireless DLink card.
I rebooted the machine and managed to go into windows without BSoDs.
I spent a couple of hours enjoying some games and then, Tried another boot without the cd in the drive. I figured I can press F8 at startup and manually choose the IDE HD to boot, but it still won't work on auto. I'm still to figure why.
Also, today I'll open the machine again and check the wireless card to see if it's loose or if it has fried indeed.
Do you have both IDE HDD and CD/DVD drive?
If so, try setting the jumpers on them to CS (Cable Select).
I had one hdd master/slave jumper go out on me, and would only work in CS mode before.
Caused all kinds of boot problems for me until I figured it out.
If that doesnt work, just try booting with only 1 hdd in (the one that has windows installed to it).
Enter the bios, and save and exit, then boot into windows.
Next, unplug the power from the power supply at the back, and press the power button on the case (to release any built up electricity in the mobo;s capacitors).
Install the other hdd, re-attach the power cable, boot into bios, save and exit, and boot into windows.
If that doesnt work, then you might have a hardware failure, like the hdd, cpu, or memory, or psu.
How is the power grid there where you moved?
Brown outs?
Dirty power?
Do you have a GOOD ups attached to the wall socket?
Yesterday I messed with my Wireless board and it was indeed loose (no loose enough that I could notice, but after removing and putting it back and activating it again, I had no more BSoDs).
So I marked dawvee's answer as the solution, since it solves that particular problem.
That said, I'm still trying to figure out the boot thing and I will try some other things tonight. Thanks everyone for the opinions, you've all been very helpful. :)
avatar
Falci: Yesterday I messed with my Wireless board and it was indeed loose (no loose enough that I could notice, but after removing and putting it back and activating it again, I had no more BSoDs).
So I marked dawvee's answer as the solution, since it solves that particular problem.
That said, I'm still trying to figure out the boot thing and I will try some other things tonight. Thanks everyone for the opinions, you've all been very helpful. :)

Awesome, glad to hear you got the BSoD thing sorted, and with no harm done. :-)