BSOD, Seems to be when i'm playing WoW/Listening to music...

Page 2 of 2 FirstFirst 12

  1. Posts : 11
    Windows 7 Professional 64 Bit
    Thread Starter
       #11




    Thought that'd be the best way to reply

    I Got the blue screen error PFN_LIST_CORRUPT whilst playing warcraft

    I reinstalled windows 7, sp1, new gpu drivers etc. even updated Directx

    the 2 dump files attached are from the fresh install

    The second blue screen was DRIVER_IRQL.....

    Edit: I'm currently typing this from my laptop, i decided to shut down my pc to spare myself from the impending crashes awaiting instruction!
    It's installing updates automatically now... 4 of 58 since it's fresh install.
    I'm not sure if this is a bad thing or not in terms of resolving the problem
    as i've got the latest driver for Mobo, GPU, mouse, etc from their respective websites and hope that windows doesn't overwrite anyof these.

    Arg heads hurting now.

    EDIT: after updates, resumed to play, and got System Service Exception blue screen.
    the computer is staying off until i have a solution :P
    Last edited by dakers89; 11 Jan 2012 at 21:25.
      My Computer


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

    Remember the ASACPI.sys driver from before - it's back to the 2005 version (which causes BSOD's) Please update it with the AISuite software

    Please uninstall the AMD OverDrive driver ( AODDriver2.sys ). You'll have to remove the AMD Vision Control Center using the AMD uninstall manager in order to get rid of it.

    The networking driver from your chipset drivers ( nvm62x64.sys ) dates from 2008. Please update the chipset drivers from the nVidia website ( NVIDIA DRIVERS 15.49 WHQL )

    So, so far we've discovered that the BSOD's are either hardware related, or are related to an unknown driver. The unknown driver issue is less likely than the hardware issue - but is easier to troubleshoot.

    So, if you keep getting BSOD's, try running Driver Verifier according to these directions. If it doesn't reveal a particular driver, then we'll start looking into the hardware problems:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
    BSOD BUGCHECK SUMMARY
    Code:
    
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011212-28860-01.dmp]
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Wed Jan 11 20:23:12.833 2012 (UTC - 5:00)
    System Uptime: 0 days 0:01:11.503
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    BugCheck D1, {7fefb6b15b2, 2, 0, fffff88001b6124a}
    Probably caused by : rdyboost.sys ( rdyboost!SmdMdlCopy+16 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD1_rdyboost!SmdMdlCopy+16
    Bugcheck code 000000D1
    Arguments 000007fe`fb6b15b2 00000000`00000002 00000000`00000000 fffff880`01b6124a
    BiosVersion = 1102   
    BiosReleaseDate = 02/28/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011212-37393-01.dmp]
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Wed Jan 11 20:15:24.140 2012 (UTC - 5:00)
    System Uptime: 0 days 2:00:11.889
    Probably caused by : memory_corruption ( nt!MiBadRefCount+4f )
    BUGCHECK_STR:  0x4E_9a
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x4E_9a_nt!MiBadRefCount+4f
    Bugcheck code 0000004E
    Arguments 00000000`0000009a 00000000`00005138 00000000`00000002 00000000`00000000
    BiosVersion = 1102   
    BiosReleaseDate = 02/28/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  3. Posts : 11
    Windows 7 Professional 64 Bit
    Thread Starter
       #13

    Hi again

    so i did what was asked, installed all the relevant drivers. and ran verifier

    Began playing, all fine, no blue screen whilst playing...

    After about a couple hours i logged off. literally as soon as the game closed i received blue screen without a general reason.

    managed to upload the dump files.

    This is becoming a vicious circle, probably going to result in me launching this machine out of the window and putting my hand in my pocket for a new one!
      My Computer


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

    The first BSOD is a Driver Verifier memory dump and it blames mcdbus.sys - a component of Magic ISO
    Uninstall it please.

    It still shows ASACPI.sys as being from 2005.
    Download the attachment that I attached
    Unzip it (Extract all files)
    Open the folder
    Double click on the AsAcpiIns.exe file.
    That should install the ASACPI.sys driver from 2009

    Go to C:\Windows\System32\drivers and check the date on it there.

    BSOD BUGCHECK SUMMARY
    Code:
    
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011212-20716-01.dmp]
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Thu Jan 12 14:55:48.898 2012 (UTC - 5:00)
    System Uptime: 0 days 0:05:49.614
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6061 )
    BUGCHECK_STR:  0x1a_411
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+6061
    Bugcheck code 0000001A
    Arguments 00000000`00000411 fffff6fc`5000e5d8 8bf00001`ce8c6882 fffff6fc`5000f5d9
    BiosVersion = 1102   
    BiosReleaseDate = 02/28/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011212-25194-01.dmp]
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Thu Jan 12 14:48:33.027 2012 (UTC - 5:00)
    System Uptime: 0 days 5:39:15.353
    *** WARNING: Unable to verify timestamp for mcdbus.sys
    *** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
    Probably caused by : mcdbus.sys ( mcdbus+36823 )
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    BUGCHECK_STR:  0xc4_81
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xc4_81_VRF_mcdbus+36823
    Bugcheck code 000000C4
    Arguments 00000000`00000081 fffffa80`0a356de0 00000000`0000008a 00000000`00000000
    BiosVersion = 1102   
    BiosReleaseDate = 02/28/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011212-24133-01.dmp]
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Thu Jan 12 08:49:13.170 2012 (UTC - 5:00)
    System Uptime: 0 days 0:03:26.840
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )
    BUGCHECK_STR:  0x19_3
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  csrss.exe
    FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+cbb
    Bugcheck code 00000019
    Arguments 00000000`00000003 fffffa80`070dc7b0 fffffa80`070dc7b0 fffffa80`070dd7b0
    BiosVersion = 1102   
    BiosReleaseDate = 02/28/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011212-31278-01.dmp]
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Wed Jan 11 21:08:29.617 2012 (UTC - 5:00)
    System Uptime: 0 days 0:06:38.912
    *** WARNING: Unable to verify timestamp for $MftMirr
    Probably caused by : ntkrnlmp.exe ( nt!RtlCompareUnicodeStrings+44 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x3B_nt!RtlCompareUnicodeStrings+44
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff800`02d6d344 fffff880`07d4c6b0 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  5. Posts : 11
    Windows 7 Professional 64 Bit
    Thread Starter
       #15

    Ah it would seem that running the AI suite alone didn't install the 2009 driver

    Located the .exe within the folder and checked in system32/drivers and found it to be updated to 2009 now.

    No BSOD yet. fingers crossed!
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 11:26.
Find Us