Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Always BSOD While Gaming in RC1

06 Nov 2009   #1
153351

Windows 7 RC1
 
 
Always BSOD While Gaming in RC1

Any game will eventually give me a blue screen, citing HIDCLASS.SYS or an NV_____ something.

I've swapped video cards, updated drivers, and reinstalled. Please help.

Minidump and msinfo32 attached.


My System SpecsSystem Spec
.
06 Nov 2009   #2
torrentg

7600.20510 x86
 
 

Please fill in your system specs so we have the information handy while looking at posts.

First gut feeling that comes to mind here is to perform a bios update. Visit your motherboard manufacturer's site to see if there are any. Use latest one if found.

Definitely update your chipset drivers along with usb audio device driver if any are available.

Migrating to 7600 build may be very helpful too. If you disabled the page file, try re-enabling it.

http://msdn.microsoft.com/en-us/library/ms795930.aspx
Code:
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Code:
SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbaudio!USBCaptureProcessPin+2a9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbaudio

IMAGE_NAME:  usbaudio.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49ee99d6

FAILURE_BUCKET_ID:  X64_0xD1_usbaudio!USBCaptureProcessPin+2a9

BUCKET_ID:  X64_0xD1_usbaudio!USBCaptureProcessPin+2a9

Followup: MachineOwner
---------

2: kd> lmvm usbaudio
start             end                 module name
fffff880`03fe3000 fffff880`03ffdc00   usbaudio   (pdb symbols)          c:\symcache\USBAudio.pdb\9989A73BAE9747E697AC3A2420F4E4F91\USBAudio.pdb
    Loaded symbol image file: usbaudio.sys
    Mapped memory image file: C:\SymCache\usbaudio.sys\49EE99D61ac00\usbaudio.sys
    Image path: \SystemRoot\system32\drivers\usbaudio.sys
    Image name: usbaudio.sys
    Timestamp:        Wed Apr 22 00:15:18 2009 (49EE99D6)
    CheckSum:         000287C3
    ImageSize:        0001AC00
    File version:     6.1.7100.0
    Product version:  6.1.7100.0
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     USBAudio.sys
    OriginalFilename: USBAudio.sys
    ProductVersion:   6.1.7100.0
    FileVersion:      6.1.7100.0 (winmain_win7rc.090421-1700)
    FileDescription:  USB Audio Class Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
Because of the following, I recommend checking your memory modules for the proper voltage VDIMM settings. Visit the maker's website and adjust your bios accordingly. Especially for OCZ brands of ram modules.

If this doesn't help, run memtest for an extended period of time. Overnight is best.

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Temp\Rar$DI54.707\101409-22838-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7100 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02a49000 PsLoadedModuleList = 0xfffff800`02c82e90
Debug session time: Wed Oct 14 19:03:32.084 2009 (GMT-5)
System Uptime: 0 days 4:42:43.644
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffffffae00ac18, 2, 1, fffff88003e67653}

Probably caused by : hardware ( mouclass!WPP_RECORDER_SF_qq+5f )

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: ffffffffae00ac18, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88003e67653, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ced0e0
 ffffffffae00ac18 

CURRENT_IRQL:  2

FAULTING_IP: 
mouclass!WPP_RECORDER_SF_qq+5f
fffff880`03e67653 8364244800      and     dword ptr [rsp+48h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f1b540 -- (.trap 0xfffff88002f1b540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88003e6b2d0 rbx=0000000000000000 rcx=fffff88003e6c580
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003e67653 rsp=fffff88002f1b6d0 rbp=0000000000000018
 r8=0000000000000004  r9=0000000000000030 r10=0000000000000020
r11=fffff88002f1b728 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
mouclass!WPP_RECORDER_SF_qq+0x5f:
fffff880`03e67653 8364244800      and     dword ptr [rsp+48h],0 ss:0018:fffff880`02f1b718=00000000
Resetting default scope

MISALIGNED_IP: 
mouclass!WPP_RECORDER_SF_qq+5f
fffff880`03e67653 8364244800      and     dword ptr [rsp+48h],0

LAST_CONTROL_TRANSFER:  from fffff80002ac74e9 to fffff80002ac7f80

STACK_TEXT:  
fffff880`02f1b3f8 fffff800`02ac74e9 : 00000000`0000000a ffffffff`ae00ac18 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f1b400 fffff800`02ac6160 : 00000000`01170000 00000000`00000030 fffff880`048fe2e9 fffffa80`087ed050 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b540 fffff880`03e67653 : 00000000`0000002f fffff880`03e6754e 00000000`0000002d fffff880`03e670a0 : nt!KiPageFault+0x260
fffff880`02f1b6d0 fffff880`03e689ad : 00000000`00000018 fffffa80`099101b0 fffffa80`099101b0 00000000`00000007 : mouclass!WPP_RECORDER_SF_qq+0x5f
fffff880`02f1b730 fffff880`03b42c79 : 00000000`00000002 00000000`00000800 fffffa80`09901310 fffffa80`098f28c0 : mouclass!MouseClassServiceCallback+0x155
fffff880`02f1b7b0 fffff800`02ad06b7 : fffffa80`086c2c33 00000000`00000000 00000000`00000001 fffff880`00000000 : mouhid!MouHid_ReadComplete+0x69d
fffff880`02f1b830 fffff880`03b22acc : fffffa80`07956ed0 fffffa80`07956e06 fffffa80`098f3100 00000000`00000000 : nt!IopfCompleteRequest+0x397
fffff880`02f1b900 fffff880`03b22d35 : fffffa80`098f3602 fffffa80`098f3660 fffffa80`098f31d0 00000000`0000000a : HIDCLASS!HidpDistributeInterruptReport+0x130
fffff880`02f1b990 fffff800`02ad06b7 : fffffa80`098c2ee3 00000000`00000000 fffffa80`098f3001 fffffa80`098c2c60 : HIDCLASS!HidpInterruptReadComplete+0x235
fffff880`02f1ba20 fffff880`041905e9 : fffffa80`087ed050 fffffa80`0777be00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x397
fffff880`02f1baf0 fffff880`04190ac7 : fffffa80`08954902 fffffa80`098c2c60 00000000`ffffffff fffffa80`087edea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02f1bbd0 fffff880`0418e65f : fffffa80`087edea8 fffffa80`087ed1a0 fffffa80`087ee040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f1bc30 fffff880`0417ff89 : fffffa80`087ed050 00000000`00000000 00000000`00000002 fffffa80`087edea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02f1bc70 fffff800`02a6db9f : fffff880`009ed300 fffffa80`087edec0 00000000`00000000 fffff880`009eb180 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f1bca0 fffff800`02aca6de : 00000000`00000000 fffff880`009f5fc0 fffffa80`07a38810 00000000`00000000 : nt!KiExecuteAllDpcs+0x15f
fffff880`02f1bd50 fffff800`02abf41a : fffff880`009eb180 00000000`00000000 fffff880`009f5fc0 fffffa80`07a38810 : nt!KiRetireDpcList+0xd8
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mouclass!WPP_RECORDER_SF_qq+5f
fffff880`03e67653 8364244800      and     dword ptr [rsp+48h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  mouclass!WPP_RECORDER_SF_qq+5f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_mouclass.sys

BUCKET_ID:  X64_IP_MISALIGNED_mouclass.sys

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: ffffffffae00ac18, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88003e67653, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS:  ffffffffae00ac18 

CURRENT_IRQL:  2

FAULTING_IP: 
mouclass!WPP_RECORDER_SF_qq+5f
fffff880`03e67653 8364244800      and     dword ptr [rsp+48h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f1b540 -- (.trap 0xfffff88002f1b540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88003e6b2d0 rbx=0000000000000000 rcx=fffff88003e6c580
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003e67653 rsp=fffff88002f1b6d0 rbp=0000000000000018
 r8=0000000000000004  r9=0000000000000030 r10=0000000000000020
r11=fffff88002f1b728 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
mouclass!WPP_RECORDER_SF_qq+0x5f:
fffff880`03e67653 8364244800      and     dword ptr [rsp+48h],0 ss:0018:fffff880`02f1b718=00000000
Resetting default scope

MISALIGNED_IP: 
mouclass!WPP_RECORDER_SF_qq+5f
fffff880`03e67653 8364244800      and     dword ptr [rsp+48h],0

LAST_CONTROL_TRANSFER:  from fffff80002ac74e9 to fffff80002ac7f80

STACK_TEXT:  
fffff880`02f1b3f8 fffff800`02ac74e9 : 00000000`0000000a ffffffff`ae00ac18 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f1b400 fffff800`02ac6160 : 00000000`01170000 00000000`00000030 fffff880`048fe2e9 fffffa80`087ed050 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b540 fffff880`03e67653 : 00000000`0000002f fffff880`03e6754e 00000000`0000002d fffff880`03e670a0 : nt!KiPageFault+0x260
fffff880`02f1b6d0 fffff880`03e689ad : 00000000`00000018 fffffa80`099101b0 fffffa80`099101b0 00000000`00000007 : mouclass!WPP_RECORDER_SF_qq+0x5f
fffff880`02f1b730 fffff880`03b42c79 : 00000000`00000002 00000000`00000800 fffffa80`09901310 fffffa80`098f28c0 : mouclass!MouseClassServiceCallback+0x155
fffff880`02f1b7b0 fffff800`02ad06b7 : fffffa80`086c2c33 00000000`00000000 00000000`00000001 fffff880`00000000 : mouhid!MouHid_ReadComplete+0x69d
fffff880`02f1b830 fffff880`03b22acc : fffffa80`07956ed0 fffffa80`07956e06 fffffa80`098f3100 00000000`00000000 : nt!IopfCompleteRequest+0x397
fffff880`02f1b900 fffff880`03b22d35 : fffffa80`098f3602 fffffa80`098f3660 fffffa80`098f31d0 00000000`0000000a : HIDCLASS!HidpDistributeInterruptReport+0x130
fffff880`02f1b990 fffff800`02ad06b7 : fffffa80`098c2ee3 00000000`00000000 fffffa80`098f3001 fffffa80`098c2c60 : HIDCLASS!HidpInterruptReadComplete+0x235
fffff880`02f1ba20 fffff880`041905e9 : fffffa80`087ed050 fffffa80`0777be00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x397
fffff880`02f1baf0 fffff880`04190ac7 : fffffa80`08954902 fffffa80`098c2c60 00000000`ffffffff fffffa80`087edea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02f1bbd0 fffff880`0418e65f : fffffa80`087edea8 fffffa80`087ed1a0 fffffa80`087ee040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f1bc30 fffff880`0417ff89 : fffffa80`087ed050 00000000`00000000 00000000`00000002 fffffa80`087edea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02f1bc70 fffff800`02a6db9f : fffff880`009ed300 fffffa80`087edec0 00000000`00000000 fffff880`009eb180 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f1bca0 fffff800`02aca6de : 00000000`00000000 fffff880`009f5fc0 fffffa80`07a38810 00000000`00000000 : nt!KiExecuteAllDpcs+0x15f
fffff880`02f1bd50 fffff800`02abf41a : fffff880`009eb180 00000000`00000000 fffff880`009f5fc0 fffffa80`07a38810 : nt!KiRetireDpcList+0xd8
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mouclass!WPP_RECORDER_SF_qq+5f
fffff880`03e67653 8364244800      and     dword ptr [rsp+48h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  mouclass!WPP_RECORDER_SF_qq+5f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_mouclass.sys

BUCKET_ID:  X64_IP_MISALIGNED_mouclass.sys

Followup: MachineOwner
---------
My System SpecsSystem Spec
Reply

 Always BSOD While Gaming in RC1




Thread Tools




Similar help and support threads
Thread Forum
BSOD with Gigabyte G1 Gaming GTX970 in SLI while gaming
Hi guys, This is my first post in this forum since I have not received any help from elswhere. You guys are my only hope. Okay, so I recently bought two G1 Gaming GTX970 graphics cards. The first driver install went bad by windows using its own drivers, so I got the Display Driver...
BSOD Help and Support
BSOD when starting MSI Gaming App and change to gaming mode or OC mode
Hello Forum, I have build a Gaming PC and i was trying to use the MSI Gaming app. It worked but nowadays when i change the mode it gives me an instant BSOD. i have uploaded the BSOD .zip file as instructed. Thank you for your help, Kind regards, Jan L
BSOD Help and Support
Various BSoD while gaming and some randomly while not gaming.
So over the past couple of weeks i've been getting alot of BSoD while gaming on my laptop, the most common being failure to reset display drivers. It seems to be a driver problem but I've tried re-installing them and it hasn't had an effect. I wasn't sure how to properly do a fresh install so if...
BSOD Help and Support
BSOD when cpu is idle for long period, no bsod while gaming 4~8hours
Hello and greetings to all. I dint understand my pc now..after i fresh format my pc after 2years of usage, i on genuine windows and uptodate till today..but i seems cant leave my pc on idle/downloading most of the time...when i wake up, my pc already restarted..just now while im watching a long...
BSOD Help and Support
BSOD Occurring Randomly while gaming and when i am not gaming???
I dont know why. I recently bought a new computer and it has been doing this since i first got it. I dont know why but hopefully you can help me. :D My Computer Stats: -Intel® Core™ i7-3770K -GIGABYTE GA-Z77X-UD3H Z77 - NVIDIA GeForce GTX 660 Ti 2GB -Corsair Vengeance 8GB -2TB Hard Drive...
BSOD Help and Support
Daily BSOD's, some random, some during gaming (Prime95 Insta-BSOD)
I have been having the worst time with my custom built PC since it was built. I am getting random BSOD's here and there, but there does seem to be a correlation between a greater occurence when playing games. Often I can't play a high-resolution game for more than an hour or two before I crash. ...
BSOD Help and Support


Our Sites

Site Links

About Us

Find 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 10:51.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App