BSOD 100000d0 and 100000c5

the dump file won't be any use except to the windows programmers. - BSOD is probably hardware or device driver problems or over heating problems (check for clogs vents/heat sinks)
if overheated it may have damaged the RAM - try replacing
Dell Pc s usually come with built in daignostics - check the manual but <ctrl> <F12> at startup should bring up the utilities screen where you can check the hardware.

also check the system restore calandar (start -all programs - accessories -system tools - system restore) use the wizard to check the calendar of check points nad see what was installed - it may be a failed update to one of thedriver (although that would be more frequent if itwas a software problrm.
I tihnkg it its random then its probably temparature and or hardware malfunction .

ASKER

Thanks, I will ask user to run the Dell diagnostics and look at system restore calendar. I can't really get on it to troubleshoot as he is always running testing scripts on it.

A similar question was asked and the issue related to a network card (3com to be exact).

https://www.experts-exchange.com/questions/22701717/BCCode-100000d0-BSOD.html

It may be worth a shot to upload the dump file. There are a few tools that can determine if there is a driver that is flaky as in the example above. Not ruling out hardware errors/failures, but I would start with the dump file.

ASKER

How can I upload the dump file? I zipped up the 2 dump files from this week and when I tried to upload, I am told "the extension of one or more files in the archive is not in the list of allowed extensions: Mini110408-01.dmp".

the zipped file should have .zip at the end not .dmp

ASKER

It does have .zip at the end. It was complaining because the zip file contains .dmp files.

Rename it logfile1.txt and logfile2.txt. let us know what to rename it to once we download it. thanks!

ASKER

Good idea. I have renamed the files to logfile1.txt and logfile2.txt and zipped them up again.
These files were originally named: Mini110408-01.dmp and Mini110608-01.dmp.
Logfiles.zip

any luck with the diagnostics and the system restore ?

ASKER

I am waiting for the user to do these as I can't break into his PC to do them as he is always running testing scripts. I also downloaded the latest drivers from Dell and ATI for his PC and asked him to try installing those to see if that helps.

Very good. I will check those out this evening and post something back over the weekend. Take care!

I am looking through the dump files now. What SP was installed on that pc?

ASKER

I'm not sure if it's SP2 or SP3 (will have to check with user).

ASKER

The user has Windows XP Pro SP2.

Perfect. That was the symbol pack I installed. Running the diag now.

Alright, after loading the first dump file you posted, it appears there is a problem with your NIC. Is this an on-board NIC? I would disable it in the BIOS and add a new NIC. If you are looking for a quick "test", reload the drivers of the NIC with the newest version and see if you can duplicate the BSOD.

I am looking through the second dump file now.

In case you wanted to see where the first dump file mentioned the problem.

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: ff9d9da5, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 805505a1, address which referenced memory
 
Debugging Details:
------------------
 
 
BUGCHECK_STR:  0xC5_2
 
CURRENT_IRQL:  2
 
FAULTING_IP: 
nt!KiDoubleFaultStack+2a21
805505a1 894804          mov     dword ptr [eax+4],ecx
 
DEFAULT_BUCKET_ID:  DRIVER_FAULT
 
PROCESS_NAME:  System
 
LAST_CONTROL_TRANSFER:  from 8056c4ab to 805505a1
 
STACK_TEXT:  
f7916b98 8056c4ab 00000000 00000001 e5726854 nt!KiDoubleFaultStack+0x2a21
f7916bbc 8056c606 88c42cd0 00000000 00000000 nt!ObOpenObjectByPointer+0x2e
f7916bf0 80573bd0 00000000 89bfbe70 00000000 nt!NtQueryInformationProcess+0xed7
f7916d4c 805740eb f7916db4 001f03ff 00000000 nt!MmMapViewOfSection+0x153
f7916d80 f7415bd8 f7916db4 001f03ff 00000000 nt!IopGetModeInformation+0x2f
f7916dac 80574128 00000074 00000000 00000000 NDIS!ndisWorkerThread+0x4b
f7916ddc 804ec791 f7415b85 00000000 00000000 nt!NtQueryInformationFile+0x459
f7916e94 00000000 00000000 00000000 00000000 nt!MiDeleteSystemPagableVm+0x280
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
NDIS!ndisWorkerThread+4b
f7415bd8 ??              ???
 
SYMBOL_STACK_INDEX:  5
 
SYMBOL_NAME:  NDIS!ndisWorkerThread+4b
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: NDIS
 
IMAGE_NAME:  NDIS.sys

Open in new window

ASKER CERTIFIED SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

Thanks for the info. We have been migrating from TrendMicro OfficeScan (corporate antivirus) & Sunbelt Software CounterSpy to Sunbelt Software Vipre antivirus/antispyware. So I think I will migrate the user to Vipre and run a deep scan and see if it finds anything. I checked his dump directory and don't see any more dump files yet but if he keeps getting BSODs, I will try switching out his NIC as you suggested.

Outstanding work. I will continue to monitor this post for an update.

ASKER

I upgraded him to Vipre and ran a deep scan and it found nothing except some cookies and non-threats like VNC. At this point, I think I will just monitor his PC and see if it behaves or not. If not, then will try putting in another network card as suggested.

You could always check to see what driver version he has on that NIC and check with the manufacturer's website to see what problems are related to that. If you get any other BSOD, please up load them. Also, have a spare NIC handy because I would be willing to bet that you see this error again.

; )

ASKER

I have several spare NICs :). I will see if there is an updated driver for the NIC from the manufacturer. I did download all the updated drivers from Dell's website but they did not have an update for the NIC.

Gotcha. Sounds like you are staying on top of it but those NIC's are responsible for a LOT of ghosts that we chase. Good luck. Post back what you find.

Any news?