New Build Startup

O

obxdude018

New Member
Ok I had some issues with my last board, so I forked out some cash for my next computer and here are the specs:
Asus Sabertooth 990FX Mobo
AMD Phenom 2 X6 1100T B.E.
G Skill 8GB 1333MHz, will be 16GB in a few days
MSI N570GTX Graphics Card
Corsair H70 Cooling
Patriot 32GB SSD, Operating System Only
Seagate 640GB 7200rpm HD
Blu-ray player
ThermalTake V9 BlacX case

Anyhow I using the old SSD and HD out of my previous build, I transfered the stuff over to my new build installed everything and go to boot up Windows 7 Ultimate 32bit(wish I had 64bit) it gets to the windows screen and then crashes after a few seconds, it wont progress any further than that. Windows repair does nothing to cure the problem any help would be appreciated.
 
well the windows is most likely liscenced to the old mobo so it can't be transfered, either contact ms or a new copy will be 100. also with 32 bit you'll only read 4gb's of that ram.
 
Yup, you'll need a new copy of windows with a new motherboard. And only go for 8GB. Only time you'll need more is RAM intense programs, but if its just games, 8GB is more than enough. And yes, 32bit will only read 4 GB, so you really need to get 64bit if you wanna use any more than that, which you probably do.
 
Ok, just read that on microsoft's webpage, at least I have my revue so I can access the internet, now I have an old windows xp disk that I have used before in desperate times just to get an operating system for the time being, obviously this is depending upon if the disk is still ok, even though the last time I used it, it worked fine. I ran the disk through the setup, the blue screen setup finished and it said setup is starting windows and crashes, I get the blue screen saying a problem has been detected and blah blah. Any insight on this?
 
Is this possibly a ram issue, it is constantly the same point of failure, which leads to the assumption that it is hitting the same bad sector over and over each time.
 
I ran a test with memtest, I started by running the test with both sticks connected, it didnt take long for it to find an error, so I let it finish, and ran tests on each card separately. The first card pulled no errors, ran the second one and no errors, let it start over and a error popped up. I did try removing the potential bad stick and tried to boot up the ssd and it crashed at the same point.
 
I am going to run the other card for a while to see if it pulls error codes, I will be getting my other set of ram tomorrow, so hopefully my problem is strictly ram related, it's killing me to see what this computer can do compared to my last build. Up to six errors on the bad card so far.
 
You must log in or register to reply here.
Back
Top