BSOD and frequent crashes when playing League of legends game

Mihuss

New member
Local time
4:32 PM
Messages
3
Whenever i play this game i get frequent BSOD/Crashes with the prompt that the application has stopped working. I had problems with BSOD before but resolved them by changing the RAM sticks to the correct positions.
I only recently started playing this game and i only get the crashes when playing it.

[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Tue 09/04/2013 08:49:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040913-16988-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (0xFFFFF88005211022)
Bugcheck code: 0x50 (0xFFFFF8800894C280, 0x0, 0xFFFFF88005211022, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Thanks!

[/FONT]
 

My Computer My Computer

At a glance

Windows 7 Professional 64 bit
OS
Windows 7 Professional 64 bit
Code:
[COLOR="Red"]BugCheck 50[/COLOR], {fffff8800894c280, 0, fffff88005211022, 0}

Could not read faulting driver name
Probably caused by : dxgkrnl.sys ( dxgkrnl!COREACCESS::AcquireShared+a2 )

Code:
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

A invalid memory address was referenced, and this case was the non-paged pool region, which is reserved for Kernel Mode processes.

Update:

Code:
0: kd> [COLOR="SeaGreen"]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff880`058d1000 fffff880`0636f000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="red"]Sat Dec 29 06:47:52 2012[/COLOR] (50DE9218)
    CheckSum:         00A7F96C
    ImageSize:        00A9E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Version: 314.22
Release Date for Desktops and Notebooks : March 25th 2013
In Device Manager: 9.18.13.1422
  1. Download Driver
  2. Start :orb: Type: Device Manager
  3. Expand Display Adapters
  4. Right-Click Driver Name, Uninstall
  5. Reboot
  6. Run Driver Sweeper
  7. Reboot
  8. Install Downloaded Driver
Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

Driver Sweeper:
Remove:

Code:
Start Menu\Programs\PC TuneUp Tools

Windows 7 doesn't require any programs which make changes to the operating system and registry, these programs tend to cause problems by modifying and deleting files.
Remove:

Code:
Start Menu\Programs\Alcohol 120%

Alcohol 120% uses a driver called sptd.sys, which is known to cause BSODs with Windows 7.

Reduce the number of programs at startup, to avoid any driver or program conflicts:
 

My Computer My Computer

Computer type
Laptop
I updated my nvidia drivers like you said and removed pctuneuptools and alcohol. So far i havent had a bsod since but now the game keeps on frequently crashing and windows prompts me to close the program.
I have attached the dump analysis.

Thanks for your help!
 

My Computer My Computer

At a glance

Windows 7 Professional 64 bit
OS
Windows 7 Professional 64 bit
Code:
[COLOR="Red"]BugCheck 24[/COLOR], {1904fb, fffff8800b13f408, fffff8800b13ec60, fffff80002c871d3}

Probably caused by : ntkrnlmp.exe ( nt!ExQueryDepthSList+3 )

Code:
Usual causes:  Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

I found this BSOD, which occurred at 12:52, I'm sure this wasn't in the folder when I first checked :huh:

Run some hard-drive diagnostics and follow these steps:
Find your hard-drive manufacturer and run their tests.

Additional Tests:
Post a screenshot of Crystal Disk Info summary:
writhziden said:
If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:
Use this command with Disk Check:

Code:
chkdsk C: /f /r

Update your System Specifications with Speccy, and then copy this information into your System Specifications: Go to your UserCP, and then select Edit System Spec in the left pane. Copy the information from Speccy into the required fields. These System Specifications will then follow your every post.
 

My Computer My Computer

Computer type
Laptop
Back
Top