BSOD on brand new system

Tazor · 2nd May 2012, 8:27 PM

I've just put together a new build and the system kept blue screening as the windows logo was appearing. I tried defaulting bios, and so fourth but there wasn't a whole lot I could do considering there is nothing installed on the system. I ran a safe mode install and the system crashed on the "disk" file. Does this mean there is an issue with the copy of windows I am using? Any help would be much appreciated, I'll see if I can copy down the code that comes up.

Cheers

Tazor

garetz · 2nd May 2012, 9:19 PM

I've never heard of an install causing problems unless you are doing a upgrade from a previous OS. More than likely its hardware related. Unless of course the install you are using is not an official disk, or an iso.

Tazor · 2nd May 2012, 9:38 PM

Quote:

Originally Posted by garetz

I've never heard of an install causing problems unless you are doing a upgrade from a previous OS. More than likely its hardware related. Unless of course the install you are using is not an official disk, or an iso.

It's an OEM copy I've had for quite a while now, never had any issues with them before. What components could be faulty? What would cause BSOD? RAM?

Creekin · 2nd May 2012, 9:41 PM

is this the same rig we are talkin about the pump?

could be heat related if ur loops dead
or uve killed it installing a block

but sounds like ram to me
are u attempting a fresh windows install from a known good cd to a known good hdd?

Tazor · 2nd May 2012, 9:43 PM

Quote:

Originally Posted by Creekin

is this the same rig we are talkin about the pump?

could be heat related if ur loops dead
or uve killed it installing a block

but sounds like ram to me
are u attempting a fresh windows install from a known good cd to a known good hdd?

Different system, brand new. I've used both OEM disks about 3 times, never had an issue. I have no way of telling whether the HDD is any good, I can't really tell... The loop in my other system is working great, just has a noisy pump.

Creekin · 2nd May 2012, 9:51 PM

download seagate seatools to test the hdds..
u can get a bootable version on a compilation disc like UBCD
or the win version to test it on another pc..

have u tried with 1 stick of ram at a time or diff ram?
also try diff psu
first 2 things to do everytime it gets weird

Tazor · 2nd May 2012, 9:55 PM

Quote:

Originally Posted by Creekin

download seagate seatools to test the hdds..
u can get a bootable version on a compilation disc like UBCD
or the win version to test it on another pc..

have u tried with 1 stick of ram at a time or diff ram?
also try diff psu
first 2 things to do everytime it gets weird

I'm going to do one stick at a time and swap them out with my main rig's ram. will also do PSU, hopefully one of these will work, cheers Creekin.

O-B-E-L-I-X · 2nd May 2012, 11:05 PM

Bent pins in the CPU socket...faulty PSU?

joshpond · 3rd May 2012, 5:42 AM

What are the items?

Try changing the mem or running memtest as well first.

Josh

plasticbastard · 3rd May 2012, 5:52 AM

Use basic troubleshooting steps, strip out everything but the bare essentials and add them back in one at a time to see which is causing the BSOD. I'd start with just one stick of RAM and test each RAM stick individually, then add them in together one at a time.

2nd May 2012, 8:27 PM	#1
Tazor Member Join Date: May 2010 Location: Research, 3095 Posts: 881	BSOD on brand new system I've just put together a new build and the system kept blue screening as the windows logo was appearing. I tried defaulting bios, and so fourth but there wasn't a whole lot I could do considering there is nothing installed on the system. I ran a safe mode install and the system crashed on the "disk" file. Does this mean there is an issue with the copy of windows I am using? Any help would be much appreciated, I'll see if I can copy down the code that comes up. Cheers Tazor __________________ My Rig \| Cubitek Mini Tank \| i7 3770k \| EVGA Stinger \| GPU Coming Soon \| 2 x OCZ Vertex 4 128Gb & 2Tb \| 16Gb GSkill DDR3 \| Corsair H90 \| SteelSeries Sensei \| Razer Black Widow Ultimate \| Audio-Technica M50's \| Cerwin Vega XLS-6's \| Yamaha RX-V481 Reciever \| 2 x Dell U2311H and a U2913 Coming Soon\| Laptop: Razer Blade R2 \| i7 3832QM \| GTX660m 2Gb \| 8Gb RAM \| 500Gb HDD w/ 64Gb cache SSD \| Sexiness \| Project Goliath - Cubitek Mini Tank Gaming Rig

2nd May 2012, 9:19 PM	#2
garetz Member Join Date: Aug 2002 Location: 2217 Posts: 544	I've never heard of an install causing problems unless you are doing a upgrade from a previous OS. More than likely its hardware related. Unless of course the install you are using is not an official disk, or an iso. __________________ $6995 in trades done

2nd May 2012, 11:05 PM	#8
O-B-E-L-I-X Member Join Date: Jul 2008 Location: SYD, Matraville 2036 Posts: 621	Bent pins in the CPU socket...faulty PSU? __________________ Successful Trade/Swap with: Flux, Haillion, Xinhua, evo800v, hendot, metho_man, rps, Jonbanez, stergiopilus, bjornzzz, baby_ute, slyls1, Error-prone, chronisis, spud42, bennyling , Southead, falun, Smashedcrab, finnigan, jyjf, tangcla, merlin13, Deus_Ex_Machina, hen84, Spada, pepsimax, cheozuka, colcha, rippi, OsamaBinAthlon, kenneth, tek_01, Franc, Sleepy Dude, theological

3rd May 2012, 5:42 AM	#9
joshpond Member Join Date: Aug 2011 Location: Townsville Posts: 242	What are the items? Try changing the mem or running memtest as well first. Josh __________________ PC - Overclocked for faster web browsing

3rd May 2012, 5:52 AM	#10
plasticbastard Member Join Date: Jul 2003 Location: Sector ZZ9 Plural Z Alpha Posts: 3,952	Use basic troubleshooting steps, strip out everything but the bare essentials and add them back in one at a time to see which is causing the BSOD. I'd start with just one stick of RAM and test each RAM stick individually, then add them in together one at a time.