BSOD in League of Legends


  1. Posts : 5
    California
       #1

    BSOD in League of Legends


    Is Windows 7 . . .
    - x64

    full retail

    kingston hyper x blu 1600 ddr3 2x2 gb
    western digital 160gb hd
    amd phenom2 x3
    nvidia gtx560

    - i've slowly been swapping out pieces, oldest piece being my hardrive
    OS installation is probably 5 months old. i usually reformat twice a year

    as the title says i get BSODs in a video game called League of Legends. most of the time its just a hang up, but the times that it does BSOD, it says Memory_management and System_Service_Exception. anyhelp on this would be VERY MUCH APPRECIATED!!!!!!
      My Computer


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

    No DMPS included in upload

    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 : 5
    California
    Thread Starter
       #3

    I've rebooted into safemode with networking.after allowing the minidump feature... but I've navigated to c/windows / but I could not find a minidump folder...what would be the correct steps to take now
    ?
      My Computer


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

    daintfish said:
    I've rebooted into safemode with networking.after allowing the minidump feature... but I've navigated to c/windows / but I could not find a minidump folder...what would be the correct steps to take now
    ?
    Have you searched for *.DMP?
      My Computer


  5. Posts : 5
    California
    Thread Starter
       #5

    There aren't any dmp files in my windows folder...unless you meant you windows search? And I know I set the dump files to.save here... should I set the default to a different location?
      My Computer


  6. Posts : 5
    California
    Thread Starter
       #6

    Also after doing a hard reset after a couple of the crashes the PC said that windows hadfailed to start up and then took me to the boot repair screen? Throwing this in there cause I don't know how relevant this info is
      My Computer


  7. Posts : 5
    California
    Thread Starter
       #7

    ok i've figured out that if i save the dump in a different location so i can find the files. i've attatched the dump here...sorry for the late reply, im not very good with computers
    Last edited by daintfish; 14 Mar 2012 at 09:03. Reason: adding dumps
      My Computer


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

    daintfish said:
    ok i've figured out that if i save the dump in a different location so i can find the files. i've attatched the dump here...sorry for the late reply, im not very good with computers


    These crashes were caused by memory corruption/exception (probably a driver).
    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 00:06.
Find Us