Memory acted up again, but now it won't even POST

archcommus

Diamond Member
Sep 14, 2003
8,115
0
76
As some of you may remember, I have had some problems with one stick of my memory over the past seven months or so. For those of you that did not read those threads, here are the cliffs:

- Used to have one 512 MB PNY stick and one 512 MB Kingmax stick
- Replaced both with the Corsair memory in my sig
- A few times I experienced issues where things would get very slow and lockup; this only happened a few times though over the course of last July until today.
- Whenever this would happen, I would reboot, and everything, especially bootup, would be incredibly slow. Myself and people here on the forums attributed this problem to my memory. However, simply removing the one stick that produced Memtest errors and then putting it back in fixed the problem.
- I eventually decided that I'd RMA both sticks since they are a pair and have a lifetime warranty. However, since it mostly runs fine, and since I'll be upgrading in a couple months anyway, I decided to wait to do it until I do the upgrade.

So that's before. Fast forward to today. I was copying some multi-GB files and it froze when I went to open IE. I rebooted, and it stayed on the first screen of bootup for well over a minute, and then hung at "Verifying DMI Pool Data" for what seemed like forever. So, I did what I did before: removed the second stick. Upon rebooting, instead of fixing it like in the past, it hung at "Detecting IDE devices." Completely froze. It couldn't get any farther than counting the memory and CPU speed. This was something I had never seen before. It would happen with either stick in or with both sticks in. So I cleared CMOS, and put in just the stick that produces no Memtest errors, and booted it up. It booted okay, detected the IDE devices and all that, and proceeded to the desktop at a normal speed. However, I knew that the memory was set to SPD, which is 200 MHz, and the CPU was at stock, which is 133 MHz, and so I expected instability. So I rebooted and put the CPU back to 200x20 - no POST. Put the CPU at stock, 133x13, and the memory frequency at 100% - no POST. Now no matter what setting I try, it won't POST.

First question, would you agree the original problem (freezing, being extremely slow upon reboot) was due to the memory? Or possibly something else?

Second question, why do you think removing the second stick when it was slow caused it to freeze at "Detecting IDE devices"?

Third question, after resetting CMOS fixed the problem, what do you think is causing it to not POST now? Simply my board being picky? Or the memory somehow? Or what?
 

Chesebert

Golden Member
Oct 16, 2001
1,013
15
81
sounds like damagd hardware. memroy is probably fine. (memtest passed) could be your mobo, IDE controller
1. Does it work with only CPU, 1 stick RAM and video?
2. Does it work with (1) + CD rom
3. Does it work with (1) + HD (use PATA connector from the CDrom)

if you have a memory problem, you will get alot more errors. Memory is a really simple device, read/store, nothing more. if memtest is ok then your mem is ok. Try PCI IDE or SATA controller to see if that fixes your problem. You could also have mistakenly damaged your mobo with static electricity..... GL
 

archcommus

Diamond Member
Sep 14, 2003
8,115
0
76
Well, one stick of memory produces errors in Memtest, the other does not. The few times it has locked up and been slow upon reboot over the months I have blamed on that one bad stick. However, removing it and putting it back in always fixed the problem, so I decided to wait to RMA it until this summer.

However this time, after removing the bad stick but keeping the good one, it froze when trying to detect my drives. Resetting CMOS DID in fact fix the problem, it booted up and I was able to get into Windows. Then I went into BIOS to change settings, and NOW it won't POST anymore. Everytime it doesn't POST, I power off the PSU, turn the computer back on, and the first bootup screen does show, so I don't believe the board is dead. It then says that the computer was powered off improperly and that it's now set to the "safe mode" FSB of 100 MHz. It then forces me to enter BIOS to change it. Then, after altering settings, it won't POST upon exiting BIOS.
 

Chesebert

Golden Member
Oct 16, 2001
1,013
15
81
I would say something is wrong with your mb. try a PCI IDE/STAT card. could be a bad CMOS chip (can't store (corrupted CMOS when store), only read), which could explain why default CMOS setting is ok and after change no boot.

 

archcommus

Diamond Member
Sep 14, 2003
8,115
0
76
Well, I agree your idea about a corrupted CMOS would make sense. What seems odd is that everything was fine until the the computer locked up and was slow upon reboot, and oddly enough that is the same problem we attributed to the memory months ago. Remember, I do have a stick that produces errors in Memtest, so I believe that's the cause of lockup sometimes when I'm moving big files or whatever, and the slow reboots thereafter. So how come the mobo would suddenly get messed up after a memory problem?

Plus, remember that the first time I turned it back on after resetting CMOS, it got to the desktop just fine. But after a BIOS change, no POST.
 

Chesebert

Golden Member
Oct 16, 2001
1,013
15
81
slow reboot is software problem. error moving file can be software problem, compatiblity or other issue. memtest error is hardware problem (Ram or the ram socket and compliment electronics)

I would venture to say that you have a bad mobo. Check that faulty ram of yours in another pc and let me know if memtest returns any errors.

 

archcommus

Diamond Member
Sep 14, 2003
8,115
0
76
Well, when I got home tonight, I powered it on, and like before, it forced me to go into BIOS to change settings because it was set to the "safe mode" FSB of 100 MHz. But, I changed nothing at all, and just exited the BIOS, and that time it POSTed. So right now it's running, but my FSB is set 133 MHz, and my memory is running at 200 MHz. Will that cause any adverse effects besides instability? Of course I don't intend to keep it this way forever.
 

archcommus

Diamond Member
Sep 14, 2003
8,115
0
76
Bump.

I was able to POST by not changing anything in BIOS, meaning I'm running at 133x13 right now with my memory set to 200 MHz. If this doesn't cause instability is there anything to worry about running it this way?