Getting blue screen on new build

Ed · 15 Oct 2008 at 21:12

I've just put a new system together with the following OcUK components:

Gigabyte GA-EP43-DS3L Intel P43 (Socket 775) PCI-Express DDR2 Motherboard

Corsair 2GB DDR2 XMS2-6400C5 TwinX (2x1GB)

Antec Three Hundred Ultimate Gaming Case

Seagate Barracuda 7200.11 500GB SATA-II 32MB Cache - OEM (ST3500320AS)

Sony NEC Optiarc AD-5200A 20x DVD±RW IDE Dual Layer ReWriter (Black) - OEM

Akasa Rounded Ultra ATA13310066 IDE Cable (0.45m) - Black

Gigabyte SUPERB 460w PSU

Akasa SATA-2 45cm Silver Data Cable

Asus ATI Radeon HD 4850 512MB GDDR3 TV-OutDual DVIHDMI (PCI-Express) - Retail

Intel Pentium Dual-Core E5200 "LGA775 Core 2" 2.50GHz (800FSB) - Retail

It posts first time and gives me the usual "non-system disk" error. I proceed to FDISK then FORMAT the disk, pop-in the Windows CD and then begin to boot from disc.

The problem is after partitioning and formatting, it begins to copy the files across from the CD but within about 3 seconds it just either freezes or more often, blue screens with a variety of notifications, most common though is "non_paged" something or other. Memory I presume?!

Is there anything in the above component list that doesn't agree with the others?

I've tried pulling a memory stick, then swapping, even tried non dual-channel but the problem is the same.

I haven't tried pulling sticks from this machine and trying them yet but I wondered if anyone can spot something obvious. I've had a few stubborn machines before but this one is plain refusing to accept an operating system, even Ubuntu. It simply blue screens a few seconds after copying files.

Help appreciated!!!

Snograt · 15 Oct 2008 at 21:17

Page_fault_in_non-paged_area - one of my favourites :/

TRY pulling sticks! Try with just one RAM module in.

RJC · 15 Oct 2008 at 21:21

Run mem test on the memory see if any errors occur.
Download diagnostic tools from Segate and scheck hard drive for errors, you might have a faulty component.

newbe5 · 15 Oct 2008 at 21:28

This is going to sound absolutely stupid, but I had this same issue a while ago with the wifes PC. Eventually I fixed it by disabling the onboard LAN adapter in the BIOS. Eventually I ran a BIOS update and the problem went away.

I'm not suggesting this is your problem, especially with a brand new board, but just hilighting that it might not be the RAM (although either the RAM or the MOBO are the most obvious culprits).

Snograt · 15 Oct 2008 at 21:46

Good point, that. Just because an error points to a memory issue, it isn't necessarily the memory at fault.

Make sure everything in the BIOS is set to default and have no unnecessary peripherals plugged in.

acharris · 15 Oct 2008 at 23:26

Definately sounds like a RAM / HDD issue. To know for sure, try getting hold of a live linux boot CD like Knoppix, as this boots from the CD and then uses the RAM to store the linux OS. I have found my memory errors 95% of the time with this, as it uses a lot of the ram to run and if it is an error, then it crashes that.

If this is runs fine, then it is HDD or some setup with the sata drivers/raid setup if you are using a RAID that is. Could be something else like said above, but in my experience you will not get an memory error blue screen if it is a on-board ethernet or some other peripheral.

dr. sarf · 15 Oct 2008 at 23:41

What settings have you configured your RAM to in your BIOS?

Ed · 16 Oct 2008 at 19:05

Thanks for all the advice.

Turns out one of the sticks were really unstable so I guess it needs to go back. The other stick was fine and let me install Vista, add games etc.

keogh · 16 Oct 2008 at 19:48

Try that other stick on its own, if it works fine, chances are you are not getting enough voltage to your sticks, you should always manually set the timings and ram voltage in the BIOS to what it suggests for that ram (usually on a sticker on the label).