Still crashing, and waiting since 10-23-06 for help

Hello again,

I am still having minidump crashes. I posted on the 23rd asking for assistance, and unfortunately noone helped me

I have enough minidumps to actually post them now, and also I have a EXCEPTION_ACCESS_VIOLATION that happend at the same time.
I have NO events errors in the Event Viewer.

If anyone can give me some input I will be very greatful!

more coming

 

part 2: Still crashing, and waiting since 10-23-06 for help

here are the rest. The last one, Mini102106-01-DIFFERENT.txt is different from the others.
again, thank you!

 

I'm not an expert at code, but here goes:

Your EAV log shows almost NO free physical memory, with only 64 MB free out of 512 MB. By the way, 512 MB is not really enough for WXP SP2 to run consistently error-free. In addition, your 1 GB+ page file is terribly under-utilized by your system at this point. Adding more RAM and moving the page file to a second disk will help, but probably not completely solve the problem.

Firefox is clearly involved in (but not necessarily the cause of) the crashes. What is the memory useage of FF in your task manager after running for a (typical length) session? It is known to have memory leaks that are significant in certain system combinations...

I see NTOSKRNL in the other files. Hmm. Bad juju. Much smoke. Electron gods not happy. Seriously, that is serious (no pun intended) because it means that the core of the WXP system is crashing, not just one program or driver (to put it very simply, somewhat inaccurately, but quite descriptively). Another reason that I would suspect that you have a serious hardware or program problem. I would say that most crashes are IRQl level problems that cause the system to shut down as a reaction to the problem at hand (think, grabbing the banister so that you don't fall down the stairs as you slip), but your system seems to be having the legs knocked out from under it (think, the ground splits open beneath your feet and you plunge into the abyss).

Last, your Java HOTSPOT VM crash is interesting. At the least, start here: http://www.java.com/en/download/help/5000041400.xml

You should consider removal & reainstall of both Java and FF, and make sure that Java is completely updated.

Insert the WXP SP2 disk in your drive, and then run sfc /scannow so WXP can check and (if necessary) reinstall corrupt or missing drivers to the system folder.

Finally, a small point: you should post all of you system specifications when you post here. I know you have WXP SP2 and an AMD processor and the size of your virtual and physical memory, but that is really quite insufficient. Occasionally, seeing one's hardware list will also suggest remedies and possibilities.....

 

1st I want to say thank you for answering my post!

GDERN IT! I just had a whole page typed out and the dern FF crashed again! GRRRRRRRRRRRRRRRRRRRRRRR
I will make it short now, I can't beleive this

I thought I needed memory I was on the correct tract.
My specs are attched now.
FF goes from about 37,00k to over 180,000k and 100% CPU.
I just re-installed java with the newest version.

This is the important part ::
I have a slipstreamed xpsp2 that I made about 1 yr ago. I have all the updates on my machine, so that slipst. is basically outdated. I was thinking about using the new AutoStreamer to make a new slipstream disk. Is that a good idea, or is there a better way to do this?
Also, I was reading about the XP REBUILD cmd. http://www.informationweek.com/story/showArticle.jhtml?articleID=185301251
Which is better? Doing the new slipstream and rebuild, or using what I have now, and using the run sfc /scannow? Lots of possibilities.

 

OK, I set it to give me the BSOD. I tried to change the memory dump to the large dump, but my machine would not take it.

 

oh btw you can run xp error free on 256 let alone 512, so don't make stupid statements.

 

MistressRene: First, do as TimW says. Those codes will likely be helpful.

Second, it is obvious why FF is crashing. 180 MB is unacceptably high, and 100% CPU is the death knell. It will not run at that point-the system WILL shed that load. Ergo, crash.

Third, you are running an Athlon Socket A with an L2 cache of 256 KB on a Motherboard that is, frankly, outdated, at a 133 bus with a five year old BIOS. This is a huge bottleneck for anything you are trying to do with WXP SP2, and it appears obvious why you are crashing--FF is like an elephant on an ant's back, with that kind of memory usage. ABIT's site says that your board is capable of using PC 2100 memory. If you don't have at least that, it is another throttle on the system.

Fourth, with FF alone using 180MB and the OS filling essentially all the rest of your 512MB, you must be paging like there's no tomorrow. Take the heat that must be coming off your processor and your memory, and couple it with a possibly inadequate PSU, and you will get OS crashes repeatedly for no other reason. Your specs from BELARC were helpful, to be sure, but we also need to know info on your other hardware. Give us something like you see in my signature.

Fifth, don't Rebuild/Repair your installation just yet. It is not yet warranted and will almost certainly produce no good results.

As I said before (and even more true now, with the info so far), you cannot run your present configuration "consistently error-free" on 512 MB. No one can.

By the way, that's a quote for those who only offer rude comments & no help.

 

I have been trying to get my machine to crash all day, and LOL it won't do it. It is like trying to watch a pot of water boil. It will never happen
I will push it tomorrow!

I have a question about the heat that comes off computers...
If a MBoard has more efficient components, will it run cooler or hotter? My machine runs on the hot side, but I have 2 internal fans, and a fan blowing on it from the outside. I'm glad I have an emergency stash put away! I think this is an emergency!

I will get back with you all tomorrow. I just wanted to let you all know how very much I do appreciate your input. I am getting a good lesson in hardware!
Have a wonderful night/weekend! Back tomorrow.

 

Tim,
I am running a db of over 10,000 entries, 3 harddrives (1 is a portable), I edit movies and do some graphics. Sometimes these are all going at the same time. I also have an antivirus/firewall combo and anti spyware, and I keep my ftp connection open ... yada yada yada
BTW:: I am still trying to get this to crash via the BSOD. I am trying to beat it up and it still won't crash! I know, as soon as I start doing something important it will poof!

 

I tried my derndest to get that BSOD today. I did everything I knew how to do to beat it up and nothing happened, so
I shut my machine off, and went to watch tv. 2 hours later, my husband says to me "Aren't you going to shut your computer off"?
AND THERE IS WAS THE BSOD! yes! I will also attach the minidump.

The stop message is as follows:

STOP: 0X000000D1
(0X0234000D, 0X00000002, 0X00000000, 0X0234000D)

finally!

 

Have a look here:
http://technet2.microsoft.com/Windo...4ea6-4068-9f55-40801292ec6d1033.mspx?mfr=true

 

I'm surprised no-one has suggested that the RAM may be flakey. Run a memory diagnostic. Several are available for download in the Diagnostics section right here at 'The Geeks'..........

hopperdave2000

 

That seems to be for Windows Server 2003, but thanks anyway!

 

It was asked of me to, if possible post a total list of hardware. I just found this site that is called Driver Guide. It gave me a complete listing of everything on my machine!
I already see a conflict or 2 that I will fix.

 

My system is old and seems to be tired (like me). So I think at this point, I am going get new components.
Just seems easier and more logical, since I have to get more memory anyway...
If anyone wants to suggest so good components, mother board, processor... etc..
I would love to hear some feedback before I make the purchace. Thanks again to everyone that
helped me. I learned lots and it was an interesting adventure! I wish my machine was worth just a
quick update, but it is antiquated

 

Here is the report as requested, pulled under normal load, 2 windows of firefox open.
I had to zip it, as it is a complete run of that program.
That is 1 nice little program, btw!

 

I ran the memtest86+.
What exactly do you need for me to post, so you can tell what is broken?
It does not 'log', so I worte everything long hand,
and will post what you need. I will tell you right off that I had it go for
4 passes and it found 6 errors. Anything else I have no clue
as to what the numbers mean. I also put my request in for the correct flash bios.
I should receive it tomorrow.

 

Do you know if your ram is two sticks or one? If two, remove one and do the mem test again, try to see whick stick is bad, not likely both if you have two. ed

 

I can't tell ya at this hour. I would have to open it up and I'm going to sleep.
The test ran for 2 hours 50 min
cached: 512
RsvMem: 76M
Mem Map: e820Std
Cache: on
ECC: off
test Std
Pass: 4
Errors: 6
ECC Err:0
----------
tst pass failing address good bad err-bits count chan
5 1 000000 135F0 0.1MB -- all these are the same see below*
5 1 49830 0.5MB
5 1 632d8 0.1 MB
5 1 99518 0.05MB
5 1 89b00 0.06MB
5 1 5a698 0.06MB
*all the same
good bad err-bits count chan
00000000 0000000 00000001 1

AMD ATHELON (0.18) 1402MZH
L1 CACHE 128k 8599MB/s
L2 CACHE 256k 2634MB/s
Memory 512M 434MB/s
Chipset AMD 761 (ECC Disabled)

that's all folks
thanks! night!

 

No need to remove the back from my machine. I looked at the report! Check out the last line!

SPD Memory Modules:
DIMM4: Xerox 512 MB PC2100 DDR SDRAM (2.5-3-3-6 @ 133 MHz) (2.0-2-2-5 @ 100 MHz)

Memory Module Properties:
Module Name Xerox
Serial Number None
Manufacture Date Week 43 / 2002
Module Size 512 MB (2 ranks, 4 banks)
Module Type Unbuffered
Memory Type DDR SDRAM
Memory Speed PC2100 (133 MHz)
Module Width 64 bit
Module Voltage SSTL 2.5
Error Detection Method None
Refresh Rate Normal (15.625 us), Self-Refresh

Memory Slots:
DRAM Slot #1 512 MB (PC2100 DDR SDRAM)

 

There are so many things wrong I am upgrading to some newer equipment ~~
Thanks to everyone that helped me do the troubleshooting!!

 

Perhaps this link could be useful (due to log "...Probably caused by : ntoskrnl.exe ( nt!IoCancelIrp+6f )...":
http://www.computerhope.com/issues/ch000646.htm.

Best wishes

Tom

 

Hi. For what it's worth, and just to answer your ?, more efficient=cooler, not hotter. The more energy wasted in the form of heat, the lower the eff. of the device.