BSOD playing any games

After playing a game for a while, I get a BSOD...

After reading the analysis, I guessed there was a problem with my video card driver but it's up to date. So maybe you guys could find the other thing!

Thanks

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {93799568, 2, 8, 93799568}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : hardware ( dxgkrnl!DmmGetPathContentFromClientVidPnSource+91 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 93799568, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 93799568, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from 82daf848
Unable to read MiSystemVaType memory at 82d8ee20
93799568
CURRENT_IRQL: 2
FAULTING_IP:
dxgkrnl!DmmGetPathContentFromClientVidPnSource+91
93799568 45 inc ebp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: TESV.exe
TRAP_FRAME: 807e6d38 -- (.trap 0xffffffff807e6d38)
ErrCode = 00000010
eax=82d74580 ebx=82cbd4c5 ecx=00000000 edx=00000000 esi=8882a440 edi=87a0e008
eip=93799568 esp=807e6dac ebp=807e6e10 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
dxgkrnl!DmmGetPathContentFromClientVidPnSource+0x91:
93799568 45 inc ebp
Resetting default scope
MISALIGNED_IP:
dxgkrnl!DmmGetPathContentFromClientVidPnSource+91
93799568 45 inc ebp
LAST_CONTROL_TRANSFER: from 93799568 to 82c875fb
FAILED_INSTRUCTION_ADDRESS:
dxgkrnl!DmmGetPathContentFromClientVidPnSource+91
93799568 45 inc ebp
STACK_TEXT:
807e6d38 93799568 badb0d00 00000000 807e6d5c nt!KiTrap0E+0x2cf
807e6e10 937c1d77 0282a440 807e6e60 937c335c dxgkrnl!DmmGetPathContentFromClientVidPnSource+0x91
807e6e1c 937c335c 8882a440 87a12000 87a13120 dxgmms1!VidSchiProcessCompletedQueuePacket+0xd
807e6e60 937c3451 87a0e008 87a13120 00000000 dxgmms1!VidSchiProcessDpcCompletedPacket+0x3e4
807e6e7c 937c351e 87a0e008 879ef000 87a0e008 dxgmms1!VidSchiProcessDpcDmaPacket+0xc5
807e6e94 937c3832 879ef000 00000001 86a83000 dxgmms1!VidSchDdiNotifyDpcWorker+0xb2
807e6eb8 93700f28 86807020 807e6ed8 93700e88 dxgmms1!VidSchDdiNotifyDpc+0x78
807e6ec4 93700e88 866cf590 86807020 93666ea0 dxgkrnl!VIDSCH_EXPORT::VidSchDdiNotifyDpc+0x11
807e6ed8 92cf2b5c 86807020 93666ea0 00000000 dxgkrnl!DxgNotifyDpcCB+0x5d
WARNING: Stack unwind information not available. Following frames may be wrong.
807e6ef4 92cf2dc3 86a83000 86a83000 00000000 nvlddmkm+0xb5b5c
807e6f0c 92cf33d0 86a83000 00000000 93666ea0 nvlddmkm+0xb5dc3
807e6f28 92c69355 807c7a00 86a83078 87eb5c64 nvlddmkm+0xb63d0
807e6f3c 92c68fb3 92c69323 807e6fa4 82cbe1b5 nvlddmkm+0x2c355
807e6f48 82cbe1b5 86a83078 86a83000 00000000 nvlddmkm+0x2bfb3
807e6fa4 82cbe018 807c6120 87eb5be0 00000000 nt!KiExecuteAllDpcs+0xf9
807e6ff4 82cbd7dc aa273ce4 00000000 00000000 nt!KiRetireDpcList+0xd5
807e6ff8 aa273ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
82cbd7dc 00000000 0000001a 00d6850f bb830000 0xaa273ce4

STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!DmmGetPathContentFromClientVidPnSource+91
93799568 45 inc ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!DmmGetPathContentFromClientVidPnSource+91
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED_dxgkrnl.sys
BUCKET_ID: IP_MISALIGNED_dxgkrnl.sys
Followup: MachineOwner
---------

Like your self help.
Well done!
But....


We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

The game doesn't happen to be Skyrim does it?

Thx for the response!

Every game crash except skyrim...

And no, it is not overclocked.

Here is 4 dump files examples! Hope it will clarify...

XCatEmpireX said:

Thx for the response!

Every game crash except skyrim...

And no, it is not overclocked.

Here is 4 dump files examples! Hope it will clarify...

Ok

In post one you posted the output of winDbg ant the active thread at the time of the crash was TESV.exe. From what I read that appears to be a Skyrim file that has a version 1.2 patch for it.

These 4 crashes have 4 different causes but they do have one thing in common. they all are related to USB/HID (human Interface device like fingerprint readers).

What do you have running on USB?

I have 2 things connected to usb :

-G700 gaming mouse with Logitech Setpoint driver
-Microsoft keyboard

I got the mouse at christmas and it might be when it all started... I'll take a closer look at the setpoint driver!

Thanks!

XCatEmpireX said:

I have 2 things connected to usb :

-G700 gaming mouse with Logitech Setpoint driver
-Microsoft keyboard

I got the mouse at christmas and it might be when it all started... I'll take a closer look at the setpoint driver!

Thanks!

Set point (especially if it isnt updated) can be a problem.