New
#1
BSOD, don't know exact cause.
As the title says I don't know the exact cause, whether it be drivers or faulty memory.
minidump attached at bottom
As the title says I don't know the exact cause, whether it be drivers or faulty memory.
minidump attached at bottom
Your dump file suggests that something connected via USB may be the issue.
Do you have a lot of peripherals connected to your system via USB?Code:.... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff8a012258841, 2, 0, fffff80002c85216} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iMapTransfer+24a ) 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: fffff8a012258841, 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: fffff80002c85216, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb2100 GetUlongFromAddress: unable to read from fffff80002eb21c0 fffff8a012258841 Paged pool CURRENT_IRQL: 2 FAULTING_IP: nt!RtlCopyMemoryNonTemporal+16 fffff800`02c85216 488b0411 mov rax,qword ptr [rcx+rdx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System
[QUOTE=TypeR;2013945]Your dump file suggests that something connected via USB may be the issue.
Do you have a lot of peripherals connected to your system via USB?[/QUOTEe]Code:.... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff8a012258841, 2, 0, fffff80002c85216} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iMapTransfer+24a ) 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: fffff8a012258841, 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: fffff80002c85216, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb2100 GetUlongFromAddress: unable to read from fffff80002eb21c0 fffff8a012258841 Paged pool CURRENT_IRQL: 2 FAULTING_IP: nt!RtlCopyMemoryNonTemporal+16 fffff800`02c85216 488b0411 mov rax,qword ptr [rcx+rdx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System
Nah, only 2 razor devices, one of which I've unplugged and the bsods have seemed to stop.
It was the razer nostromo if you're wondering.