19 replies to this topic

[Klaxon]

hi all. i recently took the plunge and built my first computer and i am having a couple of issues! hurruh!

the first one is that the fan on my psu doesn't spin. ever. im already working on sending it back to the seller on amazon after the christmas post rush here in the uk has passed. im hoping using in the mean time wont cause any problems as long as i dont leave my computer on over night or when i am at work (as i did with my old one). my psu is a 750 watt corsair tx series.

the second, more worrying one is the bluescreens. each time i start up the computer it will boot to windows seemingly fine, then within the first few minutes of being on it will bluescreen, crash, restart and then run fine for as long as i use it. i am wondering if this could be caused by the psu fan issue or (hopefully not) something more sinester.

i copied some error reports from the bluescreens which i got after the the computer restarted..

----------------------------

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000003452
BCP2: 0000000004497000
BCP3: FFFFF70001085500
BCP4: 0000000000000080
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\121712-26800-01.dmp
C:\Users\Richard\AppData\Local\Temp\WER-36192-0.sysdata.xml
--------------------------

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000099
BCP2: 0000000000181867
BCP3: 0000000000000002
BCP4: 000000000016ECB1
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\121912-23509-01.dmp
C:\Users\Richard\AppData\Local\Temp\WER-32619-0.sysdata.xml

---------------------------

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF800030E4208
BCP3: FFFFF880090E2880
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\122012-23290-01.dmp
C:\Users\Richard\AppData\Local\Temp\WER-33493-0.sysdata.xml

--------------------------

my specs are:
gigabyte sky-am3+ 970A-DS3 fx3.1 motherboard
AMD phenom II x4 965 black edition (3.4Ghz) with the stock fan
EVGA geforce gtx 570
750 corsair tx series power supply
2x 4GB corsair vengence ram (in duel channel mode)
2TB WD caviar green hard drive

i used an anti static wrist strap when building it, built it in a room with a tile floor and treated the parts with all the due care.

i figured the battletech crowd are a slightly older and more tech savvy group then your average gaming community so i thought this might be an ideal place to ask for advice. if anyone can offer any advice i will build several churches in your honour! (note: not a legally binding agreement)

happy hunting!

[Gremlich Johns]

Did you plug the CPU heatsink fan into the proper plug on the mobo? the one that usually says "cpu fan"?

Make sure!

[HitmannD]

Make sure the fan is plugged into the pins on the motherboard and nothing is obstructing the fan from spinning. If it is, try a different set of fan pins on the motherboard.

Take it from me, I've built hundreds of computers in my life. Don't run that CPU without the heat sink & fan. In fact most motherboards have a POST error (that can be turned off) that prevents you from booting up when your CPU fan is non functional.

If you get any sort of load on that thing, its going to shut down without warning when it heats up past ~100 degrees, best case scenario...

Worst case scenario, you have a faulty CPU temp sensor, and then really bad things happen when it overheats without a fail-safe mechanism.

You could possibly under-clock the CPU to get it to run without a fan & heatsink, but I would defiantly not recommend it.

Edited by HitmannD, 20 December 2012 - 06:26 PM.

[Vexgrave Lars]

http://www.newegg.co...N82E16817139006 YES?

PSU fan is either bad or unplugged/disconnected within the PSU casing, on a long shot. I cant see it, but if your feeling really adventurous there are usually 4 screws, take it out of the computer case,and in a dry safe place place (no soda cans nearby) remove the screws and see if the fan is soldered in or plugged in. If neither or there's a busted wire, then there you go.

Either send it back, solder the wire or get a new fan.

If there's a warranty sticker, DON'T DO ANY of that, send it back, get another one.

The BSODs could be a result of the issue with the fan (bad PSU?? I dunno) undervolt, bad rail, and on, and on or any one of 10000 other issues.
You haven't posted enough info.
Richard, What's in these files is probably the road map to the discovery of your first step in finding out what is wrong.
C:\Windows\Minidump\122012-23290-01.dmp
C:\Users\Richard\AppData\Local\Temp\WER-33493-0.sysdata.xml

Look in the files and look for the code that coincides with the failure.
then your best bet is to google the code, read a lot and go from there.
Lots of hardware diags out there, like Sandra for instance, get the PSU issue handled, and start lookin up your errors.
If you want to post the contents of the XML file or the Dmp.. we can all look.
Doesn't mean the answer will be easy.Do not buy a reg fixer or anything like that.

Are all your drivers up to date is an easy one and go with NV reference driver rather than the manufacturer.
Make certain the sound driver is UTD as well.

I spose that what I'd start with.

[Sir Roland MXIII]

Vexgrave Lars, on 20 December 2012 - 07:40 PM, said:

http://www.newegg.co...N82E16817139006 YES?

PSU fan is either bad or unplugged/disconnected within the PSU casing, on a long shot. I cant see it, but if your feeling really adventurous there are usually 4 screws, take it out of the computer case,and in a dry safe place place (no soda cans nearby) remove the screws and see if the fan is soldered in or plugged in. If neither or there's a busted wire, then there you go.

Either send it back, solder the wire or get a new fan.

If there's a warranty sticker, DON'T DO ANY of that, send it back, get another one.

The BSODs could be a result of the issue with the fan (bad PSU?? I dunno) undervolt, bad rail, and on, and on or any one of 10000 other issues.
You haven't posted enough info.
Richard, What's in these files is probably the road map to the discovery of your first step in finding out what is wrong.
C:\Windows\Minidump\122012-23290-01.dmp
C:\Users\Richard\AppData\Local\Temp\WER-33493-0.sysdata.xml

Look in the files and look for the code that coincides with the failure.
then your best bet is to google the code, read a lot and go from there.
Lots of hardware diags out there, like Sandra for instance, get the PSU issue handled, and start lookin up your errors.
If you want to post the contents of the XML file or the Dmp.. we can all look.
Doesn't mean the answer will be easy.Do not buy a reg fixer or anything like that.

Are all your drivers up to date is an easy one and go with NV reference driver rather than the manufacturer.
Make certain the sound driver is UTD as well.

I spose that what I'd start with.

All extremely solid advice. Ignore the other two, not sure how in the world they read CPU fan when you clearly said PSU fan.

[Barbaric Soul]

Sir Roland MXIII, on 20 December 2012 - 09:52 PM, said:

All extremely solid advice. Ignore the other two, not sure how in the world they read CPU fan when you clearly said PSU fan.

agreed, follow Vex's advise and report back to us.

[Sen]

I have an overclocked 3930k with dual 7950s. My PSU fan never spins either.

Computer draws about 6-700Watts according to my monitor. . PSU is rated for 1250. . it just never gets hot enough to need it. Are you SURE this is a defect and not just the way the PSU is designed?

https://www.overcloc...ad.php?t=692399

As to your 2nd problem, it COULD indicate a faulty PSU. . . but it could also be a driver issue. I've seen bad PSUs, and generally the behavior I've observed is things like . . pressing reset button causes computer to hang at post until you completely power it down and back on, taking multiple tries to get into windows. . .

Granted, once it was in it was usually fine, so again you COULD have a bad PSU [is it modular? are you SURE every power connecter is seated properly? both motherboard power cables plugged in, etc?] Corsair just generally has a REALLY good rep for quality.

Getting a snapshot of the actual BSOD screen with the error listed would help lock it down.

Edited by Sen, 21 December 2012 - 06:52 AM.

[Vexgrave Lars]

Sen, on 21 December 2012 - 06:50 AM, said:

I have an overclocked 3930k with dual 7950s. My PSU fan never spins either.

Computer draws about 6-700Watts according to my monitor. . PSU is rated for 1250. . it just never gets hot enough to need it. Are you SURE this is a defect and not just the way the PSU is designed?

https://www.overcloc...ad.php?t=692399

As to your 2nd problem, it COULD indicate a faulty PSU. . . but it could also be a driver issue. I've seen bad PSUs, and generally the behavior I've observed is things like . . pressing reset button causes computer to hang at post until you completely power it down and back on, taking multiple tries to get into windows. . .

Granted, once it was in it was usually fine, so again you COULD have a bad PSU [is it modular? are you SURE every power connecter is seated properly? both motherboard power cables plugged in, etc?] Corsair just generally has a REALLY good rep for quality.

Getting a snapshot of the actual BSOD screen with the error listed would help lock it down.

Sen might be right about the PSU, it may only crank the fan IF it gets hot.

Easy way to test since its winter.. get a hair dryer.. blow hot air on the CASE of the PSU.. NOT ALOT! just get it warm.. then start it up.

If the fan starts on its own.. its a power feature.. if not.. well defect/replace it.

[Klaxon]

hi all, thanks for your replies, even the first two guys who diddnt quite get it :-p


a couple of follow up questions about the help i have gotten so far

is it safe to open the files you mentioned (e.g. C:\Windows\Minidump\121712-26800-01.dmp
C:\Users\Richard\AppData\Local\Temp\WER-36192-0.sysdata.xml) in notepad? as it asks me what program to use to run them. im guessing it probably is but i would feel better knowing for certain.

also how would i go about getting a snapshot of the bluescreen? do you mean like a screencapture? as i would have thought the print screen button wouldnt work and the screencap wouldnt be carried over after the restart anyway.

also thanks for the advice on testing the psu, but i am pretty sure the fan is broken and i dont really want to mess with it as it is under warrenty. i get that corsair have a good rep (hence why i chose them) but with the parts i have and the two case fans i would think the computer would be using at least half the capacity of the psu while gaming which im guessing would cause it to spin. also sometimes when i look at it at times i think it should be spinning it is making these very small jerking movements as if it is trying to spin (there is definately nothing from the outside interrupting the movement of the fan).

also if anyone is interested you guys are doing much better then the one reply on neoseeker forums who basicly told me i should have gotten an intel cpu xD

Edited by Klaxon, 21 December 2012 - 10:05 AM.

[Barbaric Soul]

Klaxon, on 21 December 2012 - 10:04 AM, said:

also how would i go about getting a snapshot of the bluescreen? do you mean like a screencapture? as i would have thought the print screen button wouldnt work and the screencap wouldnt be carried over after the restart anyway.

camera phone, take a picture of your monitor, upload it to the internet and post a link here

[Sen]

or at a bare minimum write down what it says. common examples are:

http://www.mytechgui...olution-part-i/

Things like that. Depending on the fault being thrown, might be able to pin it down for ya a little bit.

While I'm thinking about it. . . and I have NO CLUE if this pertains to you, I"m just throwing it out there:

Did you setup everything manually in BIOS? Sometimes you have to manually setup your ram speed/timings/voltage, etc. I know my ram is rated for 1.5v 9-10-9-28, and my board auto detects at 1.65v 11-11-11!

And just to get it out of the way, AMD doesn't have anything like intel's LLC, right? I'm almost positive they don't, but it doesn't hurt to ask.

Edited by Sen, 21 December 2012 - 12:24 PM.

[Vexgrave Lars]

Sen, on 21 December 2012 - 12:24 PM, said:

or at a bare minimum write down what it says. common examples are:

http://www.mytechgui...olution-part-i/

Things like that. Depending on the fault being thrown, might be able to pin it down for ya a little bit.

While I'm thinking about it. . . and I have NO CLUE if this pertains to you, I"m just throwing it out there:

Did you setup everything manually in BIOS? Sometimes you have to manually setup your ram speed/timings/voltage, etc. I know my ram is rated for 1.5v 9-10-9-28, and my board auto detects at 1.65v 11-11-11!

And just to get it out of the way, AMD doesn't have anything like intel's LLC, right? I'm almost positive they don't, but it doesn't hurt to ask.

Write a BSOD log file by hand.. my gosh scrooge! LOL

Cam phone.. yes open the XML in IE actually it you can Notepad works too and notepad for the Dmp file.

Nice idea about resetting the bios to defaults or default "performance".

[Gremlich Johns]

Sir Roland MXIII, on 20 December 2012 - 09:52 PM, said:

All extremely solid advice. Ignore the other two, not sure how in the world they read CPU fan when you clearly said PSU fan.

can I use the recent cataract surgery I just had as an excuse?

[Sen]

Quote

[color=#959595]Write a BSOD log file by hand.. [/color]my gosh scrooge!

I don't want a log file, I want the exception from the BSOD*BEFORE* the computer restarts. It'll at least give me a clue as to whether it's a processor or memory error If it's a processor error, it could indicate a voltage problem, which could further implicate the PSU, especially if it's 100% stable after the initial BSOD.

if it's a memory error, we know to look elsewhere.

[Sir Roland MXIII]

Gremlich Johns, on 22 December 2012 - 09:47 AM, said:

can I use the recent cataract surgery I just had as an excuse?

Oh that is absolutely forgivable, aye. (pardon the accidental pun)

Edited by Sir Roland MXIII, 22 December 2012 - 03:33 PM.

[Klaxon]

hi again all.

here is the xml file:
http://pastebin.com/hsnbcQ8V

the first three dump files:
http://pastebin.com/V0mFMa9E
http://pastebin.com/2FjVzvEU
http://pastebin.com/TLdL3aUj

and a couple of shots of one of the bluescreens:
http://imgur.com/3OQGS
http://imgur.com/ajezG

probably worth noting that the stop error is not always the same. while it is 0x0000007f on that bluescreen the most recent one was 0x0000001a

also im just trying to borrow a blank usb stick so i can run memtest86. from what i gather i need to install it on the usb stick and then boot from the usb stick to run it?

once again, really appreciate the help :-)

[Sen]

http://www.pcdoctor-...rdpress/?p=4567

relevant text:

Quote

Ah, the old Stop 07F error (a subspecies of the Blue Screen of Death). I have never seen a Stop 07F that was not hardware related, and they can be a nightmare to troubleshoot. The fact that this is a new, home-built PC that has never successfully booted to Windows makes it even more likely that the problem is hardware-related.

I've come across this error twice myself and each time the reason for it surprised me. Once it was a dodgy IDE cable and the other time a dodgy DVD drive. Each time the problems was tracked down by taking a methodical approach to the troubleshooting. Basically, assume nothing!

01a:

http://forums.cnet.c...ror-0x0000001a/

relevant text:

Quote

Stop 1A is basically a memory error (most of the time.) The causes are many, but include heat, overtaxed power supply units, a real memory failure, an outdate motherboard BIOS (new motherboards don't come with latest BIOS!), incorrect IDE cables, incorrect IDE drive jumpers, and of course "parasites."

I'd probably start by double checking cables, or disconnecting everything not 100% necessary to operation [all but 1 stick ram, unplug DVD drive, etc] If it continues after that, replace the PSU and recheck.

I have a feeling it IS the PSU at this point, but best to check the easiest [and cheapest] solutions first.

Edited by Sen, 23 December 2012 - 08:26 PM.

[Klaxon]

i know it has been a while but i thought i would post in here again just to let anyone who cares know how things turned out and to thank people who gave suggestions.

turned out the power supply was actually fine. i ran far cry 3, utorrent, windows media player, firefox and a couple of other things all at the same time and i noticed my computer was a tiny bit louder then useual. i looked in through the side and the PSU fan was spinning away. it looks like i may have just bought a PSU that was ridiculously overpowered for my needs and it only started to break a sweat when i pushed my system to the absolute limit. funny how this game diddnt do that though..

turns out i had a single bad module of ram. so i am getting that replaced by amazon.

[Catamount]

Yep, bad ram will do it, and for whatever reason it's a common component to have arrive DOA. For future reference, whenever you have instability in builds, running memtest and Prime95 before you do anything else are two great ways to spot errors. Also look out for 0x50 bluescreens (http://msdn.microsof...v=vs.85%29.aspx), which are always the most common BSOD with bad RAM. That BSOD 7F is also a very, very common memory-related BSOD. Random BSODs are also sometimes indicative of memory problems, but not always (randomly timed BSODs are a big memory giveaway as well).

With any luck you won't have to deal with this again, although I've been through more than one stick of bad RAM before.


I'm glad it's all working out for you.

Edited by Catamount, 24 January 2013 - 12:18 PM.

[Klaxon]

i think memtest86 will be my first port of call in the future. i did get 0x7f quite alot. also 0x1a and another which i cant rememer but googled and apparently it is very rare. plus a couple of others. no 0x50 though. sucks that even brands like corsair turn up DOA.

also sucks at how long amazon will take to get me a replacement. no MWO for a while it looks like :-/