New
#11
Sorry, I hadn't yet set up my computer to create minidumps. Here are the most recent few. I've also had difficulties booting. Still running off the HDD only.
Sorry, I hadn't yet set up my computer to create minidumps. Here are the most recent few. I've also had difficulties booting. Still running off the HDD only.
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
If memtest reveals no error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
InformationWhy Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
WarningBefore enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.
If there is no points, make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any.Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.
___________________________________________________________________________________
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff960001ac858, fffff88007368fd0, 0} Probably caused by : memory_corruption Followup: memory_corruption --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff960001ac858, Address of the instruction which caused the bugcheck Arg3: fffff88007368fd0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: win32k!xxxSendMessageTimeout+347 fffff960`001ac858 4c8927 mov qword ptr [rdi],r12 CONTEXT: fffff88007368fd0 -- (.cxr 0xfffff88007368fd0) rax=00000000fffffdcf rbx=000000000000003c rcx=00000000002ff484 rdx=fffff88007369908 rsi=000000000000000f rdi=0000000000000010 rip=fffff960001ac858 rsp=fffff880073699a0 rbp=fffff900c083a570 r8=fffff8800308cfc0 r9=fffff88007369db0 r10=fffff900c075a3e0 r11=fffff900c0800a70 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010297 win32k!xxxSendMessageTimeout+0x347: fffff960`001ac858 4c8927 mov qword ptr [rdi],r12 ds:002b:00000000`00000010=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x3B PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff960002098de to fffff960001ac858 STACK_TEXT: fffff880`073699a0 fffff960`002098de : 00000000`00000000 fffff900`c083a570 fffff900`c083a570 00000000`00000000 : win32k!xxxSendMessageTimeout+0x347 fffff880`07369a50 fffff960`001272d3 : 00000000`00000000 00000000`00000000 00000000`01040058 00000000`00001141 : win32k!xxxUpdateWindow2+0x12e fffff880`07369ac0 fffff960`00136e7c : fffff900`c083a570 fffff900`c083a570 fffff880`07369ca0 00000000`00001141 : win32k!xxxInternalInvalidate+0x1c3 fffff880`07369b40 fffff960`001bf529 : 00000000`00000000 fffff880`07369bd8 00000000`0004031a fffff880`07369ca0 : win32k!xxxRedrawWindow+0x1a0 fffff880`07369ba0 fffff800`02c8cad3 : fffffa80`0ab8b230 fffff880`07369bd8 00000000`00d4c0c0 00000000`00000020 : win32k!NtUserRedrawWindow+0xe9 fffff880`07369c20 00000000`73742dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0013ebe8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73742dd9 CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt 5 errors : !nt (fffff80002c8d390-fffff80002c8dea8) fffff80002c8d390 *7b 6f 70 30 66 0f 6f 78 40 66 44 0f 6f 40 50 66 {op0f.ox@fD.o@Pf ... fffff80002c8d3b0 *50 00 00 00 66 44 0f 6f a0 90 00 00 00 66 44 0f P...fD.o.....fD. fffff80002c8d3c0 6f a8 a0 00 00 00 66 44 *00 6f b0 b0 00 00 00 66 o.....fD.o.....f ... fffff80002c8dab0 *00 20 c0 48 89 01 0f 20 d0 48 89 41 08 0f 20 d8 . .H... .H.A.. . ... fffff80002c8dea0 db e3 c3 cc cc cc cc cc *00 0f 1f 80 00 00 00 00 ................ MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE STACK_COMMAND: .cxr 0xfffff88007368fd0 ; kb FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption ---------