[Zithe24]

Look what I miraculously found. Apparently it started saving dumps now. I was going to post the first two last night, but I crashed in the middle of writing the post. The error was an odd one, it said "BAD_POOL_CALLER". First time it's given me this one. Also as for the no network testing, I only got to test it once so far. I unplugged the ethernet cable, booted into Windows, and then I went to go do other things. When I came back the screen was completely black and wouldn't wake up. I'm not sure how this happened, so I will try to do some more testing on this.

[valis]

here's what the analysis says.....haven't seen this one before, so I'm going to pm one of the guru's on this....

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: e2398a28, Memory contents of the pool block
Arg4: 8a6fb178, Address of the block of pool being deallocated

[valis]

okay, asked for some help on this one, we'll wait for the heavy hitters to show up.....I know when I've met my match.

[Rollin' Rog]

When is the last time you have blown out all dust with a can of compressed air?

That "whooshing' sound could well be the fan revving up, perhaps prematurely if there is a sudden heat build up. Thje timing and mode of the errors indicates a stress issue -- which could be heat.


The many "random" errors, and the ones I've seen tend to point to a hardware fault. This could be heat, but perhaps alsofaulty ram.

If you haven't tested it you should do so.

If you need any help with creating a bootable test disk, just let me know.

Beginners Guides: Diagnosing Bad Memory


Memtest86 - A Stand-alone Memory Diagnostic


>> Also, post a HijackThis scanlog so we can see if there are any obvious malware issues >>

Download and install HijackThis. Run it and select "do a system scan and save the log file". Then copy/paste the contents of the log to a reply

http://www.trendsecure.com/portal/en...ols/hijackthis

>> Finally, install Speedfan and monitor the temps with its graphical interface. Let me know if you see more than a 35 c rise from a completely cold boot.

http://www.almico.com/speedfan.php

[valis]

hey, thanks a lot, Rog.....much appreciated.

I'm still learning this msdebugger, but is has come in invaluable on 3 occasions at work, to the extent that my boss (CIO) wanted me to put a ppt together to show everyone else how to use it.

blind leading those who can't see, was what I entitled it.

[Zithe24]

Well, I think we may have found the problem. I have to leave for work now before the test finishes, but memtest86+ has already found about 80,000 errors in my memory. What do I do from here? Does memtest fix them for me or what? I will be at work until midnight so I may not get to update again until tomorrow.

[valis]

no, if memory goes bad, it's just bad....time for new memory......as it's electronically refreshed every x thousand times/second, once it begins to go south, it's time for new memory, I'm afraid.

[Rollin' Rog]

Yeah, you will have to replace it. A good time to decide if you just want to keep the same or increase.

Replacing memory isn't too hard; since you have the experience of replacing a video card -- you are already familiar with part of the drill.

http://www.youtube.com/watch?v=SiFIgSQOY7g

[Zithe24]

Thanks guys! Luckily only one of my four sticks was bad, so I still have 1.5GB to work with. I'm posting from my downstairs computer right now, and it's working like a charm. Marking this as solved. I also attached a HJT log to this post in case you wanted to give it a look anyway. Thanks again!

[Rollin' Rog]

Scanlog looks fine -- glad to see an easy solution -- and of course you are most welcome for the help.