ataport.sys BSOD caused by WMP  

So, I have done a clean install of Win7 RTM. I installed everything back onto my computer that I needed. I have tried to watch DVD's using Windows Media Player. I describe my results/progress/bsod:

Try #1: I click the autoplay button to watch dvd using Windows Media Player. Complete and entire freeze of system (no mouse, no keyboard...nothing until I hard power down laptop.

Try #2: I try click the autoplay button to watch dvd in VLC Media Player. I watched some of the dvd in fullscreen. I got out of fullscreen to do something and dragged the window slightly to the right; complete and entire freeze of system. I then un-installed K-Lite Codec Pack, thinking it to be a bad codec somewhere.

Try #3: I try again in Windows Media Player with autoplay button and it loads the DVD and plays it. If I get out of fullscreen mode and move the windows it freezes the entire system (as mentioned before).

Try #4: I try again in Windows Media Player (I believe this time with or without autoplay button) and when I tried to move the player at all I got a BSOD.

Try #5: Beginning to get a little frustrated at not being able to move a window while playing a DVD. I didn't touch the window and no problems. I watched several other videos off of the dvd without problems.

Try #6: I dragged the window tonight while in WMP because it seemed to be improving in capability. It made it over to the right computer monitor and stuttered before continuing to play (nice). Then when dragging back over to my external monitor, BSOD.

Yikes! I have tried to analyze the MEMORY.DMP files left behind in my system with the Windows Debugger program. All I can find relevant is that it is caused by ataport.sys and wmplayer.exe. The !analyze -v results are attached below.

I'm using Mobile Intel 915GM Express Chipset Family with the latest driver (6.14.10.4764). Dell hasn't made any updates for firmware for my DVD player either (Sony DVD+-RW DW-Q58A ATA Device).

I'm baffled at why ataport.sys would appear to be causing the problem--that's not a third party driver from what I can tell (it's from MS).

bwood.

first could you upload the dump file. there are some extra routines I can run on it that I cant do with the text file. the text file did tell me what I could run so good idea. the ataport.sys file is an ide driver (dvd player maybe?) and from this I cant tell if the ataport caused the WMP double fault or the other way around. the other thing I noticed is 2 gigs of ram. Im wondering if WMP/VLC in a window then moved is causing a page file call. Anyway I know it annoying but we will be more than happy to help

Ken

Great, thank you for helping!

So, I ran the Windows Memory diagnostic (before booting into Windows) and it came up with no errors. I am (sadly) using AVG Free for antivirus. I have Symantec Endpoint Client Protection, but it isn't yet compatible with Windows 7 so I can't install it (I have one install file since it's distributed from my university and can't try to install Liveupdate first). AVG is really slowing my computer down, uggh.

So, my memory dump file is originally 175 MB, but zipped to 45.5 MB. It can be found at:

http://www.et.byu.edu/~bwood720/MEMORY_dump.zip


Thanks!

BW

nothing much has changed. WMP caused the ataport driver to double fault. And again its a memory double fault. How much ram do you have? Im still running routines on it to see if there is anything more detailed.


Edit: what video driver do you have? there is a hardware interupt for this file igxpmp32.sys, which is an intel video accelerator.

ken

All I could find in services.msc for AVG was "AVG Free8 Watchdog"--I found no AVG Link Scanner.

I have 2 GB RAM (the maximum for my laptop). My video driver is for a Mobile Intel 915GM Express Chipset. It is version 6.14.10.4764 (I believe it's the latest).

bwood720 said:

All I could find in services.msc for AVG was "AVG Free8 Watchdog"--I found no AVG Link Scanner.

I have 2 GB RAM (the maximum for my laptop). My video driver is for a Mobile Intel 915GM Express Chipset. It is version 6.14.10.4764 (I believe it's the latest).

Ok well thats the max ram, thats it. I would think that since there was an intel video accelerator in the last dump, that you might want to see if the video driver is still installed and working correctly.


since WMP is involved i all the dumps, if I were you I might try a different player to see if without it the BSOD's stop. if you do VLC is a decent player. there are many things we can do to find the cause but you cant change ram, video, audio, etc.

let me know what you would like to do


ken

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.