Frequent BSOD While Gaming - 0x0000003b

[GrapeJam]

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

 

[GrapeJam]

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

 

[koolkat77]

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

http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Run a System file check (SFC): http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Run Disk Check on your Hard Drive(s): http://www.sevenforums.com/tutorials/433-disk-check.html

Update the driver to its latest version if available.

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: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

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

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


Let us know the results.

Bugcheck Summary:

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 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[GrapeJam]

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.

 

[GrapeJam]

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.

 

[GrapeJam]

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

 

[koolkat77]

Do you get BSod's in safe mode?
Start your computer in safe mode - Microsoft Windows Help

 

[GrapeJam]

So far, no.

 

[GrapeJam]

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

 

[koolkat77]

Hmm. anything now?

 

[GrapeJam]

Still nothing new. It can run endlessly as long as I don't try to watch any sort of video for too long or play games.

I have been browsing the web for several hours now without a BSOD.

Do you have any suggestions as to what the cause is most likely to be? Perhaps the RAM? I could try to remove one stick at a time and see if this helps.

Or perhaps it is a driver based issue. I did try to update all of my drivers on the HP website yesterday, however I am not very familiar with the process and simply downloaded them and double clicked them to run the setup, perhaps this was not done correctly as you mentioned that a clean install should be performed.

However i'd be shocked to find that it is a driver issue as the laptop is fresh from a factory reset.

Please advise.

 

[koolkat77]

Could you check the temps after 40 minutes/1 hour of watching a video?

 

[koolkat77]

Do a clean install using NVIDIA DRIVERS 314.22WHQL (this is for laptops only); and search for updates for your Broadcom wifi in HP's site

 

[GrapeJam]

Will give both a try and get back to you soon!

 

[GrapeJam]

Ok,

after 40 minutes of video the temperatures tend to hover around 57-61C

Whilst gaming they tend to be 75-80C.

Am restarting my computer now to see if the new drivers have had any effect

 

[Arc]

Ok,

after 40 minutes of video the temperatures tend to hover around 57-61C

Whilst gaming they tend to be 75-80C.

Am restarting my computer now to see if the new drivers have had any effect

Upload a screenshot of the summery tab of Speccy.
Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

 

[GrapeJam]

I'm using the HW Monitor, hopefully this is okay.

Attached is a screenshot of temperatures after gaming for only about 10 minutes. This is also running on one of my power plans that has my CPU capped at 75%.

 

[GrapeJam]

Okay, I think I might have solved the problem. I removed one of my sticks of RAM and have been playing without a BSOD for almost 1 hour now (normally it would BSOD in 10-20 minutes of play).

I will keep playing and see if it blue screens again.

However I have been monitoring my temperature as well and have noticed that at the moment the computer is running extremely hot (95-100C). I'm not an expert on comp temperatures but this seems dangerously hot to me. What are your thoughts?

 

[Arc]

Removing the RAM stick is a good move from your part.

About the temps... yes it is unhealthy. Can you dismantle the computer? A cleaning and re-seating may be helpful here. Clean all the air vents and fan grills. Also remove the old thermal paste to the CPU and apply fresh thermal paste.

It is supposed to reduce the temps.