Frequent BSODs While Gaming

Hi,

I have an HP pavilion dv6 notebook PC that I purchased roughly 1 year ago. A month or two after I purchased the laptop, I installed my first game on it which is when the BSODs started occurring. I have re installed Windows on the machine several times but no matter what I do, I get the same result, whenever I try to play a game, a few minutes in I will get a BSOD.


I have tried installing new drivers, however I'm not too sure whether I did so correctly. I went to the HP support website, found my machine, downloaded all the driver files and double clicked them. Some required a setup window, some didn't.


I will post my computer specifications below and my minidump files in the next 2-3 posts. I will be so grateful if anyone is able to help me!

Computer Specs:

Model: HP Pavilion dv6 Notebook PC

Processor: Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz 2.40GHz

Installed Memory (RAM): 16 GB (15.9 usable)

OS: Windows 7 Home Premium 64-bit

GPU: Nvidia GeForce GT 650M + 2GB
Intel HD Graphics 4000



:major

 

Here are the next 5 minidump files.

 

Three more

 

There was some sort of error with my last attachments

Please find all the necessary information in the attached file

 

I've had a quick look at some of your minidumps today; all I found that the stop code is IRQL_NOT_LESS_OR_EQUAL, but it doesn't indicate what driver is causing it.

The graphics driver is often the most suspect, but I see from your dxdiag list that you have the latest available driver for your Intel(R) HD Graphics 4000.

I will have another look at the dumps tomorrow; I will let you know if I find any additional information.

 

Update the drivers for your Razer Death Adder mouse (if you can, Razer don't offer updates for long) or remove it and uninstall it completely during testing.

That mix of BSODs makes me want to rule out RAM first. Test with MemTest86+ from a bootable USB stick for at least 8 full runs (or until you see an error before then), details here.

Code:

[font=lucida console]
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 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

SYSTEM UP-TIME

Code:

[font=lucida console]
System Uptime: 0 days 0:33:48.731
System Uptime: 0 days 9:24:06.773
System Uptime: 0 days 0:17:04.374
System Uptime: 0 days 0:34:28.800
System Uptime: 0 days 0:09:34.612
System Uptime: 0 days 0:16:28.167
System Uptime: 0 days 0:03:29.376
System Uptime: 0 days 0:07:54.575
System Uptime: 0 days 3:34:32.360
System Uptime: 0 days 2:27:34.400
System Uptime: 0 days 1:08:10.603
System Uptime: 0 days 0:53:15.439
System Uptime: 0 days 1:08:47.049
[/font]