These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Out of Pod Experience

 
  • Topic is locked indefinitely.
12Next page
 

BSoD issues on newly built PC
Author
Previous Topic Next Topic
NeoShocker
The Dark Space Initiative
Scary Wormhole People
#1 - 2012-02-02 03:30:19 UTC  |  Edited by: NeoShocker
Before going the details, here are the parts ordered:

Mobo: GIGABYTE|GA-Z68XP-UD3-iSSD Z68 R
GPU: VGA EVGA|012-P3-1570-AR GTX570 R
Mem: 4Gx4|CORSAIR CMZ16GX3M4A1600C9B
CPU: CPU INTEL|CORE I7 2600K 3.4G 8M R
OS: Windows 7 home Edition 64bit
Wifi: 33-127-218 WL ADPT D-LINK|DWA-556 11N
Blu-Ray: 27-151-232 BD COMBO SAMSUNG | SH-B123L/RSBP
HD: 22-148-697 HD 1T|ST SATA6.0 32M ST31000524AS, Seagate.
PSU: 12-120-401 SURGE SUP CYBERPOWER | 850 R

I don't know what is going on to be honest. Wasn't there to surpervise my brother through downloading updates and stuff after assembling the computer. But from what he told me, he first encountered BSoD when installing wifi adapter and no longer access to internet after he updated the wifi adapter. I had to come over to see what's up. The official driver from d-link can't seem to detect the wifi, but light on the wifi was on and off.

So I checked online and saw something about another driver. Start with "A". installed it, then it detected the card and internet is restored.

So, yeah, all updated and left home, until next day he PMed me over steam that he is now getting BSoD again when he's attempting to patch Star Wars MMO, the new one.

Now he told me that he rebooted the PC and getting the BSoD, then it auto-reboots in a repeated cycle.

Any ideas? Am I convinced it might be the wifi card causing all this issues? I told him to reformat, this time not updating the wifi card.
Jada Maroo
Native Freshfood
Minmatar Republic
#2 - 2012-02-02 03:58:50 UTC  |  Edited by: Jada Maroo
The weak points in a new computer build are faulty sticks of RAM (90% of the time in my experience!) and faulty power supply. Remove a couple sticks of RAM. If it still crashes, swap them out for the other two.

Also try rewiring the power supply to spread out the power across the rails if you haven't already.

If neither of those work, then pull out single parts until it stops. If it doesn't stop, you know it's either th CPU, MP, or hard drive.
Lithalnas
Dirt 'n' Glitter
Local Is Primary
#3 - 2012-02-02 08:46:48 UTC
reinstall the OS.

From what it sounds like, you cant get to a workable desktop so your only option is to reinstall the OS. If you are concerned about the memory run Memtest from a USB during boot and see it the system can run with stress outside an OS.

https://www.facebook.com/RipSeanVileRatSmith shoot at blue for Vile Rat http://community.eveonline.com/devblog.asp?a=blog&nbid=73406
NeoShocker
The Dark Space Initiative
Scary Wormhole People
#4 - 2012-02-02 09:17:10 UTC
Well, re-installed the OS. After pulling out the WiFi card, the BSoD didn't happen, until updating windows again. So reformatted and installed the WiFI card again, so far, none.

Gonna tell my bro not to install that driver for the WiFI just incase.

Thing is, I have a bad hisory with WiFI for PC. It always causes me problems when it really shouldn't. Bought a WiFI USB a year ago, and then my PC started to **** itself for the first time and had to use system recovery.
Liam Mirren
#5 - 2012-02-02 09:30:22 UTC
As Jada replied; generally issues will be with bad memory, try increasing the voltage to your mem by a slight amount, that tends to help a lot.

Excellence is not a skill, it's an attitude.
SpaceSquirrels
#6 - 2012-02-02 14:09:55 UTC
Event logs are your friend! or post codes! Or mem test!
mogwai
Gremlin Mining and Exploration
#7 - 2012-02-02 16:17:27 UTC
D-Link have issues with Win7 from a driver point of view. Especially if using DlinkUDSTcpB driver.

Visit the d-link website and grab the newest driver from there.

If that doesnt help, your going to have to start pulling RAM sticks etc as described in other posts to see if its other hardware. Other than that, nuke the OS.
Adunh Slavy
#8 - 2012-02-02 17:28:12 UTC
Post the Error code, should be a STOP Error and then four parameters,

For example,

STOP 0x0000001A (0x00000000 0x00000000 0x00000000 0x00000005)
Occurred in somefilename.blah

Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves.  - William Pitt
NeoShocker
The Dark Space Initiative
Scary Wormhole People
#9 - 2012-02-03 05:20:15 UTC
Well, seems the new PC is in working order since the second reformat. My brother is pretty nervous on his first built PC. I will see how far he goes with his Star wars MMO patch comes up. Only thing that crashed so far is the League of Legends patcher :O

Doesnt seem to be any hardware issues, especially from the dreadful WiFi card. Must've been bad drivers and I told him not to do any driver updates for his hardware besides the gpu from now on, unless he needs to, it will be under my supervision this time!
AlleyKat
The Unwanted.
#10 - 2012-02-04 12:36:23 UTC
This, is why although I could build my own rig, I'd rather pay someone else to do it so.

If they manage to screw up the hardware, or the hardware fails on them for some reason, then it's on their head; not mine. All they have to do is either start again, or grab another component off the shelf.

Probably a million to one that there would be a failure, but for some reason the million-to-one odds tend to occur 50% of the time with me.

Glad to know I am not the only One.

AK

This space for rent.
NeoShocker
The Dark Space Initiative
Scary Wormhole People
#11 - 2012-02-05 08:41:14 UTC
AlleyKat wrote:
This, is why although I could build my own rig, I'd rather pay someone else to do it so.

If they manage to screw up the hardware, or the hardware fails on them for some reason, then it's on their head; not mine. All they have to do is either start again, or grab another component off the shelf.

Probably a million to one that there would be a failure, but for some reason the million-to-one odds tend to occur 50% of the time with me.

Glad to know I am not the only One.

AK


It may be frustrating, yes. But its a rewarding experience. I am still using my built PC, 6 years ago, and still have life about 3+ years. Very good investment. Had no problems at all except one. I fried my loyal Microsoft Sidewinder Forcefeed back Pro 2 joystick (RIP!) because I plugged the USB into the firewire port, but that is mainly the fault of the manual.

My brother built his not long after I built mines, he had issues, again it wasn't on my supervision, lol. Then the latest one, which is now. My other's brother first built PC. I was supervising him, showing him how to put it together. Did not take more than 40 minutes. Can tell he enjoyed putting it together. I did too. Its my first time being involved with the latest technologies PC. Other times, its mainly cheap ones put together.

is recent issues is apparently mainly because he was updating stuff. I did told him to update, but I quickly learn what issues I can find out, plus with some advice from the eve-o dudes in this thread. :)

As long you research the computer parts and all, its very, very simple. Its no way to fail really, unless like you said, getting a faulty part, but that can be quickly solved.
Something Random
Center for Advanced Studies
Gallente Federation
#12 - 2012-02-05 11:30:01 UTC
This has the smell on it of not updating the BIOS first thing you do... and could be actual Hardware MoBo drivers too, they were installed yes ? You didnt just take the fact it all looked ok and neglect to install them ?

Be wary of Gigabyte Alpha BIOS, theyre usually just kludges to get you going until they do it proper ... like.

If an Alpha is the latest available go for the lower latest version first as a trial.

"caught on fire a little bit, just a little."

"Delinquents, check, weirdos, check, hippies, check, pillheads, check, freaks, check, potheads, check .....gangs all here!"

I love Science, it gives me a Hadron.
AlleyKat
The Unwanted.
#13 - 2012-02-05 17:19:16 UTC
NeoShocker wrote:
Its no way to fail really, unless like you said, getting a faulty part, but that can be quickly solved.


Thinking more along the lines of static discharge, or a general 'whoops' moment.

I'd rather someone else deal with the intricacies of plugging in thousands of $ worth of hardware.

This space for rent.
NeoShocker
The Dark Space Initiative
Scary Wormhole People
#14 - 2012-02-05 22:32:53 UTC  |  Edited by: NeoShocker
Something Random wrote:
This has the smell on it of not updating the BIOS first thing you do... and could be actual Hardware MoBo drivers too, they were installed yes ? You didnt just take the fact it all looked ok and neglect to install them ?

Be wary of Gigabyte Alpha BIOS, theyre usually just kludges to get you going until they do it proper ... like.

If an Alpha is the latest available go for the lower latest version first as a trial.



Yeah, updating the BIOS is one of the first thing I go for. But when I checked the website, there were multiple version of updates (7+ if I recall), but those updates were specific to certain issues which the PC do not have. There was a warning too, that only update if it is truly necessary. I must admit, I have little experience in this specific field, but I did do BIOs update before and didn't encounter an issue before.
Andski
Science and Trade Institute
Caldari State
#15 - 2012-02-06 06:38:13 UTC
That's because the only thing that can go wrong with a BIOS update usually involves ordering a replacement EEPROM from the motherboard manufacturer, and leaves your entire system out of commission while it ships.

They're also a hilarious pain to replace!

Twitter: @EVEAndski

"It's easy to speak for the silent majority. They rarely object to what you put into their mouths."    - Abrazzar
Herzog Wolfhammer
Sigma Special Tactics Group
#16 - 2012-02-06 06:49:05 UTC
In spite of all my experience in electronics, having started with fighter jets, when I build a new computer I always take the MOBO information to a parts store and hit up the better geeks in the back for the right memory.


As far as a card going bad and now a BSOD - I have seen video cards (old Chaintechs) go down and permanently kill the MOBO.

This I suspect is not going to be an easy one, but a squeaky clean install from square one would be a good start.

Bring back DEEEEP Space!
Something Random
Center for Advanced Studies
Gallente Federation
#17 - 2012-02-06 22:34:02 UTC
NeoShocker wrote:
Something Random wrote:
This has the smell on it of not updating the BIOS first thing you do... and could be actual Hardware MoBo drivers too, they were installed yes ? You didnt just take the fact it all looked ok and neglect to install them ?

Be wary of Gigabyte Alpha BIOS, theyre usually just kludges to get you going until they do it proper ... like.

If an Alpha is the latest available go for the lower latest version first as a trial.



Yeah, updating the BIOS is one of the first thing I go for. But when I checked the website, there were multiple version of updates (7+ if I recall), but those updates were specific to certain issues which the PC do not have. There was a warning too, that only update if it is truly necessary. I must admit, I have little experience in this specific field, but I did do BIOs update before and didn't encounter an issue before.


You are right in this thinking, but only when you have a rock solid performing computer in the first place. If you have issues, start by looking at the latest BIOS, they state what issues and things are fixed but very often there are things that are not mentioned but suddenly get fixed with an update. I put it down to clean coding...*cough*... otherwise youd have to suspect some manunfacturers dont wish to admit certain problems ever existed. Right?.

BIOS - especially gigabyte are usually marked *motherboard and chip codes*_F0*incremental number*.
i.e GA535P67_F05.bin = later version than GA535P67_F04.bin

Be wary of revisioned boards, example = boards marked with a Rev_1.x below the actual board code and it should be [pointed out in the Manual too. Very often BIOS will be specific to Revision number.

As far as messing up BIOS updates goes, its VERY hard to do now in the world of Dual BIOS. Normally it only ever goes wrong during BIOS update and a power loss (so never update a BIOS on a computer with suspect PSU or random reboot problems) and as i say Dual BIOS means reverting to working original BIOS is a keypress away.

Theres also no problem working down revisions or up - the whole code gets replaced and its usual practice to set it to optimal defaults once Flash is done, then instantly on the reboot go back in and set your prefs up again (ie Boot priority etc).

Anyway, no criticisms intended just all FYI to improve peeps abilities, to my knowledge everything above is sound. The more folk can make their own comps the better in my world. Good luck.

"caught on fire a little bit, just a little."

"Delinquents, check, weirdos, check, hippies, check, pillheads, check, freaks, check, potheads, check .....gangs all here!"

I love Science, it gives me a Hadron.
NeoShocker
The Dark Space Initiative
Scary Wormhole People
#18 - 2012-02-08 01:34:59 UTC  |  Edited by: NeoShocker
Well, it was working fine, but then there are some issues. Specifically gaming wise. Star Wars MMO, it crashes after 5-20 minutes, BSoD or to desktop.

Then on Star Craft II, whenever it is downloaded, BSoD.

Originally, I thought its the GPU and/or driver issues. Tried the latest stable, and the beta drivers. I think the beta drivers made it better just a bit, but no real point if it still crashes.

But then SC2 came along, and BSoD is happening when downloading. So it must be the HD I guess?

First its Star wars, now Starcraf2, except its BSoD on downloading? (like seriously?) But I checked under chkdsk and don't see anything wrong.

I am currently checking each memory stick with memtest86+.

If anyone could please provide some tips/suggestion on how to check each individual parts? Like something similar for memtest on the HD/GPU?
Lithalnas
Dirt 'n' Glitter
Local Is Primary
#19 - 2012-02-08 07:00:46 UTC
you could do a 3D Mark vantage can stress you GPU, if it survives a run it can still be the HD or GPU.

To test HD i would try HD Tune

https://www.facebook.com/RipSeanVileRatSmith shoot at blue for Vile Rat http://community.eveonline.com/devblog.asp?a=blog&nbid=73406
Adunh Slavy
#20 - 2012-02-08 07:41:45 UTC
You keep saying you get a blue screen, but never mention what the STOP code is. What is the error message?

Check your system log for errors, source would be system or save dump, event IDs 1001, 1002, 1003 ... what's the information?

Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves.  - William Pitt
12Next page