Sign in with
Sign up | Sign in
Your question

Intel DG41WV, 2 long beeps

Last response: in Motherboards
Share
November 16, 2010 1:43:49 PM

Hello, I have an intel DG41WV motherboard, Intel Core 2 Quad @2.5GHz processor. 500GB Seagate SATA HDD and another Western Digital 80GB HDD. ATI Radeon 5450HD 1GB. 3GB System RAM.

Apparently whenever I boot the computer, it makes 2 long beeps. One comes before anything is shown on the screen and the other one comes after the intel splash-screen. Intel's site only explains this as "Parity Error". I have checked everything, and all hardware is working fine.

Any ideas? Thanks!
a b å Intel
a c 715 V Motherboard
November 16, 2010 2:03:46 PM

Welcome to Tom's Forums! :) 

ref Intel® Desktop Board DG41WV http://www.intel.com/products/desktop/motherboards/Dg41...

BIOS Beep codes - http://www.intel.com/support/motherboards/desktop/sb/cs...

Do 2 things:
1. Create a Memtest86+ bootable CD/DVD {ISO/zip file} http://www.memtest.org/
2. Identify the RAM Part-Number and post the number(s) here (all of them if different); use CPUz or look at the stickers on the RAM - http://www.cpuid.com/softwares/cpu-z.html

November 17, 2010 11:19:44 AM

Hey Jaquith, thanks for the warm welcome!

I shall do as you say, however, after going to the shop and also searching a lot online, I have found that the DG41WV has this issue of 2 beeps for DDR3. I've muffled it with a piece of tape so it's extremely quiet now. However, I shall still post it for you in a while, once I get done with my drivers and programs installations :) 
Related resources
a b å Intel
a c 715 V Motherboard
November 17, 2010 11:39:10 AM

Those (2) things I listed are to test and identify the {DDR3} memory. I also want to verify that the RAM is indeed compatible with the MOBO.
November 17, 2010 2:47:17 PM

Here's the CPU-Z console



I'm pretty sure they're compatible. The Motherboard doesn't take anything other than DDR2.
November 17, 2010 3:11:49 PM

EDIT: anything other than DDR3* (not DDR2).
a b å Intel
a c 715 V Motherboard
November 17, 2010 4:21:37 PM

99P5471-002.A00LF -> KVR1333D3N9/2G CAS 9-9-9-27 @ 1.5V ; according to Kingston Tier-2 level the RAM is compatible; I bitched them out for 10 minutes about their website {CPUz->'real' part numbers.

Kingston Tested - http://www.ec.kingston.com/ecom/configurator_new/models...

I 'wish' it were that 'simple' to slap-in 'any' DDR3 and have it 'work' ; that's not the real World; memory must be selected from an Tested list per RAM Mfg 'approved' list or Certified {QVL} list per MOBO.

...That said you need to manually set the CAS to 9-9-9-27 AND...

Do 2 1 things:
1. Create a Memtest86+ bootable CD/DVD {ISO/zip file} http://www.memtest.org/
January 11, 2011 11:45:26 PM

Mao said:
Hello, I have an intel DG41WV motherboard, Intel Core 2 Quad @2.5GHz processor. 500GB Seagate SATA HDD and another Western Digital 80GB HDD. ATI Radeon 5450HD 1GB. 3GB System RAM.

Apparently whenever I boot the computer, it makes 2 long beeps. One comes before anything is shown on the screen and the other one comes after the intel splash-screen. Intel's site only explains this as "Parity Error". I have checked everything, and all hardware is working fine.

Any ideas? Thanks!

check the memory make sure the memory fit properly, or removed it and clean with an eraser then try to exchange in the memory slot, if nothing happen check the video card removed then clean with an eraser then return do it now.
January 14, 2011 4:07:44 PM

@Baadshah: Hey, thanks for that, it stopped the beeping! :) 

@Others: I haven't had much time on my hands to perform tests (I tried to make a memtest bootable USB but that didn't work so I'll try the CD next). On the other hand, Windows 7's Memory Test (on OS-choice menu) gives me a hardware error. It also says so whilst running Win7. I performed the different permutations and combinations of the RAM chips, both at the same time, in different slots, only one in, different slots, etc., but each time it gives an error. Also I've gotten the BSoD in Win7 twice and both times it says Page_Fault_Error or something like that and as far as I've learned, page faults not handled properly mean something wrong with the RAM indeed.

!