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: Frequent BSoD, random error messages.

29 Dec 2011   #1

Windows professional 64 bit
 
 
Frequent BSoD, random error messages.

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

My System SpecsSystem Spec
.

29 Dec 2011   #2

Windows 7 Home Premium 64 Bit
 
 

Code:
  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 ---------
  2. 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 ---------
  3. 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 ---------
The above are system related crashes. To rule out system file corruption, run SFC /SCANNOW Command - System File Checker
My System SpecsSystem Spec
29 Dec 2011   #3

Win 8 Release candidate 8400
 
 

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\
My System SpecsSystem Spec
.


29 Dec 2011   #4

Windows professional 64 bit
 
 

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

Pando is a program that League of Legends uses to get their install on.
My System SpecsSystem Spec
29 Dec 2011   #5

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by xthequwit View Post
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 System Restore 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.
My System SpecsSystem Spec
29 Dec 2011   #6

Windows professional 64 bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
Quote   Quote: Originally Posted by xthequwit View Post
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 System Restore 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.
My System SpecsSystem Spec
29 Dec 2011   #7

Windows professional 64 bit
 
 

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!
?
My System SpecsSystem Spec
29 Dec 2011   #8

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by xthequwit View Post
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.
My System SpecsSystem Spec
30 Dec 2011   #9

Windows professional 64 bit
 
 

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.
My System SpecsSystem Spec
30 Dec 2011   #10

Windows 7 Home Premium 64 Bit
 
 

Code:
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 USB Driver - General Fix for Problems 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!
My System SpecsSystem Spec
Reply

 Frequent BSoD, random error messages.





Thread Tools



Similar help and support threads for2: Frequent BSoD, random error messages.
Thread Forum
BSOD after random, different error messages. BSOD Help and Support
Solved Random BSOD's, various error messages. ntoskernel.exe? BSOD Help and Support
BSOD Random error messages 2nd fresh install BSOD Help and Support
Getting a BSOD at random times, at least 6 different error messages. BSOD Help and Support
BSOD multiple error messages / random BSOD Help and Support
Random BSOD's, many different error messages. BSOD Help and Support
Random BSOD's with random error messages after a new setup 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 12:55 PM.
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