Is My chipset or ram controller dying?

N2Gaming · Aug 9, 2008, 06:01 AM

I find it sad to say but I think my chipset or ram controller may be dying on my board and I was wondering if any one has any suggestions to try before I consider the board a hopeless cause... It all started a few months ago when I tried to fire up my pc after being turned off for a month or so... My Rig would post and try to load os and hang during the scrolling boot up screen in win xp pro x64. I tried several times to boot to os but it wouldn't . So I opened the case and saw the chipset fan looking like it wanted to turn so I gave it a push start and it has been working ever since.thenI went into the bios and crancked up the ram voltage all the way from 2.6 to 2.9 before it would boot up into windows. then I thought ok everything is going to be fine. I ran it like that for a day or so and tried turning the volts back down. I could only get it to boot @ 2.8 volts, which is the max volt limit for warranty issues on ram. then I ran memtest and prime95 and passed with flying colors for more that 24 hrs each. then just in the past couple of days I went back into bios and made a couple of static changes from auto to stock settings for volts/FSB's/Multipliers ram spds etc. Becuase the system started rebooting with a memry dump or blue screen crash. I don't know exactly what casused the crash. So I looked into the system event viewer and it says warning when I click on the warning and error I see this

Warning Remote Access

Unable to contact a DHCP server. The Automatic Private IP Address 160.219.283.34 will be assigned to dial-in clients. Clients may be unable to access resources on the network.

" I changed the ip above for the Example "

System Error Remote Access

Unable to add the interface {DEB289B8-1274-4E73-833D-4AB580BDDA97} with the Router Manager for the IP protocol. The following error occurred: Cannot complete this function.

Error System Error

Error code 000000000000003b, parameter1 00000000c0000005, parameter2 fffff8000104b87a, parameter3 fffffadfc8acc910, parameter4 0000000000000000.

When One of my other computers tries to get an ip using dhcp or i get an email the above errors happen related to dhcp error. This problem causes crashes/rebooting The very last time it crashed and past post this happened. The screen gave me a bad garbled image of black and blue boxes like what you would see in the movie the matrix. It looked cool but it wasn'

from the bios I can see that my chip-set, cpu and and pwm run at about 40'c and dfi says it's normal up to 60'c but to keep the cpu as low as possible like 30 to 35 c all my fans work and cpu fan turns on and off per set perameters. Would it hurt the mobo to adjust the chip-set voltage from 1.5 to 1.6 or 1.7?
Oh yeah before I forget My os is loaded on the 34 gig raptor with 3 partitions. Drive C is 10 gig, Drive E is 10 gig and drive F is 14 gig. the 180 is file storage only. most all of my system folders are on Drive E and it's full so I'm wondering if that could have something to do with any thing. Any and all advice welcome thnx Tony

Grace · Aug 9, 2008, 01:19 PM

Hello Tony,

Despite your thorough explanation, I still cannot simply guess what might be wrong with your system. There are too many possibilities. Try resetting the BIOS to Optimal settings and remove all but one RAM module and see if that causes you any trouble. Also, have you tried to perform a clean re-install of the OS? It could a software conflict causing you all these trouble.

N2Gaming · Aug 9, 2008, 05:17 PM

Oh yeah one of the first things I tried bofore making any voltage changes was to remove one stick of ram! Then it would boot right into windows. I believe this is how I discovered the chipset fan not turning. Does this tell you any thing prevelent?

**temeteus82** · Aug 9, 2008, 05:27 PM

Quote:

Originally Posted by N2Gaming

Oh yeah one of the first things I tried bofore making any voltage changes was to remove one stick of ram! Then it would boot right into windows. I believe this is how I discovered the chipset fan not turning. Does this tell you any thing prevelent?

You have fixed the chipset fan issue? I had in the past same issue and I had to change the chipset cooler. Since the chipset was overheating and that caused problems...

Grace · Aug 9, 2008, 07:19 PM

Quote:

Originally Posted by N2Gaming

Oh yeah one of the first things I tried bofore making any voltage changes was to remove one stick of ram! Then it would boot right into windows. I believe this is how I discovered the chipset fan not turning. Does this tell you any thing prevelent?

I think it's the motherboard which is causing you problems...but then again the memory controller is inside your CPU. It's tricky.

N2Gaming · Aug 9, 2008, 08:34 PM

First off thnx to both of you! yeah... I think chipset is the culprit... I reset bios to optimized settings and it still would not load os with 2 gig. If I only use one gig it boots just fine. Hm do you think it's worth having it repaired or would repairs possibly cause more problems ??? I have another system so down time is not an issue...

Grace · Aug 10, 2008, 01:35 AM

Quote:

Originally Posted by N2Gaming

First off thnx to both of you! yeah... I think chipset is the culprit... I reset bios to optimized settings and it still would not load os with 2 gig. If I only use one gig it boots just fine. Hm do you think it's worth having it repaired or would repairs possibly cause more problems ??? I have another system so down time is not an issue...

Another idea since it boots when you remove one RAM module. Remove the other module this time and try again. Perhaps the RAM module which you are removing is the one causing the problems.

As I said, it sounds likely for the motherboard to be the culprit but the memory controller is inside the CPU. It is hard to say which may have gone wrong. Either way, repairing the CPU is impossible and repairing the motherboard is not worth the shot even if it is repairable to begin with.

H3X4D3C1M4L · Aug 15, 2008, 05:22 PM

Quote:

Originally Posted by Grace

As I said, it sounds likely for the motherboard to be the culprit but the memory controller is inside the CPU.

I tend to just think of the memory subsystem as a whole rather than as the sum of its parts. It actually makes it easier if the memory controller is on the CPU to diagnose problems I think. Realistically if the memory or the controller itself was the problem I think there would be more random errors and the machine wouldn't post so steadily. The fact that taking out a stick of RAM helps the stability of the machine is probably more of a coincidence than anything.

The chipset is still responsible for providing the processor with access to the PCI(e) bus, all the connected peripherals (including the disk controllers), and most everything else. To me it sounds like the chipset is probably just overheating. I would go out and buy a chipset heatsink & fan unit and try and see if that helps it first, before tossing the motherboard or looking to just upgrade the entire thing. No need to spend a ton of money... just get something beefy and make sure you apply the thermal paste properly. To make extra sure aim a case fan right at the chipset and any other areas on the motherboard that have heatsinks and see what happens, then go from there.

Aug 9, 2008, 06:01 AM	#1
N2Gaming DriverHeaven Newbie Join Date: Aug 2008 Posts: 5 Rep Power: 0	Is My chipset or ram controller dying? I find it sad to say but I think my chipset or ram controller may be dying on my board and I was wondering if any one has any suggestions to try before I consider the board a hopeless cause... It all started a few months ago when I tried to fire up my pc after being turned off for a month or so... My Rig would post and try to load os and hang during the scrolling boot up screen in win xp pro x64. I tried several times to boot to os but it wouldn't . So I opened the case and saw the chipset fan looking like it wanted to turn so I gave it a push start and it has been working ever since.thenI went into the bios and crancked up the ram voltage all the way from 2.6 to 2.9 before it would boot up into windows. then I thought ok everything is going to be fine. I ran it like that for a day or so and tried turning the volts back down. I could only get it to boot @ 2.8 volts, which is the max volt limit for warranty issues on ram. then I ran memtest and prime95 and passed with flying colors for more that 24 hrs each. then just in the past couple of days I went back into bios and made a couple of static changes from auto to stock settings for volts/FSB's/Multipliers ram spds etc. Becuase the system started rebooting with a memry dump or blue screen crash. I don't know exactly what casused the crash. So I looked into the system event viewer and it says warning when I click on the warning and error I see this Warning Remote Access Unable to contact a DHCP server. The Automatic Private IP Address 160.219.283.34 will be assigned to dial-in clients. Clients may be unable to access resources on the network. " I changed the ip above for the Example " System Error Remote Access Unable to add the interface {DEB289B8-1274-4E73-833D-4AB580BDDA97} with the Router Manager for the IP protocol. The following error occurred: Cannot complete this function. Error System Error Error code 000000000000003b, parameter1 00000000c0000005, parameter2 fffff8000104b87a, parameter3 fffffadfc8acc910, parameter4 0000000000000000. When One of my other computers tries to get an ip using dhcp or i get an email the above errors happen related to dhcp error. This problem causes crashes/rebooting The very last time it crashed and past post this happened. The screen gave me a bad garbled image of black and blue boxes like what you would see in the movie the matrix. It looked cool but it wasn' from the bios I can see that my chip-set, cpu and and pwm run at about 40'c and dfi says it's normal up to 60'c but to keep the cpu as low as possible like 30 to 35 c all my fans work and cpu fan turns on and off per set perameters. Would it hurt the mobo to adjust the chip-set voltage from 1.5 to 1.6 or 1.7? Oh yeah before I forget My os is loaded on the 34 gig raptor with 3 partitions. Drive C is 10 gig, Drive E is 10 gig and drive F is 14 gig. the 180 is file storage only. most all of my system folders are on Drive E and it's full so I'm wondering if that could have something to do with any thing. Any and all advice welcome thnx Tony __________________ [COLOR=cyan]DFI LANPARTY NF4 SLI-DR BIOS VER: 6.00PG[/COLOR] [COLOR=cyan]AMD 3500+ VENICE W/ZALMAN 9700 LED[/COLOR] [COLOR=cyan]2X 1024 OCZ ELD PLATNUM PC3200[/COLOR] [COLOR=cyan]WIN XP PRO X64 SP1[/COLOR] [COLOR=cyan]WD RAPTOR SATA 36GB NO RAID[/COLOR] [COLOR=cyan]WD SATA 180 GB 7200RPM NO RAID[/COLOR] [COLOR=cyan]WINFAST GEFORCE PX6600TD PCIe[/COLOR] [COLOR=cyan]SMALL MID TOWER W/ENERMAX 600W SLI READY EG701AX-VE(W)[/COLOR] [COLOR=cyan]EMPREX 16X DVD RW/WR[/COLOR] [COLOR=cyan]AND A FEW SMALL & LOUD CHASSIS FANS[/COLOR] Last edited by Grace; Aug 9, 2008 at 01:20 PM.

Aug 9, 2008, 05:17 PM	Thread Starter #3
N2Gaming DriverHeaven Newbie Join Date: Aug 2008 Posts: 5 Rep Power: 0	Oh yeah one of the first things I tried bofore making any voltage changes was to remove one stick of ram! Then it would boot right into windows. I believe this is how I discovered the chipset fan not turning. Does this tell you any thing prevelent? __________________ [COLOR=cyan]DFI LANPARTY NF4 SLI-DR BIOS VER: 6.00PG[/COLOR] [COLOR=cyan]AMD 3500+ VENICE W/ZALMAN 9700 LED[/COLOR] [COLOR=cyan]2X 1024 OCZ ELD PLATNUM PC3200[/COLOR] [COLOR=cyan]WIN XP PRO X64 SP1[/COLOR] [COLOR=cyan]WD RAPTOR SATA 36GB NO RAID[/COLOR] [COLOR=cyan]WD SATA 180 GB 7200RPM NO RAID[/COLOR] [COLOR=cyan]WINFAST GEFORCE PX6600TD PCIe[/COLOR] [COLOR=cyan]SMALL MID TOWER W/ENERMAX 600W SLI READY EG701AX-VE(W)[/COLOR] [COLOR=cyan]EMPREX 16X DVD RW/WR[/COLOR] [COLOR=cyan]AND A FEW SMALL & LOUD CHASSIS FANS[/COLOR] Last edited by N2Gaming; Aug 9, 2008 at 05:23 PM.

Aug 9, 2008, 08:34 PM	Thread Starter #6
N2Gaming DriverHeaven Newbie Join Date: Aug 2008 Posts: 5 Rep Power: 0	First off thnx to both of you! yeah... I think chipset is the culprit... I reset bios to optimized settings and it still would not load os with 2 gig. If I only use one gig it boots just fine. Hm do you think it's worth having it repaired or would repairs possibly cause more problems ??? I have another system so down time is not an issue... __________________ [COLOR=cyan]DFI LANPARTY NF4 SLI-DR BIOS VER: 6.00PG[/COLOR] [COLOR=cyan]AMD 3500+ VENICE W/ZALMAN 9700 LED[/COLOR] [COLOR=cyan]2X 1024 OCZ ELD PLATNUM PC3200[/COLOR] [COLOR=cyan]WIN XP PRO X64 SP1[/COLOR] [COLOR=cyan]WD RAPTOR SATA 36GB NO RAID[/COLOR] [COLOR=cyan]WD SATA 180 GB 7200RPM NO RAID[/COLOR] [COLOR=cyan]WINFAST GEFORCE PX6600TD PCIe[/COLOR] [COLOR=cyan]SMALL MID TOWER W/ENERMAX 600W SLI READY EG701AX-VE(W)[/COLOR] [COLOR=cyan]EMPREX 16X DVD RW/WR[/COLOR] [COLOR=cyan]AND A FEW SMALL & LOUD CHASSIS FANS[/COLOR]

Aug 9, 2008, 01:19 PM	#2
Grace HH's Tomboy Join Date: Nov 2005 Location: Anywhere but in my house! Posts: 776 Rep Power: 56	Hello Tony, Despite your thorough explanation, I still cannot simply guess what might be wrong with your system. There are too many possibilities. Try resetting the BIOS to Optimal settings and remove all but one RAM module and see if that causes you any trouble. Also, have you tried to perform a clean re-install of the OS? It could a software conflict causing you all these trouble.