New
#1
Random BSOD after copying data between USBs
I was copying files between USBs and after the process finished I got the BSOD.
I have a ASUS ROG G53SW and last week I changed the HD to a SSD Samsung 840 Pro.
I was copying files between USBs and after the process finished I got the BSOD.
I have a ASUS ROG G53SW and last week I changed the HD to a SSD Samsung 840 Pro.
Hi koolkat.
Yes, I mean I think so; I installed the software that came with the SSD, it made a update of SSD firmware, but IŽll make a double check.
Hi koolkat, the firmware is updated.
I checked and when I ran the tool, the firmware was already updated.
Here it is.
Don't know if can help, but this is the xml from the event log.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2014-08-25T02:38:03.730803900Z" />
<EventRecordID>6733</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Drimy_GamePlace</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">30</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>
After enabled the "Driver Verifier" I got a BSOD.
The log named "DRIMY_GAMEPLACE-Sun_08_31_2014__95439_61" was created in Safe Mode before deleting the verifier settings.
The log named "DRIMY_GAMEPLACE-Sun_08_31_2014__95750_90" was created in Normal Mode after deleting the verifier settings.
I made two because didn't know if deleting the verifier could cause any different result.
Hi Drimiter.
koolkat77 does not have assess to her debugging computer right now. So the late in response.
Based on the driver verifier, I would suggest you to uninstall the realtek audio driver and reinstall it afresh, from Notebooks & Ultrabooks - G53SW - ASUS
Then let us know how the computer is running.
______________________________________________
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {1f0, 2, 0, fffff8000308d325} *** WARNING: Unable to verify timestamp for MBfilt64.sys *** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys Probably caused by : MBfilt64.sys ( MBfilt64+1817 ) Followup: MachineOwner --------- 6: 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: 00000000000001f0, 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: fffff8000308d325, address which referenced memory Debugging Details: ------------------ OVERLAPPED_MODULE: Address regions for 'usbvideo' and 'btfilter.sys' overlap READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c0100 GetUlongFromAddress: unable to read from fffff800032c01c0 00000000000001f0 Nonpaged pool CURRENT_IRQL: 2 FAULTING_IP: nt!KeSetEvent+1e3 fffff800`0308d325 488b00 mov rax,qword ptr [rax] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre TRAP_FRAME: fffff880039f5950 -- (.trap 0xfffff880039f5950) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000001f0 rbx=0000000000000000 rcx=fffff880029d3210 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000308d325 rsp=fffff880039f5ae0 rbp=0000000000000000 r8=0000000000000000 r9=fffff88003717180 r10=00000000000001f0 r11=fffff80003240480 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe cy nt!KeSetEvent+0x1e3: fffff800`0308d325 488b00 mov rax,qword ptr [rax] ds:00000000`000001f0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80003088169 to fffff80003088bc0 STACK_TEXT: fffff880`039f5808 fffff800`03088169 : 00000000`0000000a 00000000`000001f0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`039f5810 fffff800`03086de0 : 00000000`00000160 00000000`00000000 00000000`0000000d fffff880`029d3208 : nt!KiBugCheckDispatch+0x69 fffff880`039f5950 fffff800`0308d325 : fffffa80`09bfd802 fffffa80`09bfd8d0 00000000`00000000 fffff980`0c932ea0 : nt!KiPageFault+0x260 fffff880`039f5ae0 fffff880`06cb4817 : fffff880`00000000 fffff980`00000008 fffff800`03236d00 fffffa80`09c42450 : nt!KeSetEvent+0x1e3 fffff880`039f5b50 fffff880`00000000 : fffff980`00000008 fffff800`03236d00 fffffa80`09c42450 fffffa80`09bfd8d0 : MBfilt64+0x1817 fffff880`039f5b58 fffff980`00000008 : fffff800`03236d00 fffffa80`09c42450 fffffa80`09bfd8d0 fffff800`035303fb : 0xfffff880`00000000 fffff880`039f5b60 fffff800`03236d00 : fffffa80`09c42450 fffffa80`09bfd8d0 fffff800`035303fb fffffa80`09bfd8d0 : 0xfffff980`00000008 fffff880`039f5b68 fffffa80`09c42450 : fffffa80`09bfd8d0 fffff800`035303fb fffffa80`09bfd8d0 fffffa80`09bfd8d0 : nt!ViPendingWorkers fffff880`039f5b70 fffffa80`09bfd8d0 : fffff800`035303fb fffffa80`09bfd8d0 fffffa80`09bfd8d0 fffff980`0c933000 : 0xfffffa80`09c42450 fffff880`039f5b78 fffff800`035303fb : fffffa80`09bfd8d0 fffffa80`09bfd8d0 fffff980`0c933000 fffff980`0c932ea0 : 0xfffffa80`09bfd8d0 fffff880`039f5b80 fffff800`0353047c : fffff800`03236d60 00000000`00000080 fffffa80`06d5a890 00000000`00000100 : nt!ViPendingCompleteAfterWait+0x7b fffff880`039f5bc0 fffff800`0332473a : 00000000`00000000 00000000`00000000 10000000`00000000 00000000`00000000 : nt!ViPendingWorkerThread+0x2c fffff880`039f5c00 fffff800`030798e6 : fffff880`009b3180 fffffa80`06d90b50 fffff880`009be0c0 00000010`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`039f5c40 00000000`00000000 : fffff880`039f6000 fffff880`039f0000 fffff880`039f58d0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: MBfilt64+1817 fffff880`06cb4817 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: MBfilt64+1817 FOLLOWUP_NAME: MachineOwner MODULE_NAME: MBfilt64 IMAGE_NAME: MBfilt64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a7267b0 FAILURE_BUCKET_ID: X64_0xA_VRF_MBfilt64+1817 BUCKET_ID: X64_0xA_VRF_MBfilt64+1817 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0xa_vrf_mbfilt64+1817 FAILURE_ID_HASH: {3414a0c9-f17d-f07d-746a-a89ad9b168e6} Followup: MachineOwner --------- 6: kd> lmvm MBfilt64 start end module name fffff880`06cb3000 fffff880`06cc1000 MBfilt64 T (no symbols) Loaded symbol image file: MBfilt64.sys Image path: \SystemRoot\system32\drivers\MBfilt64.sys Image name: MBfilt64.sys Timestamp: Fri Jul 31 09:10:32 2009 (4A7267B0) CheckSum: 0000FF02 ImageSize: 0000E000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4