BSOD playing League of Legends, error 0x000000d1


  1. Posts : 2
    Windows 7 x64
       #1

    BSOD playing League of Legends, error 0x000000d1


    Been getting a BSOD playing League of Legends as the title says, here's the dump info.



    Dump File: 030312-13665-01.dmp
    Crash Time: 3/3/2012 1:20:32 PM
    Bug Check String: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code: 0x000000d1
    Parameter 1: fffff800`47ea3f5e
    Parameter 2: 00000000`0000000d
    Parameter 3: 00000000`00000008
    Parameter 4: fffff800`47ea3f5e
    Caused by Driver: ntoskrnl.exe
    Caused by Address: ntoskrnl.exe+7cc40
    File Description: NT Kernel & System
    Product: Microsoft® Windows® Operating System
    Company: Microsoft Corporation
    File Version: 6.1.7601.17640 (win7sp1_gdr.110622-1506)
    Processor: x64
    Crash Addressntoskrnl.exe+7cc40
    Full Path: C:\Windows\Minidump\030312-13665-01.dmp
    Processor Count: 8
    Major Version: 15
    Minor Version: 7601
    Dump File Size: 276,176

    This doesn't happen everytime, but it's happening enough to irritate me to no end.

    edit: Zip attached, can't believe I forgot it
    Last edited by Waylandyr; 03 Mar 2012 at 15:06. Reason: Attached Minidump zip
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2



    We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

    If you are overclocking STOP

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    *If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
      My Computer


  3. Posts : 2
    Windows 7 x64
    Thread Starter
       #3

    Updated OP with the DMP file.
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    Waylandyr said:
    Updated OP with the DMP file.
    Three different causes. To find which is the underlying cause run these tests.



    Please run these two tests to verify your memory and find which driver is causing the problem.


    * If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!

    * If you have raid update its Driver.




    Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    Driver verifier

    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.

    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.
      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 04:06.
Find Us