Layback Bear,
Good question: I have been using them for quite awhile. As far as USB 2.0 or 3.0, how would I determine that? Would it be under the driver info under Device Manager?
Boozad,
Ok, after running verifier and trying a game (Star Trek Online) I have gotten a couple of BSOD's, but they aren't associating w/ WinDBg, just showing 'MEMORY' dumps under the Windows folder. Note both the Fan and the Logitech headset are not plugged in. I did include another DM log, but not sure it caught the most recent BSOD's. Opening them via WinDBg shows information is 'inconsistent':
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
************************************************************************
WARNING: Dump file has inconsistent set-bit count. Data may be missing.
************************************************************************
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*
http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to read KLDR_DATA_TABLE_ENTRY at fffffa80`069ba890 - NTSTATUS 0xC0000147
"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000`00000000.
Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0xfffff800`03218000 PsLoadedModuleList = 0xfffff800`0345c890
Debug session time: Sun Apr 12 14:32:06.379 2015 (UTC - 5:00)
System Uptime: 0 days 0:37:21.705
Unable to read KLDR_DATA_TABLE_ENTRY at fffffa80`069ba890 - NTSTATUS 0xC0000147
"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000`00000000.
Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
Unable to read KLDR_DATA_TABLE_ENTRY at fffffa80`069ba890 - NTSTATUS 0xC0000147
Page 8b48107f1 too large to be in the dump file.
WARNING: .reload failed, module list may be incomplete
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C1, {fffff9803248ec10, fffff9803248e317, 5103e8, 23}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff9803248ec10, address trying to free
Arg2: fffff9803248e317, address where bits are corrupted
Arg3: 00000000005103e8, (reserved)
Arg4: 0000000000000023, caller is freeing an address where nearby bytes within the same page have been corrupted
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
BUGCHECK_STR: 0xC1_23
SPECIAL_POOL_CORRUPTION_TYPE: 23
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff880042f872d to fffff880042f86e4
STACK_TEXT:
fffff800`04824c68 fffff880`042f872d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`042f86e4
fffff800`04824c70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffff880`042f872d
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
BUCKET_ID: CORRUPT_MODULELIST
FAILURE_BUCKET_ID: CORRUPT_MODULELIST
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:corrupt_modulelist
FAILURE_ID_HASH: {6a10ab2d-36f9-3117-3ae8-89baa6e43dd5}
Followup: MachineOwner
---------
I apologize for the copy/paste post, but I checked to make sure I had the symbol path file still loaded in WinDBg, and it's correct per the WinDBg forum post instructions. It may be redundant, but I wanted you to see the C1 Stop, in case it's not in the DM log.
