New
#21
See you soon :)
This is what was causing the problem, btw:
All three crashdumps shows the same exact thing in that something previously has chewed off the upper byte of the memory address attempting to be used. Consistently the two 3rd-party drivers showing up for each crashdump is the Realtek network driver and the Avast virtualization driver. Updating them both (and/or switching to another AV solution) should do the trick as this appears too consistent to be caused by hardware.Code:1: 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: fffff80002ac2b45, Address of the instruction which caused the bugcheck Arg3: fffff8800a2d3530, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!ExpInterlockedPopEntrySListFault16+0 fffff800`02ac2b45 498b08 mov rcx,qword ptr [r8] CONTEXT: fffff8800a2d3530 -- (.cxr 0xfffff8800a2d3530) rax=0000000133f40004 rbx=fffffa8006b27a40 rcx=fffffa8006a24590 rdx=00fffa8006cff411 rsi=fffffa8006a24590 rdi=0000000000000001 rip=fffff80002ac2b45 rsp=fffff8800a2d3f10 rbp=0000000003abe9d0 r8=00fffa8006cff410 r9=0000000000000001 r10=fffffa8006a24590 r11=fffff8800a2d42d8 r12=0000000000000001 r13=fffff880009ea180 r14=0000000000000001 r15=0000000000000001 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 nt!ExpInterlockedPopEntrySListFault16: fffff800`02ac2b45 498b08 mov rcx,qword ptr [r8] ds:002b:00fffa80`06cff410=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: iexplore.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002dc7a27 to fffff80002ac2b45 STACK_TEXT: fffff880`0a2d3f10 fffff800`02dc7a27 : 00000000`03abd940 00000000`0000002b 00000000`77d22096 00000000`7405aa00 : nt!ExpInterlockedPopEntrySListFault16 fffff880`0a2d3f20 fffff800`02d92e2b : 00000000`03abe178 fffff880`0a2d44c0 00000000`00000000 00000000`00000001 : nt!ObCreateObject+0x47 fffff880`0a2d3f90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateEvent+0x9b FOLLOWUP_IP: nt!ExpInterlockedPopEntrySListFault16+0 fffff800`02ac2b45 498b08 mov rcx,qword ptr [r8] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ExpInterlockedPopEntrySListFault16+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 50e79935 STACK_COMMAND: .cxr 0xfffff8800a2d3530 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0 BUCKET_ID: X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0 Followup: MachineOwner ---------
However, concerning your recent experience with the hard freeze, I'm not quite sure if we're dealing with the same issue now and it may be something different entirely. Can you try to induce the freeze again (perhaps running the readiness tool and/or watching a video)?
Thank you for the information.
After my last post, I downloaded a bunch of my steam games just to reproduce a crash, previously I would have had 2-3 crashed during the download, but I had zero crashes. I also ran the readiness tool while I had multiple video's and websites open, but I had zero crashes. I will continue to push this to see if I can reproduce these crashes in the next few days.
Thanks again to both of you for the help.
Ok so I tried everything last night to induce a crash and couldn't so I went to bed pretty happy. This morning, I had 1 Youtube video playing and I heard that loud buzz from the speakers and my system crashed and restarted. Again, no BSOD, just a blackscreen after the noise and a restart. I ran the SF tool, files attached.
I'm seeing no signs of blue screening in the syslog but I do see reports of unexpected shutdowns. Nothing else we can gather so far. I did notice previously though that it reported it couldn't produce crashdumps because there wasn't enough space on the drive. Make sure the amount of free space on your Windows partition is at least the mount of your RAM and that your paging file set to be just as large plus set it so that the file exists on the Windows partition. Those are the best options to ensure that the system will be able to produce a crashdump when needed.
I recommend turning on Driver Verifier. Do not select the following checks: Force Pending I/O Requests, IRP Logging, and Low Resource Sim. Select all other checks. Make sure to restart system after you finish setup. If you experience a boot loop afterwards, go into Safe Mode by pressing F8 prior to Windows logo and disable DV there. Provide us any new crashdumps.
I reviewed your CrystalDiskInfo and I'm seeing both disconcerting and unusual values. However there's a good chance that this drive just has a very proprietary method of establishing SMART values which makes it difficult to interpret them. I normally would disregard this, but your symptoms lately sound similar to a disk I/O failure. Probably best to give that CHKDSK one more spin. If you see it correcting errors again as before, it most likely is conducive of a drive failure that's corrupting the file system on a continual basis.
However all this said is just speculation right now since we don't have any solid evidence to go on. Hopefully Driver Verifier will help us weed out all unruly drivers, but this is indeed sounding more and more like a hardware issue, which is most likely going to mean swapping hardware.
Ok thanks. I'll do these three things when I get off work.
Just curious, what type of hardware issue would only crash when watching videos? I never crash when playing games or running any other software. It seems like KoolKat may have been right and this is a LAN port problem on the motherboard. In the past, when I've had a hardware problem I would have always crashed while playing a game if it was the gpu, cpu, memory, or HDD.
It could be a whole assortment of problems, but yes the fact it seems to occur only from online video watching points finger at network activity, meaning the onboard network controller on the mobo or whatever network adapter you use. Have you actually tested with offline video playing?
No I haven't trying offline videos, but I can take a couple movies from my tablet and put them on my computer to test it out. I'll try that this weekend as well.
I'm getting a fantastic new crash where my screen goes white with some tiny colored lines. Still no BSOD. My event log shows the following error:
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D
files attached.
Also, I ran the Driver Verifier without errors. I also ran the Disk Checker and there were no errors found or repaired.
Last edited by Tusck; 23 Feb 2013 at 16:02.
So basically I know know that Nexus Mod Manager (Skyrim) is not playing well wth MSE, which is weird because it does on my other Vista system. Even after I uninstalled it, I kept getting the crash as described above (white screen with color bars), so I restored my computer to a point prior to installing it and the crashes are not happening any more.
However, I did get a BSOD, so I attached the files.
EDIT: I noticed that a dump file was not made due to lack of space. I'm not sure why that is or how to change it. The event log again says the BSOD was due to: Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D