Frequent BSOD While Gaming - 0x0000003b

Page 1 of 2 12 LastLast

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

    Frequent BSOD While Gaming - 0x0000003b


    Hi,

    Over the last few months i've been experiencing multiple different BSODs as a result of gaming and on occasion streaming online. Many of them seem to be linked to ntoskrnl.exe

    I'm running on an HP Pavilion dv6 Notebook PC that is just over 1 year old. About a month after purchasing the machine I installed my first game on it, that is when I first noticed the BSODs. However they would only seem to occur whilst gaming at first. After experimenting with drivers etc the BSODs became more and more frequent. So I decided to re-install windows and try again. I have re-installed windows twice now and each time it is the same result, my computer is completely fine unless I try to play a game.

    It has lasted multiple days without a BSOD from just performing simple tasks like browsing the web, doing work etc. Yet the minute I open a game it will BSOD within the first 10-20 minutes.

    At first the BSODs would occur much earlier within the game, however after research on the issue it was suggested that it may be a heat issue, so I tried a few different suggestions to bring the heat down, and I must admit that after doing so I can play a game for noticeable longer before a BSOD occurs. But they still occur nontheless...

    My system specs should be listed on my profile and if it helps, the two games I have been trying to play are Assassins Creed: Black Flag and Battlefield 4

    I will attach as many minidumps as I can.

    If anyone can help me you'd be a lifesaver. Please do ask if you require any more information from me!

    Here are the following BSOD's that I have received:

    INTERRUPT_EXCEPTION_NOT_HANDLED - 0x0000003d
    Caused By Driver: SynTP.sys
    Caused By Address: SynTP.sys+3bd8


    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - 0x1000007e
    Caused By Driver: dxgmms1.sys
    Caused By Address: dxgmms1.sys+1e023

    DRIVER_IRQL_NOT_LESS_OR_EQUAL - 0x000000d1
    Caused By Driver: ntoskrnl.exe
    Caused By Address: ntoskrnl.exe+7cd40

    DRIVER_IRQL_NOT_LESS_OR_EQUAL - 0x000000d1
    Caused By Driver: IDSvia64.sys
    Caused By Address: IDSvia64.sys+48d84

    INTERRUPT_EXCEPTION_NOT_HANDLED
    Caused By Driver: HDAudBus.sys
    Caused By Address: HDAudBus.sys+421f

    SYSTEM_SERVICE_EXCEPTION - 0x0000003b
    Caused By Driver: none
    Caused By Address: none

    KMODE_EXCEPTION_NOT_HANDLED - 0x0000001e
    Caused By Driver: ntoskrnl.exe
    Caused By Address: ntoskrnl.exe+7cd10

    SYSTEM_SERVICE_EXCEPTION - 0x0000003b
    Caused By Driver: SYMDS64.SYS
    Caused By Address: SYMDS64.SYS+16964

    KMODE_EXCEPTION_NOT_HANDLED - 0x0000001e
    Caused By Driver: dxgkrnl.sys
    Caused By Address: dxgkrnl.sys+3101

    INTERRUPT_EXCEPTION_NOT_HANDLED - 0x0000003d
    Caused By Driver: ntoskrnl.exe
    Caused By Address: ntoskrnl.exe+7cd40

    IRQL_NOT_LESS_OR_EQUAL - 0x0000000a
    Caused By Driver: ntoskrnl.exe
    Caused By Address: ntoskrnl.exe+75bc0

    SYSTEM_SERVICE_EXCEPTION - 0x0000003b
    Caused By Driver: ntoskrnl.exe
    Caused By Address: ntoskrnl.exe+75bc0

    SYSTEM_SERVICE_EXCEPTION - 0x0000003b
    Caused By Driver: ntoskrnl.exe
    Caused By Address: ntoskrnl.exe+75bc0

    PAGE_FAULT_IN_NONPAGED_AREA - 0x00000050
    Caused By Driver: ndis.sys
    Caused By Address: ndis.sys+230a7
    Last edited by GrapeJam; 06 Jan 2014 at 00:04. Reason: Addition information
      My Computer


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

    I have just had another BSOD while watching videos online.

    PAGE_FAULT_IN_NONPAGED_AREA
    Error code 0x00000050

    In BlueScreenViewer it has highlighted the following:
    Caused By Driver: ndis.sys
    Caused By Address: ndis.sys+230a7

    I hope the BSOD's don't start becoming more frequent
      My Computer


  3. Posts : 15,026
    Windows 10 Home 64Bit
       #3

    Welcome to the Forum.

    Norton is a known cause to Blue screens. Please remove it for testing purpose. Use Microsoft Security Essentials.

    Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

    Microsoft Security Essentials - Free Antivirus for Windows

    Malwarebytes - Free

    Good and Free system security combination.

    Reduce items at start-up: Startup Programs - Change

    Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

    Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

    ESET online scanner: Free Online Virus Scanner | ESET

    Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

    Run Disk Check on your Hard Drive(s): Disk Check

    Update the driver to its latest version if available.

    Code:
    dadder.sys Thu Aug 2 15:33:03 2007
    DeathAdder Mouse driver
    Driver Reference Table - dadder.sys

    Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

    Uninstall Bloatware using Revo Uninstaller Free.
    Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

    Check for heating issues using Speccy or HWmonitor

    Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums

    Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software: CrystalDiskInfo - Software - Crystal Dew World

    Run a Hard Drive test: https://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html


    Let us know the results.

    Bugcheck Summary:
    Code:
    BugCheck 3B, {c0000005, fffff80002ee9b97, fffff8800d8d1be0, 0}
    Probably caused by : ntkrnlmp.exe ( nt!IopDequeueIrpFromThread+7 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    BugCheck 3B, {c0000005, fffff8000300d123, fffff8800e0968e0, 0}
    Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    BugCheck A, {48000789, 2, 0, fffff80002ead058}
    Probably caused by : memory_corruption ( nt!MiFreeWsleList+3d8 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    BugCheck 3D, {fffff880033280d0, 0, 0, fffff80002e7ab79}
    Probably caused by : ntkrnlmp.exe ( nt!KiInterruptDispatch+169 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    BugCheck 1E, {ffffffffc0000005, fffff80002eba29a, 1, 12}
    Probably caused by : hardware ( win32k!NtGdiCreateDIBSection+118 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    BugCheck 3B, {c000001d, fffff80002ea9736, fffff880095c7aa0, 0}
    Probably caused by : hardware ( nt!MiAllocatePagedPoolPages+c5a )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    BugCheck 1E, {0, 0, 0, 0}
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    BugCheck 3B, {c0000005, fffff80002fbd1cf, fffff88003034da0, 0}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    BugCheck 3D, {fffff8800a373020, 0, 0, fffff88004e5a21f}
    Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::Isr+2ff )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    BugCheck D1, {fffffa8018577580, 2, 0, fffff8800a746d84}
    Probably caused by : IDSvia64.sys ( IDSvia64+48d84 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    BugCheck D1, {4f444600, 2, 1, fffffa80116a41a0}
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    BugCheck 1000007E, {ffffffffc0000005, fffff88004f8fe49, fffff8800408c568, fffff8800408bdc0}
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    BugCheck 3D, {fffff8800da76ef0, 0, 0, fffff88003018bd8}
    Probably caused by : SynTP.sys ( SynTP+3bd8 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      My Computer


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

    Thank you for the quick response Koolkat77, I'm glad to be in your hands.

    I saw some of your other posts and am currently attempting your suggestions. Will get back to you as I progress.
      My Computer


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

    Ok,

    I have downloaded the new driver, removed as much bloatware as possible, and followed as many of the instructions you have given as possible. However I am still getting BSODs.

    I have noticed that they only occur when I try to either play games or watch videos, streams etc. I do not get BSODs while operating in Safe Mode (from what I have noticed)

    I've uploaded a few files and screenshots in the attached folder.

    Please do let me know if you need any more information.
      My Computer


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

    I should also mention the BSOD I received after following your instructions:

    KMODE_EXCEPTION_NOT_HANDLED - 0x0000001e
    Caused By Driver: hal.dll
    Caused By Address hal.dll+7b7f

    Files highlighted in red in BlueScreenView:
    - hal.dll
    - ndis.sys
    - ntoskrnl.exe

    Attached is a minidump file
      My Computer


  7. Posts : 15,026
    Windows 10 Home 64Bit
       #7
      My Computer


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

    So far, no.
      My Computer


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

    Although I am unable to play games/stream video from safe mode so this could be why.
      My Computer


  10. Posts : 15,026
    Windows 10 Home 64Bit
       #10

    Hmm. anything now?
      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 04:00.
Find Us