- Joined
- Jan 12, 2002
- Location
- Goldens Bridge
I had a bad scare last nite when my WinXP-h locked up while running low demand browsing at default clock: P4-2.0A at 2 GHz, fsb 100, pci 33, Kingston pc1066 : 512 MB (Smsng chips). my DRCG is ICS 9212-13 (the fast one). Proc is cooled by waterblock. RAM was 4X and "turbo" in 1005 BIOS, running jumperless on a 1.7Vcore pintrick.
All attempts to reboot (and each effort was isolated by unplugging AC and popping out BIOS cell) met with error beeps during POST: a rapid stuttering beep for 5 sec then a continuous beep until I shut down. It was just like it could see no ram at all.
I troubleshot for 3 hrs, all the while wishing I kept a spare RIMM (I don't) to try swapping one at a time: I figgered I'd burned a RIMM.
What fixed it:
Swapping the RIMMs to the slots the CRIMMs had been in, and so moving all RDRAM from Channel A to B.
So far, all is well.
----------------------------------------------------------------------------------------
PS:
a digresssion to be skipped unless you're really curious....
Well... I am crashing Mozilla 1.3a due to the following OS error message:
********************
XPCOM:EventReceiver: mozilla.exe - Application Error.
The instruction at "0x61fc3684" referenced memory at "0x025168c4". The memory could not be "read".
Click on OK to terminate the program.
*******************
[I haven't yet learnt if the RAM address cited is consistently the same. And- this is a new build of Mozilla. It has bugs.]
---------------------------------------------------------------------------------------
Anyone familiar with this phenomenon?
Do ya think the damage was likeliest in the MCH (i850), the DRCG, or a RIMM?
Thanks for advice/speculation, and a Happy New Year to all hardware geeks out there!
-Dean
All attempts to reboot (and each effort was isolated by unplugging AC and popping out BIOS cell) met with error beeps during POST: a rapid stuttering beep for 5 sec then a continuous beep until I shut down. It was just like it could see no ram at all.
I troubleshot for 3 hrs, all the while wishing I kept a spare RIMM (I don't) to try swapping one at a time: I figgered I'd burned a RIMM.
What fixed it:
Swapping the RIMMs to the slots the CRIMMs had been in, and so moving all RDRAM from Channel A to B.
So far, all is well.
----------------------------------------------------------------------------------------
PS:
a digresssion to be skipped unless you're really curious....
Well... I am crashing Mozilla 1.3a due to the following OS error message:
********************
XPCOM:EventReceiver: mozilla.exe - Application Error.
The instruction at "0x61fc3684" referenced memory at "0x025168c4". The memory could not be "read".
Click on OK to terminate the program.
*******************
[I haven't yet learnt if the RAM address cited is consistently the same. And- this is a new build of Mozilla. It has bugs.]
---------------------------------------------------------------------------------------
Anyone familiar with this phenomenon?
Do ya think the damage was likeliest in the MCH (i850), the DRCG, or a RIMM?
Thanks for advice/speculation, and a Happy New Year to all hardware geeks out there!
-Dean