ataport.sys BSOD caused by WMP  

BW

more of the same


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\092509-42828-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a46000 PsLoadedModuleList = 0x82b8e810
Debug session time: Sat Sep 26 01:20:26.978 2009 (GMT-4)
System Uptime: 0 days 0:02:55.025
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 801dc000, 0, 0}

Unable to load image igxpmp32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igxpmp32.sys
*** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys
Probably caused by : ataport.SYS ( ataport!ProxyRequestDpc+22 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
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
Else
.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)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 801dc000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: wmplayer.exe

CURRENT_IRQL: 1f

LAST_CONTROL_TRANSFER: from 82a14ba0 to 82a14967

STACK_TEXT:
ac174000 82a14ba0 82b6fd20 00000009 ac174044 hal!HalpLowerIrqlHardwareInterrupts+0xf
ac174010 82ab3ddf 848a43f4 848a30e0 00000000 hal!KfLowerIrql+0x58
ac174044 887e486a 848a309c 00000000 00000000 nt!KeInsertQueueDpc+0x235
ac174058 887e4e6b 848a30e0 84a02290 ac174098 ataport!ProxyRequestDpc+0x22
ac174068 887dd1dc 848a43f0 ac174078 00000000 ataport!IdeProcessPortNotification+0x99
ac174098 887d1fc2 848a43f4 84a02290 848a43f4 ataport!AtaPortCompleteRequest+0x22
ac1740b4 887d21e0 848a43f4 84a02290 01174150 atapi!AtapiCompleteRequest+0x122
ac1740dc 887d22df 848a4300 84a02290 ac174150 atapi!AtapiProcessInterrupt+0x1d0
ac174104 887e1f04 848a4350 ac17411c 887e248e atapi!AtapiHwInterrupt+0xf3
ac174110 887e248e 848a30e0 ac174148 82a857ad ataport!CallMiniPortHwInterrupt+0x14
ac17411c 82a857ad 8513ea00 848a3028 ac174148 ataport!IdePortInterrupt+0x10
ac17411c 8e2835c0 8513ea00 848a3028 ac174148 nt!KiInterruptDispatch+0x6d
WARNING: Stack unwind information not available. Following frames may be wrong.
ac1741b8 e386e77d 00000263 0000001e 6386e77d igxpmp32+0x4b5c0
ac174418 00000000 00000000 00000000 00000000 0xe386e77d


STACK_COMMAND: kb

FOLLOWUP_IP:
ataport!ProxyRequestDpc+22
887e486a 5d pop ebp

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: ataport!ProxyRequestDpc+22

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ataport

IMAGE_NAME: ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf16

FAILURE_BUCKET_ID: 0x7f_8_ataport!ProxyRequestDpc+22

BUCKET_ID: 0x7f_8_ataport!ProxyRequestDpc+22

Followup: MachineOwner
---------

pretty much the same WMP causes ataport and igxpmp32.sys to fault. Is there any way you can NOT run WMP?

You haven't been reading my posts then.

I have used VLC and it completely freezes my system.

I have used K-Lite Codec Media Player Classic and it gives me the runtime error I listed earlier.

I have used WMP and get either a BSOD or it completely freezes my system depending on which driver I use.

No video player I have used works perfectly with these drivers. I have only been able to get a BSOD from WMP with the newer driver.

BW

Yep I have read both pages multilple times. We haven't talked about upgrading the bios, have we? there is something that causes the same files WMP, ataport, and the intel video accelerator to be in almost every dump.

ken

I have the latest BIOS (version A10 for the ME051 System BIOS) for my Inspiron 1300 laptop. They haven't released a new BIOS for it since April 2007.

I also never had a problem with this in XP Home or Vista Business, which I had on my laptop before doing a clean install of Windows 7 Business.

BW

Im just touching all bases I have an inspiron 1405 with A10 (32bit) and it is starting to show its age. I dont even have WMP installed so I cant even test it against ataport and the intel accelerator (which I also have).

I cant think of anything right now but let me think about it for a while.

Ken

bwood720 said:

So, I did some more extensive troubleshooting. I tested my hardware using the Dell Diagnostic boot partition--it came up clean. I then remove my video driver and went to the one provided by Dell on their website for my laptop (6.14.10.4609 instead of 6.14.10.4764 provided directly from Intel). This gave me a little better experience. I noticed that I couldn't get a BSOD with this driver--at least I couldn't yet. I could only get it to completely freeze my system if, in the process of dragging the window quickly from one screen to the other, I managed to touch the "Aero Snap" areas. This would immediately freeze my system, both in WMP and VLC.

In the process of dragging the window, WMP would stop playing the DVD for about 10 seconds before it would continue in the new location of the window (if I didn't touch any Aero Snap areas). If I used VLC and got it to completely freeze my system (I never got VLC to give a BSOD), the sound would continue playing for minutes (without any video obviously because my computer was completely frozen) before I would finally use the power button to hard reset the system.

I reinstalled K-Lite Codec Pack yesterday and then used their media player classic today to troubleshoot with. Instead of completely freezing my system when I moved the window from one screen to the other I got the following fatal error:

"Microsoft Visual C++ Runtime Library

Runtime Error!

Program:...iles\K-Lite Codec Pack\Media Player Classic\mplayerc.exe

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."

I don't know if that sheds any light on the problem, but thought it interesting none the less.

I have attached another blue screen minidump to see if it's any different. I believe this was from WMP before I rolled back to the older driver.



So, to me it's looking like a bad set of drivers from Intel. It looks like there's a bad and a worse driver that I have access to. It's too bad too, because the newer driver from Intel has a "scheme" feature making it really fast and easy to switch between using dual monitors and just my laptop.

It would be wrong to assume that the BSOD (which no longer happens) and the 'mplayerc.exe' crash share the same root cause. In fact, it's highly likely that they don't.

I'd like to try to contribute to what you and ZigZag have been doing, but I'm dog tired presently and I need a nap.

My suggestion would be to treat the media player crash as a (bad) codec issue.

haha, oops. It's actually Windows 7 Professional. I keep getting confused between Vista Business and Windows 7 Professional. I got it through the MSDNAA program at my school. I believe they got it on August 6th.

Does the current symptom manifest itself if you temporarily go into "basevideo" mode?

- BCDEDIT /SET VGA ON
- rebooot
- test

(Afterwards, to revert to your standard video driver:

- BCDEDIT /SET VGA OFF
- reboot
)