BSOD with iTunes and WMP


  1. Posts : 2
    Windows 7
       #1

    BSOD with iTunes and WMP


    Hello, i thought i would join up and see if i could get any help with this stupid BSOD i keep getting.

    To start off, i am running Windows 7 RC Build 7100 x64.
    I have got 2 HDDS, with multiple partitions. My music is stored on my primary HDD, with the OS, on a separate partition. My video is stored on another HDD.

    Now, when i am playing music through iTunes, and i decide to load up a video(in WMP or MP Classic) i get a BSOD instantly. The OS hangs for about a second then up comes the BSOD. Now i have noticed this happens whilst my iTunes is playing music, but it also happens when it is sitting idle in the tray, not playing music.

    Its very frustrating!!

    If anyone has any help, or knows where i should do to seek out the cause, i would be very grateful. Also if anyone knows where i should look for the report files on the crash?

    Thanks,

    Adam
      My Computer


  2. Posts : 125
    Win 7 RC
       #2

    Welcome to the forum mimminito. Can you upload the memory dumps that should be in C:\Windows\minidump and can you fill in your system specs.
      My Computer


  3. Posts : 2
    Windows 7
    Thread Starter
       #3

    sure, here are the dumps, and ill update specs now
      My Computer


  4. Posts : 125
    Win 7 RC
       #4

    Memory dump shows:

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

    Loading Dump File [C:\Windows\Minidump\Minidump\051409-23680-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\symbols*Symbol information
    Executable search path is:
    Windows 7 Kernel Version 7100 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
    Machine Name:
    Kernel base = 0xfffff800`02c52000 PsLoadedModuleList = 0xfffff800`02e8be90
    Debug session time: Thu May 14 23:34:49.930 2009 (GMT+1)
    System Uptime: 0 days 13:31:38.771
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck E3, {fffffa8004ddabf0, fffffa8004622990, 0, 2}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+19759 )
    Followup: MachineOwner
    ---------
    3: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    RESOURCE_NOT_OWNED (e3)
    A thread tried to release a resource it did not own.
    Arguments:
    Arg1: fffffa8004ddabf0, Address of resource
    Arg2: fffffa8004622990, Address of thread
    Arg3: 0000000000000000, Address of owner table if there is one
    Arg4: 0000000000000002
    Debugging Details:
    ------------------

    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    BUGCHECK_STR: 0xE3
    PROCESS_NAME: explorer.exe
    CURRENT_IRQL: 0
    LAST_CONTROL_TRANSFER: from fffff80002d1ee36 to fffff80002cd0f80
    STACK_TEXT:
    fffff880`094f3658 fffff800`02d1ee36 : 00000000`000000e3 fffffa80`04ddabf0 fffffa80`04622990 00000000`00000000 : nt!KeBugCheckEx
    fffff880`094f3660 fffff880`01227802 : 00000000`0000ffff 00000000`00000000 fffffa80`0a323510 11de4066`0f817ef2 : nt! ?? ::FNODOBFM::`string'+0x19759
    fffff880`094f36c0 fffff880`01228304 : fffffa80`0a323510 fffff8a0`00000001 00000000`00000000 fffffa80`07caf010 : Ntfs!NtfsCleanupIrpContext+0x1d2
    fffff880`094f3710 fffff880`0135dd0c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0a323510 : Ntfs!NtfsExtendedCompleteRequestInternal+0xd4
    fffff880`094f3750 fffff880`0132950f : fffff880`094f39d0 00000000`00000000 fffffa80`0a323510 fffffa80`0a323510 : Ntfs!NtfsCreateOrGetObjectId+0x56c
    fffff880`094f3840 fffff880`012f26ad : fffffa80`0a323510 00000000`00000000 00000000`00000001 00000000`00000000 : Ntfs! ?? ::NNGAKEGL::`string'+0x1d7ac
    fffff880`094f3880 fffff880`00d9627f : fffff880`094f39c0 fffffa80`07caf010 fffffa80`06a0c001 fffffa80`0a323510 : Ntfs!NtfsFsdFileSystemControl+0x13d
    fffff880`094f3920 fffff880`00db475e : fffffa80`04dcbde0 fffffa80`0ab26f20 fffffa80`07caf000 fffffa80`07caf010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    fffff880`094f39b0 fffff800`02fcf300 : fffffa80`07caf301 fffff880`094f3ca0 fffffa80`0ab26f20 fffffa80`07caf010 : fltmgr!FltpFsControl+0xee
    fffff880`094f3a10 fffff800`02f91f56 : 00000000`00000101 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5f0
    fffff880`094f3b40 fffff800`02cd01d3 : 00000000`00000f90 00000000`0897cf48 00000000`0897cf60 00000000`00000068 : nt!NtFsControlFile+0x56
    fffff880`094f3bb0 00000000`76e0e86a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0897cee8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e0e86a

    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+19759
    fffff800`02d1ee36 cc int 3
    SYMBOL_STACK_INDEX: 1
    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+19759
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME: ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 49ee9439
    FAILURE_BUCKET_ID: X64_0xE3_nt!_??_::FNODOBFM::_string_+19759
    BUCKET_ID: X64_0xE3_nt!_??_::FNODOBFM::_string_+19759
    Followup: MachineOwner
    ---------


    The problem appears to be caused by either a driver or an application. I would suggest uninstalling apps such as itunes, one at a time to see if the problem goes away. Check device manager as well to ensure there are no conflicts or unknown devices.
      My Computer


  5. Posts : 5,705
    Win7 x64 + x86
       #5

    I had a similar issue at work not long ago. It came from installing the 32 bit version of iTunes on a 64 bit system. The fix was to uninstall the 32 bit version, then install the 64 bit version.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:46.
Find Us