Computer help anyone?

first off the minidump file is generated according to the system state--so it will be different every time. turn off automatic reboots if you want to see the error in all it's glory [right-cliky my computard, properties->startup and recovery, and if you can't figure that out, go pay someone some money]

secondly, go check the thermal settings--there are apps that take the temperature readings--go push compressed air through the little ports and unclog that mofo.

thirdly, replace the ram. Hard to believe that you bought 1GB with no warranty, but it's possible.

With any computar problem it's science--just recreate the problem and elminate the variables that cause it.

Thanks for pointing me to the startup and recovery options. I've been fixing computers for 3 years (software, mind you) and I never new that existed haha.

In terms of the RAM, like I said I did do a memtest, and it states that the RAM was completely fine (is there any other way/program to test it by chance?)

However, the temperature of the computer could be an issue. I had my system board replaced and they messed around with the processor (I'm not sure what they did, but something about tweaking it for performance or some meep). Know about any settings that I could mess with in terms of that?

^ what phil said

a) has anything changed shortly before the problem occurred? (new software, drivers, whatever) b) how long after just had my laptop repaired through Best Buy not 4 months ago did the problem start? c) i know it seems unlikely, but try uninstalling the ram (restore to original) and see what happens.

i know of some people who tend to let memtest run for 24 hours at a minimum. they could be crazy, but you might try that.

for temps, you could grab a cpu intensive program and check temps in windows/reboot and check temps in bios/see if the problem happens more frequently. the only one i can think of off the top of my head is superpi, but i don't know if it's appropriate.

Also, run a full disc surface scan. I've seen issues sometimes where there are unmarked bad sectors in the system area of the disc (or the page file), and whenever the os tries to I/O from one of those sectors... zap.

Ok, here's an update. I got a blue screen last night (after a couple of complete freezes/manual reboots, and after preventing Windows from automatically restarting on a blue screen) and got a "Physical Memory Dump." On reboot, Windows again stated, "Windows has recovered from a serious error" with the "sysdata.xml" and "Minixxxxxxx.dmp" file errors.

So... I ran two different memory testing programs (booted them from a CD) and let the first run all night and the second run for a few hours. Neither found anything wrong with the RAM (of course that doesn't mean there necessarily isn't). I'm going to try the disk surface scan tonight after I get out of work, but with the errors given, should I assume just to go and get my RAM replaced?

I cast my vote for heat buildup. My ancient POS laptop just took the dirt nap over the same issue. It was exhibiting similar behavior the week or so prior to its demise.

It was getting up around 140 degrees regularly, despite me having removed the processor/heatsink, blowing out the fins and reapplying Artic Silver.

Running MemTest for a full burn-in cycle still wouldn't hurt, but only after you've either ruled out or remedied any heat related issues.

P.S. Don't EVAR (I MEAN EVAR!!11) take anything you value to the Geek Squad. EVAR.

P.S.S. No, really; not EVAR.

Now that you mention the high possibility of that, it somewhat might make sense. Although my actually casing of the laptop never really feels "that hot" when it crashes, I have noticed that sometimes when it crashes I can't even turn it back on without waiting (with it off) for about 30-60 seconds, and then it very likely just crashes again.

If this is the case, do you just recommend opening up the whole meep thing and seeing if meep is clogged up in there or anything?

Depends on your comfort level with such operations, and your confidence that you can get it back together again without any "extra parts."

Getting the keyboard back in place can sometimes be a meep. Just go slow, label EVERYTHING, and keep track of your screws. Once you gain access to the mobo, blow out all the dustbunnies with some canned air. Look for canned air with one of those twirly keyboard cleaning widgets; they're meep for cleaning out hard to reach areas.

If I remember correctly, Intel chips exhibit this behavior during overheating. AMD chips tend to self destruct. So if its an Intel chip then the heat issue is probably culprit. Also if they did some "adjusting" I would double check and make sure they dont have it over clocked. If this is the case you can clean and clean and its still going to overheat.

The chip is an AMD 3200+, if that helps with anything. In terms of seeing what your processor is running at, and/or to modify the settings, how exactly would I go about that?

You can do this within the BIOS setup on the machine. See what the socket clock is set to. Depending on the BIOS there are probably several different settings, 100-400mhz and an auto select or something like that. If you know what the multiplier is on the chip then you pick the best socket speed, when multiplied by that number best matches the cou speed. At least thats how I remember it. I'm not positive but I think alot of the newer BIOS's have the ability to do this for you. While your in there check to see if there is a parity check for the memory. If its on, turn it off, I know on the IBMs here at work we have to disable that or the machines will tend to kick out blue screens relating to the parity check from time to time.

unless i missed a comment, then it looks more likely to be an overheating issue. google for mother board monitor or similar temp display utility and check it out.

cleaning the dust out should in theory be relatively easy, should be similar panels as the one you removed to fit the ram upgrade, check whats in them, get a can of compressed air and give it a good blast and see what comes out the side vents.

might be a good idea to see if one of the fans is operating properly while you got a panel off, then try sticking a fork in a wall socket.

Here's a couple of things:

1. Double check to see if your memory has matching speeds. If you're running DDR 2100 with a DDR 2700 chip, the 2700 is supposed to bump down to 2100. On some AMD boards this is a problem which can cause memory problems.

2. Switch the memory modules so that the higher density chip is in slot 1. On laptops slot 1 is sometimes not very apparent. So just switch it until it works.

Both of those issues won't cause errors that'll be noticeable by Memtest86..... so I guess just mess around with it until it works.

Somebody said to me once that "fixing a computer isn't so much a science as it is like fixing your prostate: You just have to dig around in that meep until things start running smoothly."

"(I'm not sure what they did, but something about tweaking it for performance or some meep)."

As said by fl_project check for overclocking of the processor. Download a program like Lavalys Everest Home Edition (freeware). You can check some hardware info with it.

http://www.majorgeeks.com/download4181.html

Alright, after running Everest with my computer being on for about 10 minutes, here's what the program said:

Under the sensor tab, my CPU is running at 25 C and my hardware at 31 C. I'm guessing these temperature are normal?

Here is a summary of the information given under the Computer/Overclock tab:

<code>CPU Properties:
  CPU Type                                          AMD Athlon 64 3000+
  CPU Alias                                         Newcastle S939
  CPU Stepping                                      DH-CG
  CPUID CPU Name                                    AMD Athlon(tm) 64 Processor 3200+
  CPUID Revision                                    00000FF0h

CPU Speed:
  CPU Clock                                         996.99 MHz
  CPU Multiplier                                    5.0x
  CPU FSB                                           199.40 MHz  (original: 200 MHz)
  Memory Bus                                        166.16 MHz

CPU Cache:
  L1 Code Cache                                     64 KB  (Parity)
  L1 Data Cache                                     64 KB  (ECC)
  L2 Cache                                          512 KB  (On-Die, ECC, Full-Speed)

Motherboard Properties:
  Motherboard ID                                    <DMI>
  Motherboard Name                                  Hewlett-Packard Presario R4000 (PX356UA#ABA)

Chipset Properties:
  Motherboard Chipset                               ATI Radeon Xpress 200M, AMD Hammer
  Memory Timings                                    2.5-3-3-7  (CL-RCD-RP-RAS)
  Command Rate (CR)                                 1T

SPD Memory Modules:
  DIMM2: Kingston K                                 1 GB PC2700 DDR SDRAM  (2.5-3-3-7 @ 166 MHz)  (2.0-3-3-6 @ 133 MHz)

BIOS Properties:
  System BIOS Date                                  08/24/06
  Video BIOS Date                                   05/03/03

Graphics Processor Properties:
  Video Adapter                                     ATI Radeon Xpress 200M (RS480M) Chipset
  GPU Code Name                                     RS480M  (PCI 1002 / 5955, Rev 00)
  GPU Clock                                         301 MHz  (original: 300 MHz)
</code>

Since I have no idea what half of that meep means, if something is out of whack, let me know. And I really do appreciate the help guys, I haven't messed around with hardware/hardware settings much in my days, so the info has been really helpful.

Interesting I guess...

neejjir: Somebody said to me once that "fixing a computer isn't so much a science as it is like fixing your prostate: You just have to dig around in that meep until things start running smoothly."

I don't know much about fixing one's prostate [never broken it] but I still think isolating the causation will give you the solution--or at least the cause of the problem.

Check to see if this is in there:

http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-42489-1&lc=en&cc=us&dlc=&product=453183&os=228

Now go play with software. . . but I doubt you have ever fixed a Software issue like this one. The minidump files actually say things in those codes. What be those STOP error codes?? BUT WAIT! don't post them here, just plug them into google, and then realize what general thing you have to research next. Then at the end of the day you can know what causes the problem and then fix it. If your processor is being told to run at a different speed, maybe there be a problem.

Anyhow, back everything up and learn how to use any computer anywhere...

Quickest and Easiest solution: Buy a Mac.

For total satisfaction buy a Big Mac.

Your memory module is in DIMM2, not DIMM1. Switch the memory to the other slot before you continue with anything.

PS - Phil:

You might want to look at this site for how to fix a "broken" prostate...

lol. i've been having this exact problem for a few weeks now. after reading many a lame thread on the supposed "fixes" i tried removing the side panel of my computer case. guess what? no more minidump reboots. it was an entirely thermal problem. i've got an OC'd athlon 64 (3000), 4 hard drives, and a ginormous video card so the heat issue makes sense.

as you well know, laptops run hot anyway so this is likely the problem.