Random lockups/system freezes, with a side of BSOD...

  • Thread starter Majarvis
  • 14 comments
  • 509 views

Majarvis

(Banned)
1,423
Hi there :)
I should have posted much sooner than this, but I guess I just didn't think of it.
I own a Compaq R3140CA laptop, and have had it for about a year now. A few months back, my system started having total system lockups out of nowhere. I mean, I'm checking my email, chatting on MSN, nothing strenuous, and then it happens, forcing me to do a hard-reboot.
I thought that it was because maybe I needed more RAM (came stock with 512MB of PC2700 SO-DIMM). So I purchased a stick of Corsair 1024MB PC3200 SO-DIMM memory, thinking it may solve the problem. So I install it, turn the laptop on, and everything is all fine and dandy for a few days, before the same thing starts happening again.
At this point, I am miffed, and getting very frustrated. As a precaution, I ran a memory test program that my friend uses at Staples, looped that for 8 hours while I was at work, came home, and it found no errors whatsoever.
So, as another precaution, I remove the new RAM, and it still freezes up, with the occasional BSOD, of course.
So, now that I have come to the conclusion it isn't the new RAM, I call Compaq. I explain what I have just told you, and they, of course, blame the RAM, and ignore the fact that it was doing this before the new RAM was installed.

So, here I am before you, a broken, bitter man looking for assistance with his laptop :dunce:

I, of course, have everything up-to-date like BIOS, Windows and other important programs like Office, etc. I have scanned for viruses, and came up empty. I have scanned for spyware with Ad-Aware, and came up empty again.

Here are my specs *taken from CPU-Z*:

CPU(s)
Number of CPUs 1

Code Name ClawHammer
Specification AMD Athlon(tm) 64 Processor 3000+
Family / Model / Stepping F 4 8
Extended Family / Model F 4
Brand ID 1
Package Socket 754
Core Stepping SH7-C0
Technology 0.13 µ
Supported Instructions Sets MMX, Extended MMX, 3DNow!, Extended 3DNow!, SSE, SSE2, X86-64
CPU Clock Speed 798.0 MHz
Clock multiplier x 4.0
HTT Bus Frequency 199.5 MHz
L1 Data Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L1 Instruction Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L2 Cache 1024 KBytes, 16-way set associative, 64 Bytes line size
L2 Speed 798.0 MHz (Full)
L2 Location On Chip
L2 Data Prefetch Logic yes
L2 Bus Width 128 bits

Mainboard and chipset
Motherboard manufacturer Compal
Motherboard model 08A0, 32.41
BIOS vendor Hewlett-Packard
BIOS revision F.34
BIOS release date 12/23/2004
Chipset nVidia nForce3 rev. A4
Southbridge nVidia nForce3 rev. A4

Memory
DRAM Type DDR-SDRAM
DRAM Size 1280 MBytes
DRAM Frequency 159.6 MHz
FSB:DRAM CPU/5
CAS# Latency 2.5 clocks
RAS# to CAS# 3 clocks
RAS# Precharge 3 clocks
Cycle Time (TRAS) 7 clocks
Bank Cycle Time (TRC) 10 clocks
DRAM Idle Timer 16 clocks
# of memory modules 2
Module 0 Infineon DDR-SDRAM PC2700 - 256 MBytes
Module 1 Corsair DDR-SDRAM PC3200 - 1024 MBytes

Software
Windows version Microsoft Windows XP Workstation Service Pack 2 (Build 2600)

Thanks, hopefully someone will know how to fix this... :)
 
The only time I've seen XP get a BSOD is when there is something wrong with the hardware (memory more specifically).

Take out the original 256MB stick and move the new 1GB stick into the first slot and boot with that only. See if you still have the BSOD problems.
 
My dad's computer has been pretty much doing the same thing. Reformat the HDD like LM said and that should fix it.
 
What you need to think about is the system uptime. How long has it been powered on before it starts to freeze? And does this time frame remain consistent across reboots?

If it's always the same amount of time, no matter how many times you restart the system, then it's most likely a cooling issue.

If the timeframe varies with reboots, you have a rogue process that is filling up some allocation of something somewhere. Been installing anything recently?

Have a look through your System and Application event logs, to see if there are any clues there.
 
My dad's computer got into something I liked to call "boot-lock". It would boot up to the windows screen, go black, then about 10 minutes late it would restart and repeat the process. All this was after the second clean format of the day on that computer because it was previously BSODing about two minutes after windows loaded.
 
LoudMusic
Format. Reinstall.
I forgot to mention that I have reformatted several times, with the same gloom outcome...
Viper Zero
The only time I've seen XP get a BSOD is when there is something wrong with the hardware (memory more specifically).

Take out the original 256MB stick and move the new 1GB stick into the first slot and boot with that only. See if you still have the BSOD problems.
If I could place the 1024 stick into slot 1, I most certainly would, but unfortunately that original 256 stick is non-removable, so I am indeed SOL... :indiff:
GilesGuthrie
What you need to think about is the system uptime. How long has it been powered on before it starts to freeze? And does this time frame remain consistent across reboots?

If it's always the same amount of time, no matter how many times you restart the system, then it's most likely a cooling issue.

If the timeframe varies with reboots, you have a rogue process that is filling up some allocation of something somewhere. Been installing anything recently?

Have a look through your System and Application event logs, to see if there are any clues there.
I would have to say that it seems to be locking up about 2-3 hours after I reboot. This is a fairly consistent timeframe, and it seems to be fluctuating between 2-3 hours of uptime after initial start-up.

Thanks for your replies guys, hopefully someone will think of something with my reply. If you need any more details, I'd be more than happy to oblige.
 
Majarvis
I forgot to mention that I have reformatted several times, with the same gloom outcome...

Aww, man, I was just teasing. Being a sys-admin that has become my standard answer to any computer related questions outside of the office.

To agree with the crowd ...

A) Don't expect Windows (any flavor) to go uncycled for more than a couple weeks.
B) It's probably hardware related - RAM specifically.
 
LoudMusic
Aww, man, I was just teasing. Being a sys-admin that has become my standard answer to any computer related questions outside of the office.

To agree with the crowd ...

A) Don't expect Windows (any flavor) to go uncycled for more than a couple weeks.
B) It's probably hardware related - RAM specifically.
lol, no problem. My laptop is usually running for 12 hours a day, sometimes more, sometimes less, so it never goes for a week without being rebooted (or in my case, a few hours due to my problem).
If the new 1024 stick isn't the problem, then perhaps it is the non-removable module which is the culprit. Because with, or without, the 1024 stick, my system locks up regardless if the stick is in, or out :indiff:
 
It could also be an overheating issue. The CPU or video overheating will cause a system to freeze without any indication of what's causing the problem. Laptops are also notorious for overheating, as they are small contained devices. Make sure all the fans spin.
 
LoudMusic
It could also be an overheating issue. The CPU or video overheating will cause a system to freeze without any indication of what's causing the problem. Laptops are also notorious for overheating, as they are small contained devices. Make sure all the fans spin.
Interesting. Is there anything like a laptop mount I can buy to put on my desk, to elevate the bottom of the laptop to promote better circulation? Right now it lays flush on my desk, and not much air can get below.
 
Well, i have had numerous problems with my toshiba overheating recently, but they all seem to have been cured since it got cleaned out. So, have the fan cleaned out regularly is one peice of advice i can give you, and yes, you can get things to lift the laptop off the desk for better cooling. I saw on on qvc the other month for about £70 . I also found that having objects behind the laptop increased the chances of it overheating - the hot air coming out the back of the laptop was either hitting the object, and being fed back in through the fan in the bottom, or was heating the object up, and making that displace heat, which heated up the air, which was then fed into the back of the laptop. Try buying a fan to put behind the laptop, and position it so that it blows the hot air out of reach of the laptop's fan. That should do it, but do make sure you get it cleaned out every so often. About every 4 months if you use if frequently.
 
Eh, you don't really need to buy some fancy pants item to elevate a laptop. Just find something kind of tall, long, and narrow, and then another one just like it, and set the laptop on those. Just little risers. And cleaning is a must. Make sure all the air vents are clear of any disruptions.
 
Back