BSOD 100000d0 and 100000c5

A Windows XP Pro Dell PC is getting blue screens periodically with the following errors:
Error code 100000d0, parameter1 ff9d9da5, parameter2 00000002, parameter3 00000001, parameter4 8054d579.
Error code 100000c5, parameter1 ff9d9da5, parameter2 00000002, parameter3 00000001, parameter4 805505a1.
The user is the QA Manager so is very PC literate and says he has not installed any new software or devices in weeks or even months, as far as he can remember.
Is there someone here that can read a dump file if I send it (actually, it would be 2 dump files for the 2 different errors)? I don't have the expertise to read a dump file and when I asked Dell tech support to read one from the last PC here that was blue screening a week ago, they could not read it either. They had the wrong "symbol library". I would like to find out what is causing this and fix it if possible, rather than have to reinstall the OS from scratch. That would have a severe impact on the productivity of this QA manager if I have to do that and then he has to reinstall all his QA software.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rob HutchinsonTech Lead, Desktop SupportCommented:
Peter HartCommented:
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.
Peter HartCommented:
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 .
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

mauldlouieAuthor Commented:
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).

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.
mauldlouieAuthor Commented:
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".
Peter HartCommented:
the zipped file should have .zip at the end not .dmp
mauldlouieAuthor Commented:
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!
mauldlouieAuthor Commented:
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.
Peter HartCommented:
any luck with the diagnostics and the system restore ?
mauldlouieAuthor Commented:
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?
mauldlouieAuthor Commented:
I'm not sure if it's SP2 or SP3 (will have to check with user).
mauldlouieAuthor Commented:
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                                    *
*                                                                             *
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.
Arg1: ff9d9da5, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 805505a1, address which referenced memory
Debugging Details:
805505a1 894804          mov     dword ptr [eax+4],ecx
LAST_CONTROL_TRANSFER:  from 8056c4ab to 805505a1
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
f7415bd8 ??              ???
SYMBOL_NAME:  NDIS!ndisWorkerThread+4b
FOLLOWUP_NAME:  MachineOwner

Open in new window

The second dump file is wierd.  It's pointing to your ntoskrnl.exe as the culprit.  This is usually a problem with spyware/virus/malware infection.  An infection would also explain the problems with the NIC driver.  You really have a couple options:  1)  Replace the NIC with a new one after disabling it in the BIOS and see what results you get or 2) run a scan with SuperAntiSpyware and see what it turns up.  Either way you will need the pc for 30 minutes while you do either 1 or 2.

If you get any more dump files, let me know so I can review them and see if there is a pattern.  Thanks mauldlouie!

Superantispyware ->

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mauldlouieAuthor Commented:
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.
mauldlouieAuthor Commented:
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.

; )
mauldlouieAuthor Commented:
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?
mauldlouieAuthor Commented:
I just checked the event log on the PC and there have been no further BSODs yet.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.