Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Device Driver causing XP to shutdown and restart.

May 22, 2005 7:52PM PDT

I'm running XP SP2 on a hp pavilion. I have recently upgraded the RAM from 256MHz to 1GHz. Since I have done this I occasionaly (but regular enough to be now getting on my nerves) find XP shutting down, restarting and filing an error report as "the system has recovered from a serious error". Microsoft reports that it is a device driver that has caused the problem but can be no more specific about which one. As the only hardware I have changed recently is the RAM, I can only assume this is the cause.
To complicate things a little the replacement RAM is 2nd hand but is in good working order (PC2100 266DDR). It is by the same manufacturer as the original, but I don't know who that is!! The logo is a rounded letter M circled by a planet-style ring.
1) Does RAM require a driver?
2) Who is the manufacturer of my RAM?
3) Am I barking up the wrong tree?

I haven't lost any work yet, but it can't be long. Any advice would be much appreciated.

nossy

Discussion is locked

- Collapse -
Two things.......
May 22, 2005 8:51PM PDT

First, you said you upgraded from 256Mb to 1Gb, but you didn't state the configuration of the modules ie. 1x512 and 2x256. You also stated that the ram is in good working order. At this stage I'm not entirely sure we can make that determination. You're problemis definitely symtomatic of bad ram, but don't panic yet, it may just be an installation problem. The first thing to try, is to reseat the ram (assuming of course you feel competent enough to do this, and making sure you're grounded from static by touching the chasis of the computer while it's plugged into the wall and not running) often newly installed ram can be seated a little off and cause problems due to a poor connection, it happens to the best of us. The other thing to try is to switch dimm slots on the board if you reseat in the original slot and the problem persists. It may just be that slot doesn't like that chip but would work fine with other chips. It's a pavillion, so it doesn't have a high end motherboard in it. Last but not least, to test the memory, go to http://www.memtest86.com/ and download the floppy of bootable cd version of this free tool (the standard in the industry amongst techs) and it'll run when you boot the computer with the disk in. Most of it may look like greek to you, but what you're looking for is in the bottom potion of the left hand side of the screen... badmem= (hex value here) hex value being an address on one or more of the modules you have installed. Note: If you have more than one module installed, I recommend testing each one individually to determine the culprit if the initial test shows bad memory addresses. To answer your question... no ram doesn't need drivers, no you're not barking up the wrong tree, and please post back if the bios is correctly identifying the amount of installed ram. Happy Have a great day!

- Collapse -
Trying it out
May 25, 2005 6:20PM PDT

The RAM is 2 X 512MB. I've gone straight for swaping the slots and being as sure as I can be that they are seated properly. I'll leave it a couple of days to see if the problem manifests itself again. I've also obtained the memtest86 boot floppy you suggest in case I need it. I'll use it anyway to see what it does. Thanks for your advice, and I'll let you know if it works.

- Collapse -
I forgot...........
May 22, 2005 8:58PM PDT
- Collapse -
Memory
May 23, 2005 12:48AM PDT

An easy and fast test is to remove the new ram you just installed and find out if the problem is still there.As you said this issue started after the upgrade.

- Collapse -
will do
May 25, 2005 6:21PM PDT

Will do if initial steps are not successful.

- Collapse -
Check specs...
May 23, 2005 3:00AM PDT

Remove the new ram and see if things settle down. If they do, it suggest one of two areas to look into: the power may not be enough to run all ram -OR- the ram is defective.

You can also, remove the old ram and install the new alone and see how the system reacts. If it seems OK, install the old ram *after* the new ram in the slots. Last, sometimes, some mtrbds. just don't like all slots populated, it may offer a reason under its specs sheet, but consider that the CAS rating don't match. Offhand, your logo doesn't ring a bell at the moment. Google for this pgm. Everest Home Edition by Lavalys. Its system status report pgm. that shows what you really got and for you what ram sticks report as. If they differ too much not a good match, but if your system allows you to tweak the ram setting, go for a safe or lower setting for now and see how it reacts. Otherwise, the ram maybe good but not a good match for your system with *all" ram present.

tada -----Willy

- Collapse -
you learn something new everyday
May 25, 2005 6:41PM PDT

Thanks for your suggestions. Will be trying them if initial steps don't work out. I downloaded Everest Home Edition, looks useful, and it is identifying 2 slots occuppied by 512MB SDRAM. So that's promising at the moment.