Solved Frequent BSoD, random error messages.

[xthequwit]

Windows 7 x64 Prof.

Mobo: M3A770DE ASrock running the latest drivers/bios from their website. (1.80) i think.
Bought 2 weeks ago, new.

CPU: Athlon x3 455, stock volts, stock speeds, stock cooler, core temp reporting 25-35c idle to moderate load.
Bought 2 months ago, new, functioning in a different computer until now.

RAM: PNY 2x4 gigs, ddr3 1333, timing 9-9-9-24
New 2 weeks ago

GPU: Powercolor 5770, factory overclock.
Bought a year ago, functioning in a different computer until now.
Attempting to install the drivers resulted in 2 error messages that the application had failed.
Uninstalling the driver and trying again had the same effect, windows says the drivers are up to date.
Idle at 41c, 100% load in skyrim or dueces ex has it topped off at 65-70c.

PSU: Corsair GS600
A year old, etc.


My friend seems to think the way I tried to install windows bricked my box.

I put the new mobo in with all listed Hardware.
Tried to boot my old windows 7 installation, and obv that didnt work.
Got a windows prof, and upgraded, preserving my files on the hdd.

Since then Ive done the the following

What I've done so far after installing the hardware/the above
4 passes of memtest, 0 errors.
Repaired windows 7 installation.
Formatted the drive, reinstalled the OS
Set the ram timers to 9-10-9-27, then to 9-9-9-24

 

[writhziden]

[list=1]
[*]

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xthequwit\Windows_NT6_BSOD_jcgriff2\122911-17296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a07000 PsLoadedModuleList = 0xfffff800`02c4ce90
Debug session time: Thu Dec 29 10:49:00.706 2011 (GMT-7)
System Uptime: 0 days 1:11:33.331
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff80080bfe310, 2, 1, fffff80002a900e2}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+1e2 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff80080bfe310, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a900e2, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb80e8
 fffff80080bfe310 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerWaitTest+1e2
fffff800`02a900e2 f0490fbaaf9044000000 lock bts qword ptr [r15+4490h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  PMB.exe

TRAP_FRAME:  fffff80000ba2600 -- (.trap 0xfffff80000ba2600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a900e2 rsp=fffff80000ba2790 rbp=fffffa8007922788
 r8=fffff80002bfc001  r9=0000000000000002 r10=0000000000000055
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiTimerWaitTest+0x1e2:
fffff800`02a900e2 f0490fbaaf9044000000 lock bts qword ptr [r15+4490h],0 ds:aa70:00000000`00004490=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a86be9 to fffff80002a87640

STACK_TEXT:  
fffff800`00ba24b8 fffff800`02a86be9 : 00000000`0000000a fffff800`80bfe310 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba24c0 fffff800`02a85860 : 00000000`00000000 00000000`00068bff fffffa80`079e9208 fffffa80`07922788 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2600 fffff800`02a900e2 : fffff880`009e8180 fffffa80`079226c0 fffff800`02bf9e80 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00ba2790 fffff800`02a92ead : fffffa80`07922780 fffffa80`079227c8 fffffa80`079227c8 00000000`00000102 : nt!KiTimerWaitTest+0x1e2
fffff800`00ba2810 fffff800`02a92dee : 00000009`ff065452 fffff800`00ba2e88 00000000`00043155 fffff800`02bfcd28 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00ba2e60 fffff800`02a92bd7 : fffffa80`086271c1 fffffa80`00043155 00000000`00000000 00000000`00000055 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`02a8a165 : 00000000`00000000 fffffa80`07680580 00000000`00000000 fffff880`0147ca00 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`02a89f7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0836d090 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerWaitTest+1e2
fffff800`02a900e2 f0490fbaaf9044000000 lock bts qword ptr [r15+4490h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerWaitTest+1e2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+1e2

BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+1e2

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xthequwit\Windows_NT6_BSOD_jcgriff2\122911-22890-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02ca1e90
Debug session time: Thu Dec 29 11:21:50.366 2011 (GMT-7)
System Uptime: 0 days 0:10:25.584
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8886, fffffa8000d0e660, fffffa8000d2a560, 507}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+117c3 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008886, The subtype of the bugcheck.
Arg2: fffffa8000d0e660
Arg3: fffffa8000d2a560
Arg4: 0000000000000507

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


BUGCHECK_STR:  0x1a_8886

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002a70de3 to fffff80002adc640

STACK_TEXT:  
fffff880`080c2768 fffff800`02a70de3 : 00000000`0000001a 00000000`00008886 fffffa80`00d0e660 fffffa80`00d2a560 : nt!KeBugCheckEx
fffff880`080c2770 fffff800`02abe034 : fffff8a0`027e0b68 00000000`00000002 fffff8a0`00000001 fffff8a0`027e0b68 : nt! ?? ::FNODOBFM::`string'+0x117c3
fffff880`080c2800 fffff800`02db82a9 : fffffa80`08194b20 fffff6fc`40031620 fffff8a0`00000002 00000000`00000000 : nt!MiValidateImagePages+0x244
fffff880`080c28b0 fffff800`02db83e8 : ffffffff`ffffffff 00000000`00000001 fffff8a0`027e1000 00000000`00000097 : nt!MiSwitchBaseAddress+0x61
fffff880`080c28e0 fffff800`02dd8eff : 00000000`00000004 00000000`00000080 00000000`01000000 00000000`01000000 : nt!MiRelocateImageAgain+0x100
fffff880`080c2930 fffff800`02db7b22 : fffff880`080c2b80 fffff880`080c2ca0 00000000`00000000 fffff880`080c2b78 : nt!MmCreateSection+0x2df
fffff880`080c2b30 fffff800`02adb8d3 : fffffa80`06edc060 00000000`0030de08 fffff880`080c2bc8 00000000`00000000 : nt!NtCreateSection+0x171
fffff880`080c2bb0 00000000`777a17ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0030dde8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777a17ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+117c3
fffff800`02a70de3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+117c3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0x1a_8886_nt!_??_::FNODOBFM::_string_+117c3

BUCKET_ID:  X64_0x1a_8886_nt!_??_::FNODOBFM::_string_+117c3

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xthequwit\Windows_NT6_BSOD_jcgriff2\122911-23296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0285c000 PsLoadedModuleList = 0xfffff800`02aa1e90
Debug session time: Thu Dec 29 17:23:07.699 2011 (GMT-7)
System Uptime: 0 days 0:06:30.917
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 1097, 4400016, fffffa80071b1c10}

GetPointerFromAddress: unable to read from fffff80002b0d0e8
Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000004400016, Memory contents of the pool block
Arg4: fffffa80071b1c10, Address of the block of pool being deallocated

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


POOL_ADDRESS:  fffffa80071b1c10 

FREED_POOL_TAG:  Irp 

BUGCHECK_STR:  0xc2_7_Irp 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002a06be9 to fffff800028dc640

STACK_TEXT:  
fffff880`02f8c658 fffff800`02a06be9 : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`04400016 : nt!KeBugCheckEx
fffff880`02f8c660 fffff800`028dfba5 : 00000000`00000001 00000000`00000002 fffff880`02f64180 00000000`00000000 : nt!ExDeferredFreePool+0x1201
fffff880`02f8c710 fffff880`01984bce : 00000000`02985801 fffff800`02985801 fffffa80`09550848 00000000`00000000 : nt!IopfCompleteRequest+0x4c5
fffff880`02f8c7f0 fffff800`028dfa91 : 00000000`00000000 fffff800`02818156 fffffa80`0797eea0 00000000`00002000 : CLASSPNP!TransferPktComplete+0x1ce
fffff880`02f8c870 fffff880`00e3c41a : 00000000`00002000 00000000`00000001 fffffa80`06f6db80 00000000`00000000 : nt!IopfCompleteRequest+0x3b1
fffff880`02f8c950 fffff880`00e3c242 : fffffa80`06f6db80 fffff880`00e3eb53 fffffa80`06d65010 fffffa80`0799b1b0 : ataport!IdeCompleteScsiIrp+0x62
fffff880`02f8c980 fffff880`00e36e32 : 00000000`00000000 00000000`00000000 fffffa80`0756b500 fffffa80`0799b1b0 : ataport!IdeCommonCrbCompletion+0x5a
fffff880`02f8c9b0 fffff880`00e3f805 : fffffa80`0756a1a0 fffffa80`06f6db80 00000000`00000000 fffffa80`06f6db80 : ataport!IdeTranslateCompletedRequest+0x236
fffff880`02f8cae0 fffff880`00e3f104 : fffffa80`0756a1a0 00000000`00000000 fffffa80`0756a1a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
fffff880`02f8cc10 fffff800`028e7b1c : fffff880`02f64180 00000000`53807d2c fffffa80`0756a050 fffffa80`0756a118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02f8ccd0 fffff800`028d436a : fffff880`02f64180 fffff880`02f6ef80 00000000`00000000 fffff880`00e3ef5c : nt!KiRetireDpcList+0x1bc
fffff880`02f8cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
CLASSPNP!TransferPktComplete+1ce
fffff880`01984bce 837c243002      cmp     dword ptr [rsp+30h],2

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  CLASSPNP!TransferPktComplete+1ce

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME:  CLASSPNP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7929b

FAILURE_BUCKET_ID:  X64_0xc2_7_Irp__CLASSPNP!TransferPktComplete+1ce

BUCKET_ID:  X64_0xc2_7_Irp__CLASSPNP!TransferPktComplete+1ce

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


[/list]

The above are system related crashes. To rule out system file corruption, run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[zigzag3143]

ALSO YOU MIGHT WANT TO REMOVE THIS


Related to Pando Media Booster a tiny (2MB) UI-less client that enables you to cost effectively stream full-screen HD video. Note: Located in \%Program Files%\Pando Networks\Media Booster\

 

[xthequwit]

I was running SFC, it came back with no problems.

Pando is a program that League of Legends uses to get their install on.

 

[writhziden]

I was running SFC, it came back with no problems.

Pando is a program that League of Legends uses to get their install on.

Yeah, I kinda figured that was the case. Since your blue screens are rather inconclusive, run Driver Verifier as follows:
1. Backup your system and user files
2. Create a system restore point
3. If you do not have a Windows 7 DVD, Create a system repair disc
4. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.

Thanks to zigzag3143 for contributing to the above steps.

If verifying all drivers at once causes blue screens with no dmp files, you may need to run Driver Verifier on one non-Microsoft driver at a time to determine any bad drivers.

 

[xthequwit]

I was running SFC, it came back with no problems.

Pando is a program that League of Legends uses to get their install on.

Yeah, I kinda figured that was the case. Since your blue screens are rather inconclusive, run Driver Verifier as follows:
1. Backup your system and user files
2. Create a system restore point
3. If you do not have a Windows 7 DVD, Create a system repair disc
4. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.

Thanks to zigzag3143 for contributing to the above steps.

If verifying all drivers at once causes blue screens with no dmp files, you may need to run Driver Verifier on one non-Microsoft driver at a time to determine any bad drivers.

K trying this.

 

[xthequwit]

Ok, I didnt have to start in safe mode.
Do I just wait 24 hours? Anyway to expedite a BSoD?
Should I just do what Ive been doing or leave the computer on and gently stroke its hair while telling it, that everything is going to be ok. DONT LOOK BACK AS LONG AS IVE GOT YOU WE'LL MAKE IT!
?

 

[writhziden]

Ok, I didnt have to start in safe mode.
Do I just wait 24 hours? Anyway to expedite a BSoD?
Should I just do what Ive been doing or leave the computer on and gently stroke its hair while telling it, that everything is going to be ok. DONT LOOK BACK AS LONG AS IVE GOT YOU WE'LL MAKE IT!
?

Use it as you normally would. If you do not receive any blue screen errors for ~48 hours, disable Verifier and post back.

 

[xthequwit]

Ok it BSoD, was trying to install League of Legends again. ;.;

It said something about my IRQ and etc, also my belkin gamepad turned off.

 

[writhziden]

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xthequwit\123011-21593-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 (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a1c000 PsLoadedModuleList = 0xfffff800`02c61670
Debug session time: Fri Dec 30 03:29:24.928 2011 (UTC - 7:00)
System Uptime: 0 days 0:49:05.147
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {f0, 2, 0, fffff880069bb3d3}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_FlushAdapterDBs+17 )

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: 00000000000000f0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880069bb3d3, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ccb100
 00000000000000f0 

CURRENT_IRQL:  2

FAULTING_IP: 
USBPORT!USBPORT_FlushAdapterDBs+17
fffff880`069bb3d3 488b4940        mov     rcx,qword ptr [rcx+40h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f8c960 -- (.trap 0xfffff88002f8c960)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800933a050
rdx=fffffa8009d99990 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880069bb3d3 rsp=fffff88002f8caf8 rbp=fffffa800933a050
 r8=0000000000000000  r9=00000000000000b0 r10=fffff88002f64dc0
r11=fffffa8007cd4b10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
USBPORT!USBPORT_FlushAdapterDBs+0x17:
fffff880`069bb3d3 488b4940        mov     rcx,qword ptr [rcx+40h] ds:fffffa80`0933a090=fffffa800933a1a0
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a981e9 to fffff80002a98c40

STACK_TEXT:  
fffff880`02f8c818 fffff800`02a981e9 : 00000000`0000000a 00000000`000000f0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f8c820 fffff800`02a96e60 : fffffa80`07cd4000 fffffa80`07cd4b00 00000000`00000001 fffffa80`0933a1a0 : nt!KiBugCheckDispatch+0x69
fffff880`02f8c960 fffff880`069bb3d3 : 00000000`00000000 00000000`00000000 fffffa80`0a05f010 fffffa80`09d99990 : nt!KiPageFault+0x260
fffff880`02f8caf8 fffffa80`0933a1a0 : fffffa80`09d99d28 fffffa80`09d99990 fffffa80`0933a1a0 fffffa80`0000000f : USBPORT!USBPORT_FlushAdapterDBs+0x17
fffff880`02f8cb28 fffffa80`09d99d28 : fffffa80`09d99990 fffffa80`0933a1a0 fffffa80`0000000f fffffa80`094f0478 : 0xfffffa80`0933a1a0
fffff880`02f8cb30 fffffa80`09d99990 : fffffa80`0933a1a0 fffffa80`0000000f fffffa80`094f0478 fffffa80`09d99b90 : 0xfffffa80`09d99d28
fffff880`02f8cb38 fffffa80`0933a1a0 : fffffa80`0000000f fffffa80`094f0478 fffffa80`09d99b90 00000000`ffffff02 : 0xfffffa80`09d99990
fffff880`02f8cb40 fffffa80`0000000f : fffffa80`094f0478 fffffa80`09d99b90 00000000`ffffff02 00000000`00000000 : 0xfffffa80`0933a1a0
fffff880`02f8cb48 fffffa80`094f0478 : fffffa80`09d99b90 00000000`ffffff02 00000000`00000000 fffff880`069b9b28 : 0xfffffa80`0000000f
fffff880`02f8cb50 fffffa80`09d99b90 : 00000000`ffffff02 00000000`00000000 fffff880`069b9b28 fffffa80`0933aeb0 : 0xfffffa80`094f0478
fffff880`02f8cb58 00000000`ffffff02 : 00000000`00000000 fffff880`069b9b28 fffffa80`0933aeb0 fffff880`07228744 : 0xfffffa80`09d99b90
fffff880`02f8cb60 00000000`00000000 : fffff880`069b9b28 fffffa80`0933aeb0 fffff880`07228744 fffffa80`00000000 : 0xffffff02


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_FlushAdapterDBs+17
fffff880`069bb3d3 488b4940        mov     rcx,qword ptr [rcx+40h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  USBPORT!USBPORT_FlushAdapterDBs+17

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c08

FAILURE_BUCKET_ID:  X64_0xD1_VRF_USBPORT!USBPORT_FlushAdapterDBs+17

BUCKET_ID:  X64_0xD1_VRF_USBPORT!USBPORT_FlushAdapterDBs+17

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

This is a driver verified blue screen crash (I say this for informational purposes, not because you did anything wrong). It is likely related to a USB device plugged into your computer; it was probably due to your gamepad device since you said it turned off, but it may have been due to other underlying issues, as well. Run through the steps in http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html and see if it resolves the issue with the gamepad. Pay close attention to not plug in the gamepad during the applied fixes.

Good luck!

 

[xthequwit]

K followed the directions, hopefully this is solved.
Thanks for the help...now I wait for the blue screen of death...the monster in my closet.

 

[writhziden]

K followed the directions, hopefully this is solved.
Thanks for the help...now I wait for the blue screen of death...the monster in my closet.

We'll be here waiting to push that monster back into the closet. Good luck!

 

[xthequwit]

K followed the directions, hopefully this is solved.
Thanks for the help...now I wait for the blue screen of death...the monster in my closet.

We'll be here waiting to push that monster back into the closet. Good luck!

...Oh hey...nice to see the cookie monster avatar again.

;.;

I was playing League with the gamepad plugged in, the entire computer froze for 5 seconds-ish I regained control for a few seconds, then it BSoD.

 

[writhziden]

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xthequwit\123011-21234-01\123011-21234-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`02a5e000 PsLoadedModuleList = 0xfffff800`02ca3670
Debug session time: Fri Dec 30 10:58:01.131 2011 (UTC - 7:00)
System Uptime: 0 days 0:16:16.366
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80057d0d000, 0, fffff88002cf59ba, 5}


Could not read faulting driver name
Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkEscape+d6 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80057d0d000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88002cf59ba, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0d100
 fffff80057d0d000 

FAULTING_IP: 
dxgkrnl!DxgkEscape+d6
fffff880`02cf59ba 483b38          cmp     rdi,qword ptr [rax]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x50

PROCESS_NAME:  League of Lege

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800afbf6e0 -- (.trap 0xfffff8800afbf6e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80057d0d000 rbx=0000000000000000 rcx=fffffa8007b71550
rdx=000000000f2ce800 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002cf59ba rsp=fffff8800afbf870 rbp=fffff8800afbfca0
 r8=000000000000016b  r9=0000000000000006 r10=fffff9600022fbf0
r11=fffff8800afbfbe8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgkrnl!DxgkEscape+0xd6:
fffff880`02cf59ba 483b38          cmp     rdi,qword ptr [rax] ds:3000:fffff800`57d0d000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a853bf to fffff80002adac40

STACK_TEXT:  
fffff880`0afbf578 fffff800`02a853bf : 00000000`00000050 fffff800`57d0d000 00000000`00000000 fffff880`0afbf6e0 : nt!KeBugCheckEx
fffff880`0afbf580 fffff800`02ad8d6e : 00000000`00000000 fffff800`57d0d000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`0afbf6e0 fffff880`02cf59ba : 00000000`ffffd833 00000000`00000000 00000000`00000003 00000000`00000003 : nt!KiPageFault+0x16e
fffff880`0afbf870 fffff960`0022fc02 : 00000000`00000000 fffffa80`0a227060 00000000`7efa4000 00000000`00000020 : dxgkrnl!DxgkEscape+0xd6
fffff880`0afbfbf0 fffff800`02ad9ed3 : fffffa80`0a227060 00000000`000007b0 00000000`00000000 fffffa80`095bf700 : win32k!NtGdiDdDDIEscape+0x12
fffff880`0afbfc20 00000000`73d2148a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0f2ce7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73d2148a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DxgkEscape+d6
fffff880`02cf59ba 483b38          cmp     rdi,qword ptr [rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgkrnl!DxgkEscape+d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa

FAILURE_BUCKET_ID:  X64_0x50_VRF_dxgkrnl!DxgkEscape+d6

BUCKET_ID:  X64_0x50_VRF_dxgkrnl!DxgkEscape+d6

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

Alright, this is with verifier enabled and is due to DirectX. Go through the steps in Diagnosing basic problems with DirectX to see if it resolves the issue.


If you go through the update for your display card as specified in the steps for resolving DirectX issues, do so as follows:

1. Download and install Driver Sweeper
2. Download the latest driver for your display card from amd
3. Click Start Menu
4. Right Click My Computer
5. Click Manage
6. Click Device Manager from the list on the left
7. Click the + next to Display adapter
8. Right click your amd display/graphics card device
9. Click Uninstall
10. Check the box to Delete driver software for the device
11. Click OK
12. Restart your computer in safe mode
13. Run Driver Sweeper, select display card amd drivers, analyze, clean
14. Restart your computer
15. Install the latest drivers

 

[xthequwit]

When asked to click the "Change settings" button on the Troubleshoot tab of the advanced settings, it is grey and I am unable to click it.
D:

 

[writhziden]

When asked to click the "Change settings" button on the Troubleshoot tab of the advanced settings, it is grey and I am unable to click it.
D:

That just means your driver does not allow you to change settings. Ignore that step in the guide as it does not apply to you. Your display driver optimizes those settings without manual input.

 

[xthequwit]

When asked to click the "Change settings" button on the Troubleshoot tab of the advanced settings, it is grey and I am unable to click it.
D:

That just means your driver does not allow you to change settings. Ignore that step in the guide as it does not apply to you. Your display driver optimizes those settings without manual input.

I figured, ok did the rest...safe mode cleansing and such.

The drivers failed two unspecified packages again, apparently no recourse.

To note, I noticed my belkin n52te doesnt list W7 as a supported OS.
without its drivers, its a comfortable keyboard...but with vista drivers it a timebomb maybe? Many fan sites recommended installing the vista's because "7 is just a pretty vista". Seemed crude but Im not one to throw a 70 dollar hand couch in the trash.

;.;

tl;dr: I installed vista drivers on w7 for a gamepad because Im dumb, have i summoned the harbingers of the apocalypse?

 

[writhziden]

When asked to click the "Change settings" button on the Troubleshoot tab of the advanced settings, it is grey and I am unable to click it.
D:

That just means your driver does not allow you to change settings. Ignore that step in the guide as it does not apply to you. Your display driver optimizes those settings without manual input.

I figured, ok did the rest...safe mode cleansing and such.

The drivers failed two unspecified packages again, apparently no recourse.

To note, I noticed my belkin n52te doesnt list W7 as a supported OS.
without its drivers, its a comfortable keyboard...but with vista drivers it a timebomb maybe? Many fan sites recommended installing the vista's because "7 is just a pretty vista". Seemed crude but Im not one to throw a 70 dollar hand couch in the trash.

;.;

tl;dr: I installed vista drivers on w7 for a gamepad because Im dumb, have i summoned the harbingers of the apocalypse?

Depends on how you installed them. As long as the installation procedure matched the methods described in http://www.sevenforums.com/tutorials/98073-drivers-install-vista-drivers-windows-7-a.html, they should work fine. Occasionally, that method does cause conflicts, but since your keyboard is not showing up as a source of the blue screens after doing the USB fix, you are probably safe.

 

[xthequwit]

Depends on how you installed them. As long as the installation procedure matched the methods described in http://www.sevenforums.com/tutorials/98073-drivers-install-vista-drivers-windows-7-a.html, they should work fine. Occasionally, that method does cause conflicts, but since your keyboard is not showing up as a source of the blue screens after doing the USB fix, you are probably safe.

EDIT:I uninstalled the old ones first, promise.
Using the above tutorial
Installed the drivers with vista comp and admin enabled.
rebooted when prompted
the gamepad wasnt detected so I unplugged/replugged, windows searched for drivers and then...
Youll never guess.

BSOD!
;.;


It wasnt detecting it on start up before, but I didnt think much of it. Error code 43 in the device manager.

 

[writhziden]

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xthequwit\123011-23859-01\123011-23859-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`02c1d000 PsLoadedModuleList = 0xfffff800`02e62670
Debug session time: Fri Dec 30 14:13:05.613 2011 (UTC - 7:00)
System Uptime: 0 days 0:05:31.847
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002c9dbb6}

Unable to load image \SystemRoot\system32\drivers\JmtFltr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for JmtFltr.sys
*** ERROR: Module load completed but symbols could not be loaded for JmtFltr.sys
Probably caused by : JmtFltr.sys ( JmtFltr+a5df )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c9dbb6, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ecc100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeSetEvent+16
fffff800`02c9dbb6 f6037f          test    byte ptr [rbx],7Fh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880031af1f0 -- (.trap 0xfffff880031af1f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c9dbb6 rsp=fffff880031af380 rbp=0000000000000002
 r8=0000000000000000  r9=0000000000000000 r10=fffff88009d7f000
r11=fffff9800aa72f20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeSetEvent+0x16:
fffff800`02c9dbb6 f6037f          test    byte ptr [rbx],7Fh ds:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c991e9 to fffff80002c99c40

STACK_TEXT:  
fffff880`031af0a8 fffff800`02c991e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`031af0b0 fffff800`02c97e60 : 00000000`00000000 00000000`00040001 00000000`0000000e 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031af1f0 fffff800`02c9dbb6 : fffff800`02e4c260 00000000`00000280 fffffa80`06b2c340 fffff800`02cc3972 : nt!KiPageFault+0x260
fffff880`031af380 fffff880`09d7d5df : fffffa80`0848c340 00000000`00000000 fffffa80`07a81400 fffff980`0aa72ca0 : nt!KeSetEvent+0x16
fffff880`031af3f0 fffffa80`0848c340 : 00000000`00000000 fffffa80`07a81400 fffff980`0aa72ca0 00000000`00000000 : JmtFltr+0xa5df
fffff880`031af3f8 00000000`00000000 : fffffa80`07a81400 fffff980`0aa72ca0 00000000`00000000 fffffa80`07a81410 : 0xfffffa80`0848c340


STACK_COMMAND:  kb

FOLLOWUP_IP: 
JmtFltr+a5df
fffff880`09d7d5df ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  JmtFltr+a5df

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: JmtFltr

IMAGE_NAME:  JmtFltr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  46fd3439

FAILURE_BUCKET_ID:  X64_0xA_VRF_JmtFltr+a5df

BUCKET_ID:  X64_0xA_VRF_JmtFltr+a5df

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

Update the following drivers if possible:

JmtFltr	fffff880`09d73000	fffff880`09d7e580	Fri Sep 28 11:04:57 2007 (46fd3439)	0001641e	None	JmtFltr.sys
vhidmini	fffff880`07df8000	fffff880`07dfb680	Fri Sep 28 11:21:57 2007 (46fd3835)	0000ddea		vhidmini.sys

You may find them with the help of Driver Reference