Tech Support Forum banner
Not open for further replies.
1 - 4 of 4 Posts

2 Posts
Discussion Starter · #1 ·

can you help me in solving these crashes. i previously encountered same but out IT recommended to repair OS. after a month i then again encountered blue screen error, and decided to research. below are the details of the error and i also attached the minidump files.

i hope you can help me in analyzing and solving this issue.

* *
* Bugcheck Analysis *
* *

This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
kb will then show the corrected stack.
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

Debugging Details:




PROCESS_NAME: devenv.exe

LAST_CONTROL_TRANSFER: from 805cedc5 to 805c5e77

a742f008 805cedc5 a742f0c8 a742f0ac a742f02c nt!ObFastReferenceObject+0x5
a742f018 805f6f85 89902020 a742f0c8 a742f090 nt!PsReferencePrimaryToken+0x17
a742f02c 805f15bb 898f2da8 89902020 a742f0c8 nt!SeCaptureSubjectContextEx+0x3d
a742f04c 805f1712 898f2da8 89902020 a742f0ac nt!SeCreateAccessStateEx+0x4f
a742f06c 805cb55b a742f0ac a742f090 001f0fff nt!SeCreateAccessState+0x28
a742f164 8054167c a742f208 001f0fff a742f20c nt!NtOpenProcess+0x11b
a742f164 805006d5 a742f208 001f0fff a742f20c nt!KiFastCallEntry+0xfc
a742f1ec b9827174 a742f208 001f0fff a742f20c nt!ZwOpenProcess+0x11
WARNING: Stack unwind information not available. Following frames may be wrong.
a742f22c b981164f 8a3dea20 000007f8 002320cc igxpmp32+0x20174
a742fdc4 b980c084 8a3dea20 a742fdf4 00000000 igxpmp32+0xa64f
a742fdd8 b9801729 8a3dea20 a742fdf4 0000000c igxpmp32+0x5084
a742fe9c 804ef19f 8a3de708 896b95b8 00000004 VIDEOPRT!pVideoPortDispatch+0xabf
a742feac bf8651da e457a000 e49825d0 00000001 nt!IopfCallDriver+0x31
a742fedc bf865254 8a3de708 002320cc a742ff40 win32k!GreDeviceIoControl+0x93
a742ff00 bf05701e 8a3de708 002320cc a742ff40 win32k!EngDeviceIoControl+0x1f
a742ff20 e457a000 e49825d0 00000001 e4982798 igxpdv32+0x801e
a742ff38 e457a000 35e0d000 00000001 000007f8 0xe457a000
a742ff3c 35e0d000 00000001 000007f8 bf057283 0xe457a000
a742ff40 00000000 000007f8 bf057283 8a204000 0x35e0d000


b9827174 ?? ???


SYMBOL_NAME: igxpmp32+20174


MODULE_NAME: igxpmp32

IMAGE_NAME: igxpmp32.sys


FAILURE_BUCKET_ID: 0x7f_8_igxpmp32+20174

BUCKET_ID: 0x7f_8_igxpmp32+20174

Followup: MachineOwner


2,210 Posts
Both crashes blame your Intel Graphics Accelerator Drivers. Judging by the date of these drivers (Feb 2008) I'd say there's good reason for that. See if you can't find an update for your graphics drivers.

2 Posts
Discussion Starter · #3 · (Edited)

i will try to update the said driver, by the way how will i know what made the error and the date you mentioned in the minidump file. i wish to know more so that i can fix and diagnose my pc in the future.

2,210 Posts
It's not all that easy. I'm only going by what is suspect in the callstack (which is the big ole ugly list of stuff there). 3rd party drivers present in the callstack hint as potential cause, but not always, and it's not usually that easy. The 3rd party drivers I see are igxpmp32.sys and igxpdv32.dll, both of which involve the Intel graphics drivers.

There's a lot to kernel debugging and crashdump analysis than what whipping out Windbg and typing !analyze -v will do for you. Much of the time you'll get false positives caused by the suspect leaving the scene with only an innocent bystander to blame for the crime. There's a lot involved in determining if what is shown by the minidump can even help you, and if it can, what you need to do to give it the answers. Essentially no different than a crime scene analyst, just a lot more nerdier.

Minidumps don't provide much info, but they're usually used to show up patterns. If you can find consistencies between them then you're on the right track. In this case even though it's just two crashdumps I do see both are the same type of bugcheck, both are performing the same exact thing, and both involve those same two drivers. That's pretty consistent enough to land blame on that driver. If you aren't finding anything consistent, than most likely the cause is hidden and you'll have to do some heavy-duty investigation to point it out. Driver Verifier often helps big time, causing seemingly impossible cases to be resolved very quickly.

Oh, and if you want to know how I got the dates, you can use the command lm (list module) to list currently loaded modules. Read the help manual for Windbg to hear all the various ways you can use it. For the dates I use lmsm t, where the sm sorts list by filename rather than by memory address, and t displays file stamps. Great for discovering old drivers on your PC. For the nitty gritty on particular drivers, you can use lmvm <modulename>, where <modulename> is the name of the module/driver. In example:

0: kd> lmvm igxpmp32
start    end        module name
b9807000 b9d9c620   igxpmp32 T (no symbols)           
    Loaded symbol image file: igxpmp32.sys
    Image path: igxpmp32.sys
    Image name: igxpmp32.sys
    Timestamp:        Fri Feb 15 16:12:05 2008 (47B60025)
    CheckSum:         005A0262
    ImageSize:        00595620
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
This usually isn't all that much to go by, though do note sometimes the entire image path will be mentioned (like \Windows\System32\) so that helps in some cases. Usually I just do a google search of the module name. This website also helps.

Have fun mate. If you're ever curious getting into this kinda stuff in the future we're happy to help lead ya on the way. I'm a novice myself but I'm gradually improving :)
1 - 4 of 4 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Not open for further replies.