Check this box, then you can look in the location that is in the 'Crash Dump' box to find the dmp file.
Ok, we need two more passes of dumps to make progress on this. 1) We need to enable pool tags, and get a full memory dump to isolate which tag...
This latest dump is showing evidence that your physical memory is bad. The data in your memory for the file WIN32k.SYS does not match the data...
I think that hotfix certainly could yield some fruit. If it doesnt pan out, i'd take some perfmons of the machine and see how you are doing on...
use the trace, luke.. use the trace. start a trace on a freshly booted client, then try to hit the server. Look in the trace for DNS traffic...
is it generating a Drwatson log, are you setup to have it write out a dump file? You can configure it by Start->Run drwtsn32 Once you get...
ill look at this tomorrow. real quick, this is pool corruption, maybe a double free. Setup for a FULL KERNEL dump, we are going to need to go...
its not a conslusive test, unfortunatly. But its interesting. did you remove that old driver? Your old ram will probably not fit. if you arent...
In explorer, navigate into the folder c:\windows\system32\drivers Within that directory, you will find a file named BANTExt.sys. Rename that file...
I would clearly point out we have several resident hardware experts, who have given you some very good information. I do not see any problem in...
It seems pretty clear that you have a driver that is touching hardware in a bad way to force it to reset like that. The safe mode list is a good...
We need to keep it seperate.. the USER.DMPs are from user mode programs crashing, and probably not related to the memory corruption problem....
note to self: ask people if they are overclocking thier ram before debugging memory corruption issues. Pending testing with a known good stick...
This latest STOP 50 is bad news. The memory is hosed. The area of memory that got whacked is in such a place that unless you have a driver on...
ok this is a good one.
We are looking for one that is NOT a double fault. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT <--------- Arg2: 80042000 Arg3:...
This is another double fault. unfortunatly, we are no closer to our goal, we need one of the other kinds to happen to catch the bad guy. Lets...
i'm a little dissapointed the HP tech took you down that route, it sounds like there would have been less invasive means to get you out of the...
You've got something messing with your memory. two possible vectors, bad driver or bad ram. Lets talk bad driver isolation first Driver...
its difficult to make an authoritative leap from the safe mode output to a specific driver at fault. The only good data is a dump for 8es. At this...
Separate names with a comma.
