Hello,
here is a quick update; I'm receiving a BSOD with no specific error. I don't know why or when it happens, it's really random.
I don't know what to-do this time, as it's hard to think what the problem could be.
I've attached the latest mini dump which just occurred a few moments ago.
It seems to have been caused by the volume shadow copy service.Code:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 8b9b4be1, The address that the exception occurred at Arg3: 8d435b08, Exception Record Address Arg4: 8d4356e0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: volsnap!VspTableCompareRoutine+11 8b9b4be1 8b31 mov esi,dword ptr [ecx] EXCEPTION_RECORD: 8d435b08 -- (.exr 0xffffffff8d435b08) ExceptionAddress: 8b9b4be1 (volsnap!VspTableCompareRoutine+0x00000011) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000010 Attempt to read from address 00000010 CONTEXT: 8d4356e0 -- (.cxr 0xffffffff8d4356e0) eax=00000018 ebx=866285ec ecx=00000010 edx=a5068000 esi=00000000 edi=85b146ec eip=8b9b4be1 esp=8d435bd0 ebp=8d435bd4 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 volsnap!VspTableCompareRoutine+0x11: 8b9b4be1 8b31 mov esi,dword ptr [ecx] ds:0023:00000010=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00000010 READ_ADDRESS: GetPointerFromAddress: unable to read from 83174718 Unable to read MiSystemVaType memory at 83154160 00000010 FOLLOWUP_IP: volsnap!VspTableCompareRoutine+11 8b9b4be1 8b31 mov esi,dword ptr [ecx] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from 830c540f to 8b9b4be1 STACK_TEXT: 8d435bd4 830c540f 85b146ec 87fea198 00000010 volsnap!VspTableCompareRoutine+0x11 8d435bec 83044a4f 87fea198 8d435c0c 00000000 nt!FindNodeOrParent+0x20 8d435c00 8b9adcef 85b146ec 87fea198 85b14598 nt!RtlDeleteElementGenericTableAvl+0x15 8d435c14 8b9b38c9 85b146ec 87fea198 866285e0 volsnap!AvlDeleteElementGenericTable+0x1f 8d435c2c 8b9aa559 87fea198 00000000 87fea1d0 volsnap!VspWriteVolumePhase5+0x1d 8d435cdc 8b9ccd1b 00b14598 87fea1d0 00000000 volsnap!VspAcquireNonPagedResource+0xff 8d435d34 8b9bee59 00fea198 00000000 86675470 volsnap!VspWriteVolumePhase4+0x171 8d435d50 8321a9df 85806cf4 a0cf70dc 00000000 volsnap!VspWorkerThread+0x83 8d435d90 830cc1d9 8b9bedd6 86675730 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: volsnap!VspTableCompareRoutine+11 FOLLOWUP_NAME: MachineOwner MODULE_NAME: volsnap IMAGE_NAME: volsnap.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf26 STACK_COMMAND: .cxr 0xffffffff8d4356e0 ; kb FAILURE_BUCKET_ID: 0x7E_volsnap!VspTableCompareRoutine+11 BUCKET_ID: 0x7E_volsnap!VspTableCompareRoutine+11 Followup: MachineOwner ---------
Run a secure file check.
SFC /SCANNOW Command - System File Checker
also remove all external devices but the keyboard and mouse for the moment.
I'd like to say, thank you for your help.
I run the test and it said that I had some corrupted which it said it repaired. Hopefully this will fix the BSOD.
If I receive another I will post here.
If you get this you may also want to run a disk check.
Disk Check
Need to find out why the files got corrupted in the first place.
I'm really starting to think either the memory or harddrive is bad, this problem has gone on way too long.
And no, check disk should not run instantaneously. It should take a bit of time and display it's progress on the screen as it goes.
At that point we're not even in windows though, which points even more to a hard ware issue.
I would like to get a second opinion before telling you to replace hardware.
Did we ever do a normal memory check?
Sorry I have so many threads I'm in right now I sometimes forget things.
Memory Diagnostics Tool
See, little details like that go a long way in troubleshooting.
You may just need to update your motherboard bios.
This is a tricky thing to do, typically it goes smoothly, but if something does go wrong it's very likely the machine will never boot again.
For bios updates you generally want to go to the motherboard manufacturer's website.
Quote