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: BSOD while playing games.


28 Dec 2011   #1

Windows 7 Ultimate x64
 
 
BSOD while playing games.

Windows 7 ultimate service pack 1
RAM: 4 GB
Quad CPU Q9400 @ 2.66GHz 2.67 GHz
Nvidia Geforce GTS 450

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64
- the original installed OS on the system? Windows XP 32 bit
- an OEM or full retail version? Full retail

- What is the age of system (hardware)? Around 3 years.
- What is the age of OS installation (have you re-installed the OS?) Did a complete reinstall probably around 2 months ago, didn't help.

My System SpecsSystem Spec
.

28 Dec 2011   #2

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\krazy7\Windows_NT6_BSOD_jcgriff2\122711-15210-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0324f000 PsLoadedModuleList = 0xfffff800`03494670 Debug session time: Tue Dec 27 05:53:19.144 2011 (UTC - 7:00) System Uptime: 0 days 15:07:06.596 Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : hardware ( mouclass!WPP_RECORDER_SF_qq+60 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +6637333138336133 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: League of Lege CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff80000ba26b8 -- (.exr 0xfffff80000ba26b8) ExceptionAddress: fffff8800f20e654 (mouclass!WPP_RECORDER_SF_qq+0x0000000000000060) ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000 NumberParameters: 0 TRAP_FRAME: fffff80000ba2760 -- (.trap 0xfffff80000ba2760) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8800f2122d0 rbx=0000000000000000 rcx=fffff8800f213580 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800f20e654 rsp=fffff80000ba28f0 rbp=0000000000000018 r8=0000000000000004 r9=0000000000000030 r10=0000000000000020 r11=fffff80000ba2948 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc mouclass!WPP_RECORDER_SF_qq+0x60: fffff880`0f20e654 642448 and al,48h Resetting default scope MISALIGNED_IP: mouclass!WPP_RECORDER_SF_qq+60 fffff880`0f20e654 642448 and al,48h LAST_CONTROL_TRANSFER: from fffff800032c35fe to fffff800032cbc10 STACK_TEXT: fffff800`00ba1798 fffff800`032c35fe : 00000000`00000000 fffffa80`0537e9ee fffff800`00ba1f10 fffff800`032f7830 : nt!KeBugCheck fffff800`00ba17a0 fffff800`032f74fd : fffff800`034d571c fffff800`03412c30 fffff800`0324f000 fffff800`00ba26b8 : nt!KiKernelCalloutExceptionHandler+0xe fffff800`00ba17d0 fffff800`032f62d5 : fffff800`03416028 fffff800`00ba1848 fffff800`00ba26b8 fffff800`0324f000 : nt!RtlpExecuteHandlerForException+0xd fffff800`00ba1800 fffff800`03307361 : fffff800`00ba26b8 fffff800`00ba1f10 fffff800`00000000 fffffa80`052cc960 : nt!RtlDispatchException+0x415 fffff800`00ba1ee0 fffff800`032cb2c2 : fffff800`00ba26b8 00000000`00003530 fffff800`00ba2760 00000000`00000008 : nt!KiDispatchException+0x135 fffff800`00ba2580 fffff800`032c941f : fffff800`00ba2760 fffff880`03ca8f02 fffffa80`03ffc700 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff800`00ba2760 fffff880`0f20e654 : 00000000`0000002f fffff880`0f20e54e 00000000`0000002d fffff880`0f20e0a0 : nt!KiInvalidOpcodeFault+0x11f fffff800`00ba28f0 fffff880`0f20f9ad : 00000000`00000018 fffffa80`05d8da80 fffffa80`05d8da80 00000000`00000007 : mouclass!WPP_RECORDER_SF_qq+0x60 fffff800`00ba2950 fffff880`07167c79 : 00000000`00000002 00000000`ffffffff fffffa80`05e03b30 fffffa80`05daede0 : mouclass!MouseClassServiceCallback+0x155 fffff800`00ba29d0 fffff800`032cf021 : fffffa80`04915b7b fffff800`00000000 fffffa80`00000001 fffff880`00000001 : mouhid!MouHid_ReadComplete+0x69d fffff800`00ba2a50 fffff880`03c789c4 : fffffa80`05dac9b0 fffffa80`05dac906 fffffa80`05da7a00 00000000`00000000 : nt!IopfCompleteRequest+0x341 fffff800`00ba2b40 fffff880`03c78c2d : fffffa80`05d85f02 fffffa80`05d85f20 fffffa80`05da7a00 00000000`00000008 : HIDCLASS!HidpDistributeInterruptReport+0x130 fffff800`00ba2bd0 fffff800`032cf021 : fffffa80`05b4a24b 00000000`00000000 fffffa80`05da7801 fffffa80`05b4a010 : HIDCLASS!HidpInterruptReadComplete+0x235 fffff800`00ba2c60 fffff880`03cb6631 : fffffa80`05256050 fffffa80`0645f000 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341 fffff800`00ba2d50 fffff880`03cb6b0f : fffffa80`05fa4202 fffffa80`05b4a010 00000000`ffffffff fffffa80`05256eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15 fffff800`00ba2e30 fffff880`03cb466f : fffffa80`05256eb0 fffffa80`052561a0 fffffa80`05257050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7 fffff800`00ba2e90 fffff880`03ca5f89 : fffffa80`05256050 00000000`00000000 fffffa80`05256e02 fffffa80`05256eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3 fffff800`00ba2ed0 fffff800`032d70ac : fffff800`03441e80 fffffa80`05256eb0 fffffa80`05256ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9 fffff800`00ba2f00 fffff800`032ce765 : 00000000`00000000 fffffa80`03d60b60 00000000`00000000 fffff880`03ca5db0 : nt!KiRetireDpcList+0x1bc fffff800`00ba2fb0 fffff800`032ce57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5 fffff880`0df01ba0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: mouclass!WPP_RECORDER_SF_qq+60 fffff880`0f20e654 642448 and al,48h SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: mouclass!WPP_RECORDER_SF_qq+60 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 ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\krazy7\Windows_NT6_BSOD_jcgriff2\122711-17097-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03259000 PsLoadedModuleList = 0xfffff800`0349e670 Debug session time: Tue Dec 27 14:20:35.370 2011 (UTC - 7:00) System Uptime: 0 days 8:26:40.212 Loading Kernel Symbols ............................................................... ................................................................ ................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {4f444648, 2, 1, fffff8800f012d3f} Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+123 ) Followup: MachineOwner --------- 0: 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: 000000004f444648, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff8800f012d3f, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003508100 000000004f444648 CURRENT_IRQL: 2 FAULTING_IP: USBPORT!USBPORT_Core_iCompleteDoneTransfer+123 fffff880`0f012d3f 41b808000000 mov r8d,8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff80000b9c950 -- (.trap 0xfffff80000b9c950) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800f012d3f rsp=fffff80000b9cae0 rbp=0000000000000000 r8=000000004f444648 r9=000000000000000b r10=00000000ffffffff r11=fffffa80052121a0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x123: fffff880`0f012d3f 41b808000000 mov r8d,8 Resetting default scope LAST_CONTROL_TRANSFER: from fffff800032d51e9 to fffff800032d5c40 STACK_TEXT: fffff800`00b9c808 fffff800`032d51e9 : 00000000`0000000a 00000000`4f444648 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff800`00b9c810 fffff800`032d3e60 : fffffa80`052121a0 fffff880`0f002783 fffffa80`05212ba0 fffffa80`052121a0 : nt!KiBugCheckDispatch+0x69 fffff800`00b9c950 fffff880`0f012d3f : fffffa80`05212eb0 00000000`ffffffff fffffa80`05212050 fffff880`0f01156a : nt!KiPageFault+0x260 fffff800`00b9cae0 fffff880`0f013b0f : fffffa80`04561602 fffffa80`05b7fc60 00000000`ffffffff fffffa80`05212eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x123 fffff800`00b9cbc0 fffff880`0f01166f : fffffa80`05212eb0 fffffa80`052121a0 fffffa80`05213050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7 fffff800`00b9cc20 fffff880`0f002f89 : fffffa80`05212050 00000000`00000000 fffffa80`05212e02 fffffa80`05212eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3 fffff800`00b9cc60 fffff800`032e10ac : fffff800`0344be80 fffffa80`05212eb0 fffffa80`05212ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9 fffff800`00b9cc90 fffff800`032cd96a : fffff800`0344be80 fffff800`03459cc0 00000000`00000000 fffff880`0f002db0 : nt!KiRetireDpcList+0x1bc fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: USBPORT!USBPORT_Core_iCompleteDoneTransfer+123 fffff880`0f012d3f 41b808000000 mov r8d,8 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: USBPORT!USBPORT_Core_iCompleteDoneTransfer+123 FOLLOWUP_NAME: MachineOwner MODULE_NAME: USBPORT IMAGE_NAME: USBPORT.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c08 FAILURE_BUCKET_ID: X64_0xD1_USBPORT!USBPORT_Core_iCompleteDoneTransfer+123 BUCKET_ID: X64_0xD1_USBPORT!USBPORT_Core_iCompleteDoneTransfer+123 Followup: MachineOwner ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\krazy7\Windows_NT6_BSOD_jcgriff2\122911-15802-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0320f000 PsLoadedModuleList = 0xfffff800`03454670 Debug session time: Wed Dec 28 16:34:29.729 2011 (UTC - 7:00) System Uptime: 0 days 2:25:30.181 Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffff87ffbdef490, 2, 8, fffff87ffbdef490} Probably caused by : usbuhci.sys ( usbuhci!UhciPollAsyncEndpoint+165 ) Followup: MachineOwner --------- 0: 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: fffff87ffbdef490, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: fffff87ffbdef490, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034be100 fffff87ffbdef490 CURRENT_IRQL: 2 FAULTING_IP: +6637333138336133 fffff87f`fbdef490 ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: League of Lege TRAP_FRAME: fffff80000ba2bb0 -- (.trap 0xfffff80000ba2bb0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa8004c2e2ff rbx=0000000000000000 rcx=fffffa8005229c80 rdx=000000004f444648 rsi=0000000000000000 rdi=0000000000000000 rip=fffff87ffbdef490 rsp=fffff80000ba2d48 rbp=fffff8800771d700 r8=000000004f444648 r9=00000000cff3a780 r10=00000000ffffffff r11=fffffa8005c9e820 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc fffff87f`fbdef490 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000328b1e9 to fffff8000328bc40 FAILED_INSTRUCTION_ADDRESS: +6637333138336133 fffff87f`fbdef490 ?? ??? STACK_TEXT: fffff800`00ba2a68 fffff800`0328b1e9 : 00000000`0000000a fffff87f`fbdef490 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx fffff800`00ba2a70 fffff800`03289e60 : 00000000`00000000 fffffa80`04c6f000 00000000`00000000 00000000`00000002 : nt!KiBugCheckDispatch+0x69 fffff800`00ba2bb0 fffff87f`fbdef490 : fffff880`0fdef34d 00000000`00000002 fffffa80`04c2e258 fffffa80`04c2e258 : nt!KiPageFault+0x260 fffff800`00ba2d48 fffff880`0fdef34d : 00000000`00000002 fffffa80`04c2e258 fffffa80`04c2e258 fffffa80`04c2e318 : 0xfffff87f`fbdef490 fffff800`00ba2d50 fffff880`0fdec2d6 : 00000000`00000002 fffffa80`04c2e010 00000000`00000000 fffffa80`052251a0 : usbuhci!UhciPollAsyncEndpoint+0x165 fffff800`00ba2db0 fffff880`06d1be8b : fffffa80`052251a0 00000000`00000002 00000000`00000000 00000000`00000040 : usbuhci!UhciPollEndpoint+0x1a fffff800`00ba2de0 fffff880`06d209d1 : 00000000`00000040 00000000`00000004 fffffa80`04c2e010 fffffa80`05225050 : USBPORT!MPf_PollEndpoint+0x9b fffff800`00ba2e10 fffff880`06d2c077 : fffffa80`052251a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1 fffff800`00ba2e70 fffff880`06d1cf89 : fffffa80`05225050 00000000`00000000 fffffa80`05225a02 fffffa80`05225a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3 fffff800`00ba2ed0 fffff800`032970ac : fffff800`03401e80 fffffa80`05225a18 fffffa80`05225a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9 fffff800`00ba2f00 fffff800`0328e765 : 00000000`00000000 fffffa80`04121b60 00000000`00000000 fffff880`06d1cdb0 : nt!KiRetireDpcList+0x1bc fffff800`00ba2fb0 fffff800`0328e57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5 fffff880`09cc3ba0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: usbuhci!UhciPollAsyncEndpoint+165 fffff880`0fdef34d 0300 add eax,dword ptr [rax] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: usbuhci!UhciPollAsyncEndpoint+165 FOLLOWUP_NAME: MachineOwner MODULE_NAME: usbuhci IMAGE_NAME: usbuhci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0bff FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_usbuhci!UhciPollAsyncEndpoint+165 BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_usbuhci!UhciPollAsyncEndpoint+165 Followup: MachineOwner ---------
  4. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\krazy7\Windows_NT6_BSOD_jcgriff2\122911-13478-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0325d000 PsLoadedModuleList = 0xfffff800`034a2670 Debug session time: Thu Dec 29 06:48:59.475 2011 (UTC - 7:00) System Uptime: 0 days 14:13:51.926 Loading Kernel Symbols ............................................................... ................................................................ ................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {3f4, 2, 1, fffff880081afac0} Probably caused by : hidusb.sys ( hidusb!WppAutoLogTrace+108 ) Followup: MachineOwner --------- 2: 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: 00000000000003f4, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff880081afac0, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350c100 00000000000003f4 CURRENT_IRQL: 2 FAULTING_IP: hidusb!WppAutoLogTrace+108 fffff880`081afac0 66894108 mov word ptr [rcx+8],ax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff88002f8b640 -- (.trap 0xfffff88002f8b640) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000003f4 rbx=0000000000000000 rcx=fffffa8004c9546c rdx=000000000000524c rsi=0000000000000000 rdi=0000000000000000 rip=fffff880081afac0 rsp=fffff88002f8b7d0 rbp=0000000000000000 r8=fffffa8004c95498 r9=fffff880081b11c0 r10=000000000000002c r11=fffffa8004c95000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc hidusb!WppAutoLogTrace+0x108: fffff880`081afac0 66894108 mov word ptr [rcx+8],ax ds:23c0:fffffa80`04c95474=???? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800032d91e9 to fffff800032d9c40 STACK_TEXT: fffff880`02f8b4f8 fffff800`032d91e9 : 00000000`0000000a 00000000`000003f4 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`02f8b500 fffff800`032d7e60 : fffffa80`052b6670 fffff880`0f0804a0 00000000`00000012 fffffa80`04ef4d30 : nt!KiBugCheckDispatch+0x69 fffff880`02f8b640 fffff880`081afac0 : 00000000`00000000 fffff800`032dd021 fffffa80`04f2dafb fffff880`00000000 : nt!KiPageFault+0x260 fffff880`02f8b7d0 fffff880`081acd2d : fffffa80`039f7148 fffffa80`052b6670 00000000`00000004 fffff880`0f07fb2b : hidusb!WppAutoLogTrace+0x108 fffff880`02f8b830 fffff880`081ace76 : fffffa80`05db9ab0 fffffa80`05d66b30 00000000`0000000d fffff880`0f076622 : hidusb!WPP_RECORDER_SF_qq+0xa1 fffff880`02f8b890 fffff880`0f078555 : fffffa80`05db9a01 fffffa80`05db9ab0 fffffa80`04f2dc60 00000000`00000008 : hidusb!HumInternalIoctl+0x52 fffff880`02f8b900 fffff880`0f078d75 : fffffa80`05db9ab0 fffffa80`05d66ca0 00000000`00000000 00000000`00000008 : HIDCLASS!HidpSubmitInterruptRead+0xdd fffff880`02f8b960 fffff800`032dd021 : fffffa80`04f2de9b 00000000`00000000 fffffa80`05d66b01 fffffa80`04f2dc00 : HIDCLASS!HidpInterruptReadComplete+0x37d fffff880`02f8b9f0 fffff880`03e44631 : fffffa80`0522b050 fffffa80`0412a400 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341 fffff880`02f8bae0 fffff880`03e44b0f : fffffa80`04df7502 fffffa80`04f2dc60 00000000`ffffffff fffffa80`0522beb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15 fffff880`02f8bbc0 fffff880`03e4266f : fffffa80`0522beb0 fffffa80`0522b1a0 fffffa80`0522c050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7 fffff880`02f8bc20 fffff880`03e33f89 : fffffa80`0522b050 00000000`00000000 fffffa80`0522be02 fffffa80`0522beb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3 fffff880`02f8bc60 fffff800`032e50ac : fffff880`02f63180 fffffa80`0522beb0 fffffa80`0522bec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9 fffff880`02f8bc90 fffff800`032d196a : fffff880`02f63180 fffff880`02f6dfc0 00000000`00000000 fffff880`03e33db0 : nt!KiRetireDpcList+0x1bc fffff880`02f8bd40 00000000`00000000 : fffff880`02f8c000 fffff880`02f86000 fffff880`02f8bd00 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: hidusb!WppAutoLogTrace+108 fffff880`081afac0 66894108 mov word ptr [rcx+8],ax SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: hidusb!WppAutoLogTrace+108 FOLLOWUP_NAME: MachineOwner MODULE_NAME: hidusb IMAGE_NAME: hidusb.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7a665 FAILURE_BUCKET_ID: X64_0xD1_hidusb!WppAutoLogTrace+108 BUCKET_ID: X64_0xD1_hidusb!WppAutoLogTrace+108 Followup: MachineOwner ---------
Your blue screens were related to hardware once, USBPORT.SYS, usbuhci.sys, and hidusb.sys. League of Legends was the attributed program in two of the four cases.

You should udpate (if possible) the following drivers via Driver Reference information:
Code:
TBPANELX64	fffff880`08911000	fffff880`08919000	Tue Sep 20 05:32:31 2005 (432ff34f)	00012376		TBPANELX64.SYS
hamachi	fffff880`0f056000	fffff880`0f061000	Thu Feb 19 03:36:41 2009 (499d3639)	0000a5d7		hamachi.sys

Take a look at the troubleshooting steps in Stop 0x124 What it means and what to try.


My first instinct is there is a device plugged into your USB ports that is causing issues. Unplug all non-essentials leaving only the mouse, keyboard, and monitor plugged in. If you are using a USB gaming device: try to find newer drivers for it, roll back the drivers to those that came with it on a CD or DVD, or replace it if no other drivers may be used.
My System SpecsSystem Spec
31 Dec 2011   #3

Windows 7 Ultimate x64
 
 

Tried all of the above.
Got 2 more BSODS
My System SpecsSystem Spec
.


31 Dec 2011   #4

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\krazy7\Windows_NT6_BSOD_jcgriff2\122911-15802-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0320f000 PsLoadedModuleList = 0xfffff800`03454670 Debug session time: Wed Dec 28 16:34:29.729 2011 (UTC - 7:00) System Uptime: 0 days 2:25:30.181 Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffff87ffbdef490, 2, 8, fffff87ffbdef490} Probably caused by : usbuhci.sys ( usbuhci!UhciPollAsyncEndpoint+165 ) Followup: MachineOwner --------- 0: 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: fffff87ffbdef490, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: fffff87ffbdef490, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034be100 fffff87ffbdef490 CURRENT_IRQL: 2 FAULTING_IP: +6637333138336133 fffff87f`fbdef490 ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: League of Lege TRAP_FRAME: fffff80000ba2bb0 -- (.trap 0xfffff80000ba2bb0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa8004c2e2ff rbx=0000000000000000 rcx=fffffa8005229c80 rdx=000000004f444648 rsi=0000000000000000 rdi=0000000000000000 rip=fffff87ffbdef490 rsp=fffff80000ba2d48 rbp=fffff8800771d700 r8=000000004f444648 r9=00000000cff3a780 r10=00000000ffffffff r11=fffffa8005c9e820 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc fffff87f`fbdef490 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000328b1e9 to fffff8000328bc40 FAILED_INSTRUCTION_ADDRESS: +6637333138336133 fffff87f`fbdef490 ?? ??? STACK_TEXT: fffff800`00ba2a68 fffff800`0328b1e9 : 00000000`0000000a fffff87f`fbdef490 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx fffff800`00ba2a70 fffff800`03289e60 : 00000000`00000000 fffffa80`04c6f000 00000000`00000000 00000000`00000002 : nt!KiBugCheckDispatch+0x69 fffff800`00ba2bb0 fffff87f`fbdef490 : fffff880`0fdef34d 00000000`00000002 fffffa80`04c2e258 fffffa80`04c2e258 : nt!KiPageFault+0x260 fffff800`00ba2d48 fffff880`0fdef34d : 00000000`00000002 fffffa80`04c2e258 fffffa80`04c2e258 fffffa80`04c2e318 : 0xfffff87f`fbdef490 fffff800`00ba2d50 fffff880`0fdec2d6 : 00000000`00000002 fffffa80`04c2e010 00000000`00000000 fffffa80`052251a0 : usbuhci!UhciPollAsyncEndpoint+0x165 fffff800`00ba2db0 fffff880`06d1be8b : fffffa80`052251a0 00000000`00000002 00000000`00000000 00000000`00000040 : usbuhci!UhciPollEndpoint+0x1a fffff800`00ba2de0 fffff880`06d209d1 : 00000000`00000040 00000000`00000004 fffffa80`04c2e010 fffffa80`05225050 : USBPORT!MPf_PollEndpoint+0x9b fffff800`00ba2e10 fffff880`06d2c077 : fffffa80`052251a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1 fffff800`00ba2e70 fffff880`06d1cf89 : fffffa80`05225050 00000000`00000000 fffffa80`05225a02 fffffa80`05225a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3 fffff800`00ba2ed0 fffff800`032970ac : fffff800`03401e80 fffffa80`05225a18 fffffa80`05225a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9 fffff800`00ba2f00 fffff800`0328e765 : 00000000`00000000 fffffa80`04121b60 00000000`00000000 fffff880`06d1cdb0 : nt!KiRetireDpcList+0x1bc fffff800`00ba2fb0 fffff800`0328e57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5 fffff880`09cc3ba0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: usbuhci!UhciPollAsyncEndpoint+165 fffff880`0fdef34d 0300 add eax,dword ptr [rax] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: usbuhci!UhciPollAsyncEndpoint+165 FOLLOWUP_NAME: MachineOwner MODULE_NAME: usbuhci IMAGE_NAME: usbuhci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0bff FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_usbuhci!UhciPollAsyncEndpoint+165 BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_usbuhci!UhciPollAsyncEndpoint+165 Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\krazy7\Windows_NT6_BSOD_jcgriff2\123111-15147-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03217000 PsLoadedModuleList = 0xfffff800`0345c670 Debug session time: Sat Dec 31 06:20:38.085 2011 (UTC - 7:00) System Uptime: 1 days 21:22:43.536 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck BE, {9fca12, 3ff000010f545025, fffff880009b0960, a} 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 : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcVSyncCookie+168 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) An attempt was made to write to readonly memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: 00000000009fca12, Virtual address for the attempted write. Arg2: 3ff000010f545025, PTE contents. Arg3: fffff880009b0960, (reserved) Arg4: 000000000000000a, (reserved) Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xBE PROCESS_NAME: dragonica.exe CURRENT_IRQL: 2 TRAP_FRAME: fffff880009b0960 -- (.trap 0xfffff880009b0960) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000009fca12 rbx=0000000000000000 rcx=00000000000098a9 rdx=000000000000002d rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800f208fc0 rsp=fffff880009b0af0 rbp=fffffa80061b78e0 r8=000000000000a9af r9=0000000000000000 r10=fffffa80061a67d0 r11=fffff880009b0ba8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc dxgmms1!VidSchiProcessDpcVSyncCookie+0x168: fffff880`0f208fc0 4383bc345404000005 cmp dword ptr [r12+r14+454h],5 ds:00000000`00000454=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000323df57 to fffff80003293c40 STACK_TEXT: fffff880`009b07f8 fffff800`0323df57 : 00000000`000000be 00000000`009fca12 3ff00001`0f545025 fffff880`009b0960 : nt!KeBugCheckEx fffff880`009b0800 fffff800`03291d6e : 00000000`00000000 fffffa80`05a5b000 00000000`00000000 fffffa80`061a6010 : nt! ?? ::FNODOBFM::`string'+0x442cb fffff880`009b0960 fffff880`0f208fc0 : fffffa80`03dc9450 00000000`00000000 fffffa80`061b6000 00000000`00000000 : nt!KiPageFault+0x16e fffff880`009b0af0 fffff880`0f208ce8 : 00000000`00000000 fffffa80`0000002d 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiProcessDpcVSyncCookie+0x168 fffff880`009b0bb0 fffff880`0f208c4c : 00000000`00000300 fffffa80`061a6010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x80 fffff880`009b0c00 fffff880`0fee01cf : fffffa80`05099480 fffff880`0f4b4438 00000000`00000022 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94 fffff880`009b0c50 fffff880`0f33ce90 : fffffa80`05205000 fffffa80`05205000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgNotifyDpcCB+0x77 fffff880`009b0c80 fffffa80`05205000 : fffffa80`05205000 00000000`00000000 00000000`00000000 fffff880`0f33ce23 : nvlddmkm+0xdbe90 fffff880`009b0c88 fffffa80`05205000 : 00000000`00000000 00000000`00000000 fffff880`0f33ce23 fffffa80`05205000 : 0xfffffa80`05205000 fffff880`009b0c90 00000000`00000000 : 00000000`00000000 fffff880`0f33ce23 fffffa80`05205000 00000000`00000000 : 0xfffffa80`05205000 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VidSchiProcessDpcVSyncCookie+168 fffff880`0f208fc0 4383bc345404000005 cmp dword ptr [r12+r14+454h],5 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: dxgmms1!VidSchiProcessDpcVSyncCookie+168 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1 FAILURE_BUCKET_ID: X64_0xBE_dxgmms1!VidSchiProcessDpcVSyncCookie+168 BUCKET_ID: X64_0xBE_dxgmms1!VidSchiProcessDpcVSyncCookie+168 Followup: MachineOwner ---------
Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.
My System SpecsSystem Spec
08 Jan 2012   #5

Windows 7 Ultimate x64
 
 

A new one.
My System SpecsSystem Spec
08 Jan 2012   #6
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

krazy,

> Your Asacpi.sys driver is dated 2005

The pre 2009 version of this driver is a known bsod cause.
Quote:
Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (notbefore).


> IF you still crash after the above...


Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!



1-Memtest.
Quote:
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



2-Driver verifier

Quote:
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users
My System SpecsSystem Spec
08 Jan 2012   #7

Windows 7 Ultimate x64
 
 

Instead of the links you posted i downloaded the driver from here
ASUSTeK Computer Inc. -Support- Drivers and Download P5Q SE (The links you posted were from a different motherboard model)

The date the driver was modified on is now 5/14/2009
Hope this will fix it
My System SpecsSystem Spec
08 Jan 2012   #8

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by krazy7 View Post
Instead of the links you posted i downloaded the driver from here
ASUSTeK Computer Inc. -Support- Drivers and Download P5Q SE (The links you posted were from a different motherboard model)

The date the driver was modified on is now 5/14/2009
Hope this will fix it
Did you do a re-install of Windows or of the ASACPI driver? Your previous blue screen drivers were dated later.
Code:
ASACPI	fffff880`06df7000	fffff880`06dff000	Wed May 13 19:25:17 2009 (4a0b72fd)	0000ed7a		ASACPI.sys
My System SpecsSystem Spec
08 Jan 2012   #9

Windows 7 Ultimate x64
 
 

Yeh i did a re-install of windows yesterday, got a BSOD just now again, gonna try running memtest overnight.
My System SpecsSystem Spec
08 Jan 2012   #10

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by krazy7 View Post
Yeh i did a re-install of windows yesterday, got a BSOD just now again, gonna try running memtest overnight.
You may want to consider replacing your mouse or updating your driver for it. Is it a USB mouse?
Code:
dadder	fffff880`056f0000	fffff880`056f3180	Thu Aug 02 03:33:03 2007 (46b1a4cf)	000065d9		dadder.sys
dadder.sys from Driver Reference
My System SpecsSystem Spec
Reply

 BSOD while playing games.




Thread Tools




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 08:24 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33