BSODs While Gaming (Different Driver Errors each time) [ntoskrnl.exe]

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 7 64 bit Home Premium
       #1

    BSODs While Gaming (Different Driver Errors each time) [ntoskrnl.exe]


    Hi, this is my first time asking for help, reading through most of the similar posts on this issue led me nowhere, so I am hoping someone with more expertise can have a look and see what's wrong. I'll try and be as detailed as possible, so apologies in advance if this is too much info.

    I have attached the Dmp files as well as the system health report to this post, although I think some of the crashes on that Dmp list are from a while back, hopefully you can refer only to the ones that have happened off late.


    The issue:
    It seems to be that everytime I run a game, within the first 20 odd minutes of running it (Either full screen or windowed mode), I get a BSOD and crash. Many of the crashes have not been picked up by the dump file, however from memory, amongst the usual drivers suggested are ntoskrnl.exe, hal.dll. Most of the time the BSOD locks up the PC before the crash file can be logged, and I have to force a restart myself. The BSOD's don't have any particular pattern, as in, they occur sometimes for a bunch of hours, making any sort of gaming impossible, but then can run fine for up to 4-5 days, before coming back once again with a vengeance for a few hours.
    I can be browsing, watching videos/music for hours and never have an issue, but within a few minutes of loading a game (less than 20 most of the time), I'll get the bluescreen. I've tested on multiple games (Warhammer/WoW/Skyrim)



    Troubleshooting steps I have taken:

    1: Got a fresh HDD, fresh install of Windows 7 on it. Had the first crash about 40 minutes after installing the game on the new HDD.

    2: Memtest, came clean. Replaced RAM for testing anyways, didn't help.

    3: Stress tested my GPU using Furmark. Ran perfectly for 30 minutes or so with no issues before I ended the test. Nothing abnormal during those tests.

    4: Ran Driver Verifier. This produced interesting results. I turned Verifier on for EVERY driver (including Microsoft ones), restarted the computer, and it would chain crash right at the Windows 7 loading screen (About 2 seconds after the BIOS screen was gone). I'd get a hint of a blue screen but the PC would restart instantly for me to have a look at the error, and I don't think these crashes were logged in the dump file. I had to force into Safe mode, turn off verifier, and restart to get back on.

    5: I have updated my video drivers to the latest version, although this didn't seem to help either.

    Computer Specs:
    AMD 965 x4 3.40Ghz
    8GB Ram
    Windows 7 OEM Home Premium
    HD5750 1gb GPU

    Any advice on what I should do? I kind of have a feeling it has to be corrupted drivers, maybe something to do with my Mouse/Keyboard (Razer Lachesis/ Logitech G110) but I'm not sure. Maybe after going through those logs you can figure out something a novice like me cannot.

    Thankyou once again for any help you might be able to provide,
    Jayrawr
      My Computer


  2. Posts : 5,405
    Windows 7 Ultimate 64bit SP1
       #2

    Hi.

    Remove avg from your system.

    Download,install and use Anti-Malware, Virus, Spyware Protection | Microsoft Security Essentials with windows firewall.

    Update software\driver for your Razer Lachesis Mouse.

    Razer Support


    Finish and pot back.
      My Computer


  3. Posts : 9
    Windows 7 64 bit Home Premium
    Thread Starter
       #3

    Hi, I am installing that now..

    But after the last BSOD, i got 2 crashes in a row on Windows startup (After i logged in and everything on the desktop loaded)

    Here's a brief overview of the errors :


    On Fri 9/12/2011 2:22:01 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121011-18813-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
    Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x341, 0x34300000282)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Fri 9/12/2011 2:22:01 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x341, 0x34300000282)
    Error: MEMORY_MANAGEMENT
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

    Any advice on what this new error might be? I do want to point out that every BSOD earlier has had a different error message, this one's new. Do you want the dump files for these crashes as well? I wasn't in game for either of them, was simply logging on to Windows.

    Will update once I do what you've suggested above, although do keep me updated if this new data suggests something else.
      My Computer


  4. Posts : 5,405
    Windows 7 Ultimate 64bit SP1
       #4

    The most recent crash\bsod points to Razer Lachesis Mouse.

    Update the software\driver and post back.

    Also disable Driver Verifier.
      My Computer


  5. Posts : 9
    Windows 7 64 bit Home Premium
    Thread Starter
       #5

    Hi, done all you've said. Installed new drivers for the mouse, yet it crashes again during the first 20 minutes of gameplay, despite working perfectly for an hour and a bit while MSE did a full scan(No threats)

    Then when I restarted, I got these back to back crashes on the login screen:


    On Fri 9/12/2011 4:33:57 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x1E95)
    Bugcheck code: 0x24 (0xC08A2, 0x0, 0x0, 0x0)
    Error: NTFS_FILE_SYSTEM
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates a problem occurred in the NTFS file system.
    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 which cannot be identified at this time.


    On Fri 9/12/2011 4:32:33 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121011-34023-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
    Bugcheck code: 0x44 (0xFFFFFA8009D75810, 0xEAE, 0x0, 0x0)
    Error: MULTIPLE_IRP_COMPLETE_REQUESTS
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
    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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    Any suggestions?
      My Computer


  6. Posts : 9
    Windows 7 64 bit Home Premium
    Thread Starter
       #6

    Another set of crashes, this time clearly because of my mouse. Is this the cause of all the crashes or is it just a coincidence?


    On Fri 9/12/2011 5:04:23 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121011-22557-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF800030B20B4, 0x0, 0x8)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Fri 9/12/2011 5:04:23 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: lachesis.sys (Lachesis+0x1081)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF800030B20B4, 0x0, 0x8)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\drivers\lachesis.sys
    product: Lachesis USB Optical Mouse
    company: Razer (Asia-Pacific) Pte Ltd
    description: Lachesis USB Optical Mouse Driver
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: lachesis.sys (Lachesis USB Optical Mouse Driver, Razer (Asia-Pacific) Pte Ltd).
    Google query: lachesis.sys Razer (Asia-Pacific) Pte Ltd KMODE_EXCEPTION_NOT_HANDLED





    I'll upload the mini dumps as well, maybe it has some clues.
      My Computer


  7. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #7

    Jayrawr said:
    Another set of crashes, this time clearly because of my mouse. Is this the cause of all the crashes or is it just a coincidence?


    On Fri 9/12/2011 5:04:23 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121011-22557-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF800030B20B4, 0x0, 0x8)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Fri 9/12/2011 5:04:23 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: lachesis.sys (Lachesis+0x1081)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF800030B20B4, 0x0, 0x8)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\drivers\lachesis.sys
    product: Lachesis USB Optical Mouse
    company: Razer (Asia-Pacific) Pte Ltd
    description: Lachesis USB Optical Mouse Driver
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: lachesis.sys (Lachesis USB Optical Mouse Driver, Razer (Asia-Pacific) Pte Ltd).
    Google query: lachesis.sys Razer (Asia-Pacific) Pte Ltd KMODE_EXCEPTION_NOT_HANDLED





    I'll upload the mini dumps as well, maybe it has some clues.
    Yes, upload these dumps. :)
      My Computer


  8. Posts : 9
    Windows 7 64 bit Home Premium
    Thread Starter
       #8

    Here you go, I've uploaded the files.

    In the meantime, I have completely uninstalled the Lachesis drivers/software, so it's running as a default mouse now.

    I haven't experienced any blue screens, hence no logs, but since this change, the computer's just been rebooting itself, after going blank for a second. This has happened twice, once in a game, and once outside of it, so I feel it's random.
      My Computer


  9. Posts : 9
    Windows 7 64 bit Home Premium
    Thread Starter
       #9

    Bump! Any help? Did a clean Windows 7 reinstall, only installed my graphics card driver, got this:
    On Sat 12/10/2011 10:01:59 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121011-24897-01.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag+0x39F560)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF88004A3C560, 0xFFFFF88005EE1A98, 0xFFFFF88005EE12F0)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon Family
    company: ATI Technologies Inc.
    description: ATI Radeon Kernel Mode Driver
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
    Google query: atikmdag.sys ATI Technologies Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
      My Computer


  10. Posts : 10
    Windows 7 Home Premium 64-bit
       #10

    Look at the blue text in this article:
    Possible Solution to ATIKMDAG Driver Crash

    also state your graphics card.
      My Computer


 
Page 1 of 2 12 LastLast

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