• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Issue with fresh built computer

J

jbou91

n00b
Joined
Nov 25, 2010
Messages
33
I'll just post the cliffs, if you want to read the whole thread (on another forum) feel free as the link will be posted below.

Cliffs:
- Built new pc
- BSOD then System32 error (won't go away until I reformatt)
- Used NEW Windows XP SP3 CD to install windows
- Ran multiple tests on HD (passed)
- Ran memtest86 (passed)
- Noticed the ram timings were faster than what they should be (then adjusted in BIOS)
- Still getting BSOD but NO system32 error (thankfully)

Here is the thread showing everything that has been done and said...

http://www.overclock.net/amd-general/871852-problem-computer-8.html
 
When you get the BSOD, what error code are you getting? Can you make it BSOD?
I read some of the posts and the newegg link. Not knowing much more, I'd say that if data on the drive is corrupting, its either a bad HD or the sata controller is flaky. I would try another hard drive AND another SATA cable. I had a drive that had a bunk sata connector, so it would pop up and disappear.
 
Also, look in the bios and check to see what the SATA options are set on. Make sure its in IDE or AHCI mode, and not RAID.
 
Oh, and if you can, try putting the ram in another system. I had a set of ram that would pass memory testing time after time. Running prime95 and AOD's stability test. The RAM ended up being the culprit, and one stick ended up going completely bad, where it wouldn't boot with that stick in. I installed windows 7 about 15 times before I ended up figuring out it was the ram. For some reason both sticks would pass memtest all day.
 
what voltage are you running the ram at?

have you done memtest with one stick at a time with 0 errors?

edit: he should still be able to run it in RAID anyway, even if he doesnt actually define them into an array.

edit2: also just to make sure, next time it bsods, put the back of your hand on the ram chips to check the temp's, if its hot enough to make you jerk your hand back, its overheating.
 
Last edited:
ckryan said:
When you get the BSOD, what error code are you getting? Can you make it BSOD?
I read some of the posts and the newegg link. Not knowing much more, I'd say that if data on the drive is corrupting, its either a bad HD or the sata controller is flaky. I would try another hard drive AND another SATA cable. I had a drive that had a bunk sata connector, so it would pop up and disappear.
Click to expand...

The BSOD goes away too fast for me to catch it. I changed the SATA cable and now the only error seems like the BSOD and no more System32 error.

ckryan said:
Oh, and if you can, try putting the ram in another system. I had a set of ram that would pass memory testing time after time. Running prime95 and AOD's stability test. The RAM ended up being the culprit, and one stick ended up going completely bad, where it wouldn't boot with that stick in. I installed windows 7 about 15 times before I ended up figuring out it was the ram. For some reason both sticks would pass memtest all day.
Click to expand...

I will do that tomorrow, I built 3 of the identical computers and this is the only one with issues. I don't want to end up crashing the HD on that though...

evanisthecoastie said:
what voltage are you running the ram at?

have you done memtest with one stick at a time with 0 errors?

edit: he should still be able to run it in RAID anyway, even if he doesnt actually define them into an array.

edit2: also just to make sure, next time it bsods, put the back of your hand on the ram chips to check the temp's, if its hot enough to make you jerk your hand back, its overheating.
Click to expand...

Honestly I don't know, what ever the factory BIOS has it set to.

Nope, only with both sticks in there.

I will do that, thank you.

--

As of now I submitted a RMA request through MSI as some people are saying the mobo is faulty since the ram and HD tested fine.
 
for the ram voltage, look inside the bios and see if it is set to auto or some other value, if its above your rams specified voltages, lower it within its specs. Ive done builds before that had it 1 volt too high, and it took me forever to find out why it kept BSODing even though the ram was testing fine every time.

the problem was just the ram overheating because of too much voltage.

I dont know the bios on your board, but for me it's jumperfree configuration
 
Well, good luck. The only reason I mentioned the BIOS SATA settings is because I was changing settings from IDE to AHCI but accidentally selected RAID. Windows BSOD'd upon booting windows, and immediately rebooting. Its worth a shot just to check the BIOS settings, maybe bump the RAM voltages and or check the settings just in case there is something wrong with the SPD (and it isn't auto setting the ram appropriately). In any event, just check out the BIOS. It might save you from a lot of time wasted.
 
hossdaddy said:
When does the bsod happen? can you update the bios?
Click to expand...

Its random, I already updated the bios.

evanisthecoastie said:
for the ram voltage, look inside the bios and see if it is set to auto or some other value, if its above your rams specified voltages, lower it within its specs. Ive done builds before that had it 1 volt too high, and it took me forever to find out why it kept BSODing even though the ram was testing fine every time.

the problem was just the ram overheating because of too much voltage.

I dont know the bios on your board, but for me it's jumperfree configuration
Click to expand...

Well the the thing is, I built 3 of these EXACT computers and this is the ONLY one that is having issues.
 
bad mobo? maybe try testing individual parts in one of the other systems to rule them out.
 
hossdaddy said:
bad mobo? maybe try testing individual parts in one of the other systems to rule them out.
Click to expand...

That's what its starting to look like... I will try the ram out tomorrow on another computer and take it from there. I already requested a RMA for the mobo just in case.
 
I think I found the issue. Upon startup I decided to keep one stick of ram in the MB and wiggle it upon start up, well what do you know... BSOD came up and System32 crashed.

I'm back on the computer now after reformatting and installing a fresh copy of XPSP3 and installed the stick of ram on the OTHER slot. Wiggled it, tapped it, no issues what so ever. I guess the MB is faulty...
 
keep in mind, touching the ram while the computer is running will short a lot of the time, at least it does for me, causing bsods.
 
I guess I lied, I just tried it again and I cannot duplicate the problem. I turned off the auto restart so I can get the BSOD error this time.
 
Works normal in the other PC..

I left it running all day and night running multiple tests of Prime95, and it hasn't BSOD... I'm willing to pay someone to help me find a solution..
 
For the BSOD error code after the system reboots, start tapping F8 until the Windows boot menu comes up. Towards the bottom of the screen is an option to not restart
on error. Arrow down to highlight it and press Enter. Then if the BSOD
appears, it will (should) stay there until you power off
 
Basalt said:
For the BSOD error code after the system reboots, start tapping F8 until the Windows boot menu comes up. Towards the bottom of the screen is an option to not restart
on error. Arrow down to highlight it and press Enter. Then if the BSOD
appears, it will (should) stay there until you power off
Click to expand...

Yes I turned that off already, but now the BSOD error is not happening. I'm not sure what the hell is causing it.
 
jbou91 said:
Yes I turned that off already, but now the BSOD error is not happening. I'm not sure what the hell is causing it.
Click to expand...

I wonder if it's possible something may have been shorting your mobo. Probably not.

Since the components test out in another board and you've started an RMA, your better off not risking your other components before the board is swapped out.
 
Basalt said:
I wonder if it's possible something may have been shorting your mobo. Probably not.

Since the components test out in another board and you've started an RMA, your better off not risking your other components before the board is swapped out.
Click to expand...

So what do you suggest I do then? MSI has terrible customer support, I tried calling with no luck today.

My uncle has been without a computer for about 2 months now, this issue is becoming a problem.
 
ok stop the insanity and buy a gigabyte or asus board to get him up and running. Then get the board rma'd without worrying about him. Then if you get it replaced you can sell it or maybe keep it as a backup. The black friday sales have some very inexpensive boards am3 sockets from $49 with free shipping, just to give you an idea.

ASUS M4N68T-M AM3 NVIDIA Geforce 7025/nForce 630a Micro ATX $49.99 + fs

ASUS M4N68T-M V2 AM3 NVIDIA GeForce 7050PV/nForce 630a Micro ATX $49.99 + fs
BIOSTAR A880G+ AM3 AMD 880G HDMI Micro ATX AMD Motherboard $54.99 - $10 mir + fs
Foxconn M61PMP-K AM3 NVIDIA MCP61P Micro ATX AMD Motherboard $43.99 + fs
 
Last edited:
if you tested the other removable components ram cpu etc in the other systems it must be the mobo.
 
Got the new mobo today, installed it and turned on the computer. I got 3 blue screens of death upon start up, I got pictures of them. One thing though, I did NOT reformat prior to installing the new mobo, could this be the problem?

After the 3rd BSOD, windows crashed, a file from system32 was missing/corrupt upon start up.

img0374n.jpg
img0375t.jpg
img0376s.jpg
 
Yeah not reformatting might be a cause of some of those issues.
 
Danny Bui said:
Yeah not reformatting might be a cause of some of those issues.
Click to expand...

Thanks for the reply. I will reformat, if I get BSOD again I will RMA the ram. Speaking of ram, I noticed the ram use to read around 2GB under my computer properties, now it only reads 1.75? What gives?
 
Took the computer back to my uncle and then it started having BSOD errors. I got all of them on camera so let me know what the problem is. I took one stick of ram out and it hasn't BSOD'd since. I already submitted a RMA with g.skill for the ram. I'm assuming this is the problem too?



img0378i.jpg


img0379sm.jpg


img0380m.jpg
 
BSODs like this are almost always directly or indirectly linked to the memory. Mobo may not be particularly compatible with those sticks, etc. Try some new RAM in it, the manufacturer should list what is compatible.

A crappy or dying PSU or HDD can also cause this.
 
switch the sticks out and see what happens. Or make a bootable cd with memtest 86+ and have it in the drive on boot up and it will run and test the ram. You can run it with one or both sticks in.

My guess is you have a bad stick of ram. Wait, didn't you say you ran memtest in your op?
 
hossdaddy said:
switch the sticks out and see what happens. Or make a bootable cd with memtest 86+ and have it in the drive on boot up and it will run and test the ram. You can run it with one or both sticks in.

My guess is you have a bad stick of ram. Wait, didn't you say you ran memtest in your op?
Click to expand...

Well, I just got a phone call from my uncle and he said system32 crashed again.

I ram memtest already and it passed.

I submitted an RMA with G.Skill, I will send out the ram... Why the hell am I getting so many problems with this computer?
 
I believe the power supply may be an issue. I had one case with generic power supply that caused instability and would cause data to go missing on a hard drive. Probably became so corrupted with failed writes with fluctuating power.
 
You must log in or register to reply here.
Back
Top