• Diagnosing a problem with a new PC
    15 replies, posted
Hi. [url=http://www.facepunch.com/threads/1097131-Is-this-the-best-PC-I-can-get-for-%C2%A31500?highlight=]Facepunch recently helped me build a PC.[/url] For the first week or 2 it was great, then the new 1TB HDD stopped working and had to be replaced. Occasionally everything will freeze up (except uTorrent?) and after about 2 minutes the computer will have a BSOD (it restarts too quickly to read what the problem is) When the computer reboots, the 120GB SSD isn't detected so Windows fails to boot. Turning the computer off then on again fixes this. I thought this was quite bad but neglected to remember to ask for help for quite some time. Now, recently (in this week) it's got considerably worse - occasionally both my monitors will instantly black out, my keyboard will flash once, then after about a minute the computer will restart. First time this happened it failed to POST/beep and the screens didn't turn on, next time it made a series of beeps (I didn't think to count and it hasn't happened since). Then I had to turn the computer off then on again by the plug socket to get it to boot again. Sometimes when the computer boots it will be fine for hours, sometimes less than a minute before the screen goes black and it has to be rebooted. I've formatted several times, so it isn't Windows fault. The only culprits I can imagine are the brand new motherboard, or the brand new SSD. More like the motherboard due to the first HDD that failed completely, perhaps? none of my other HDDs have failed since though, and I have 4 plugged in. Any suggestions for what to do? Oh. Minor note, if I disable my paging file it says I've used up all my RAM when only about half of it is in use. Is that just normal? Do I just have to buy more RAM? (these are the full specs: [url]http://dl.dropbox.com/u/900111/attempt3.JPG[/url])
I'm thinking it's probably the ram. Do this and use the computer till it blue screens again recording what the error is. [url]http://pcsupport.about.com/od/windows7/ht/automatic-restart-windows-7.htm[/url]
I agree with moesislack, i'd run memtext86 for a night and see if any sticks are bad. If that isn't the problem i'd guess it's your powersupply that is giving all the errors. I wouldn't know how to check if the powersupply is bad though.
Quick thing, I managed to read a BSOD - it said a vital system process/service stopped responding unexpectedly (or something like that). Will run memtest and let you know what it says.
Memory or SSD Run memtest for a start.
Minor changes - Fixed the RAM not being in dual channel mode Moved the SSD to the correct SATA port (the one it was in before was being referred to as an "adapter" while booting Still gonna memtest tonight.
Go into bios and disable automatic boot after BSOD
This sounds like exactly what is happening to my OCZ Vertex 2 SSD. Windows hangs up and the HDD light is on full and I have to restart the computer. Then, the SSD won't even show up in BIOS.
Well, it passed memtest and chkdsk. Thought it's worth noting memtest crashed the first time I ran it, about 26 minutes in.
Okay, I fixed it by using the BIOS automatic overclock feature. I guess the RAM wasn't getting enough voltage.
Alright. 3 days later and it's starting BSODing regularly again. Same error, crucial process/thread blah terminated blah blah. What the hell do I do? My friend's just built a computer too, and it's having the same problem. The only component we share is the case. What the fuck? [editline]23rd August 2011[/editline] actually it's worse now - 2 bsod's in 20 mins there
hopeful bump
It'd be nice if you give us the stop code of the bluescreen. This can be found in the event viewer or reliability monitor.
This is all the information the reliability history will give me: Problem signature Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 2057 Extra information about the problem BCCode: 116 BCP1: FFFFFA80086614E0 BCP2: FFFFF88010641F10 BCP3: FFFFFFFFC000009A BCP4: 0000000000000004 OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1 I'm pretty sure the stop code was 0x0000004 (might be too many/few 0s). I'll confirm next BSOD.
[QUOTE=NeoDement;31942327]This is all the information the reliability history will give me: Problem signature Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 2057 Extra information about the problem BCCode: 116 BCP1: FFFFFA80086614E0 BCP2: FFFFF88010641F10 BCP3: FFFFFFFFC000009A BCP4: 0000000000000004 OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1 I'm pretty sure the stop code was 0x0000004 (might be too many/few 0s). I'll confirm next BSOD.[/QUOTE] A 32 bit longword memory location on a 64 bit machine seems a tad odd, unless you didn't count the places right (32 bit longwords are 8 hex, 64 bit quadwords are 16 hex.) The only thing I can find about that error is that it's related to incompatible drivers being loaded. If you have a 32 bit driver loaded on a 64 bit OS, that could be your problem.
It was probably 0000000000000004, as BCP4. How would I go about working out what driver it could be? All I've non-automatically installed using Windows 7 is stuff from the disk that came with the motherboard.
Sorry, you need to Log In to post a reply to this thread.