05-24-2016 05:21 AM
A couple of days ago I bought a new lenovo y700-17isk laptop. Just after windows 10 installation I started to get blue screens then using computer or even then I left pc idle. I updated all the latest drivers and updates but still the problem persists periodically. How this can be happening on a new laptop with fresh windows installed? I was reading that this might be because of the bios problem with these models(my bios version is CDCN27WW) and this is a well known issue for lenovo. I am wondering should I hope that this problem will be solved with bios update? or should I return this pc because I cant use it of bsod getting every hour. I tried to reinstall windows two times tried different version still the same..
05-24-2016 06:56 AM - edited 05-24-2016 07:02 AM
It would help to see the details of the memory dump from the BSOD, but by default Windows 10 creates one that is typically too large to upload to a site that can analyze it so you can paste the results, so you will first have to configure Windows 10 to create a Small Memory Dump, recreate the issue, and then upload the .dmp file for analysis.
How to Configure Windows to create a small memory dump
The next time your computer has a BSOD, Windows will create a <date/timestamp> file in the C:\Windows\minidump folder.
Once the BSOD has occurred and you have rebooted, browse to the OSR link below
Once the analysis is complete (a couple of minutes), then copy and paste the results into your reply here, and hopefully it will give insight as to the cause of the BOD's
OSR's Instant Online Crash Analysis
Once you have done so, you can then go back and set the setting for the debugging information back to Window's default setting of Automatic.
PS I do not see any BIOS update avaiable on Lenovo's site for the y700-17isk, so that currently does not seem to be a solution unless they have a BETA version available only from support. Most likely since this is a Windows BSOD, it is a driver issue that hopefully the .dmp will identify.
05-24-2016 02:37 PM
okay, so here it is.
thank you in advance
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
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80139d9e75d, The address that the exception occurred at
Arg3: ffffd000d3dfb098, Exception Record Address
Arg4: ffffd000d3dfa8b0, Context Record Address
TRIAGER: Could not open triage file : e:\dump_analysis\program\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".
fffff801`39d9e75d 48394af0 cmp qword ptr [rdx-10h],rcx
EXCEPTION_RECORD: ffffd000d3dfb098 -- (.exr 0xffffd000d3dfb098)
ExceptionAddress: fffff80139d9e75d (nt!MiDemoteCombinedPte+0x0000000000000039)
ExceptionCode: c0000005 (Access violation)
Attempt to read from address ffffffffffffffff
CONTEXT: ffffd000d3dfa8b0 -- (.cxr 0xffffd000d3dfa8b0)
rax=ffffa3c47272b137 rbx=a9e00001fe2e9963 rcx=0000000000000001
rdx=fdfff6e00107e0e8 rsi=ffffe000bdea1000 rdi=fffff781000796f0
rip=fffff80139d9e75d rsp=ffffd000d3dfb2d0 rbp=ffffd000d3dfb4b0
r8=8000000000000000 r9=0000007ffffffff8 r10=0000098000000000
r11=0000058000000000 r12=00000000000000d1 r13=fffff6e00107e0e8
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
fffff801`39d9e75d 48394af0 cmp qword ptr [rdx-10h],rcx ds:002b:fdfff6e0`0107e0d8=????????????????
Resetting default scope
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
fffff801`39d9e75d 48394af0 cmp qword ptr [rdx-10h],rcx
LAST_CONTROL_TRANSFER: from fffff80139cc58e9 to fffff80139d9e75d
ffffd000`d3dfb2d0 fffff801`39cc58e9 : 00000003`00000000 ffffd000`d3dfb4b0 a9e00001`fe2e9963 00000000`73576d4d : nt!MiDemoteCombinedPte+0x39
ffffd000`d3dfb3b0 fffff801`39ceae12 : fffff801`39f83878 00000000`00002082 fffff801`39f83878 00000000`00006f06 : nt!MiAgeWorkingSet+0x1079
ffffd000`d3dfb700 fffff801`39cea83b : 00000000`00000000 ffffd000`d3dfb980 ffffd000`d3dfb8b0 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0x182
ffffd000`d3dfb7b0 fffff801`39c8ec4b : fffff801`00000000 00000000`00000000 00000000`0000012a 00000000`00000002 : nt!MiProcessWorkingSets+0x1fb
ffffd000`d3dfb960 fffff801`39dac9cd : 00000000`ffffffff 00000000`00000004 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0xa7
ffffd000`d3dfba20 fffff801`39d74b65 : ffffe000`b6f48040 00000000`00000080 fffff801`39dac87c 0067006e`00690074 : nt!KeBalanceSetManager+0x151
ffffd000`d3dfbb10 fffff801`39dce926 : ffffd000`d3b69180 ffffe000`b6f48040 fffff801`39d74b24 01d112f1`a01403f5 : nt!PspSystemThreadStartup+0x41
ffffd000`d3dfbb60 00000000`00000000 : ffffd000`d3dfc000 ffffd000`d3df5000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .cxr 0xffffd000d3dfa8b0 ; kb
*** Memory manager detected 47009 instance(s) of page corruption, target is likely to have memory corruption.
05-24-2016 05:47 PM
I have checked previous minidump files and it seems that I am getting different bsod every time sometimes the same, for example: DPC_WATCHDOG_VIOLATION (133), CRITICAL_PROCESS_DIED (ef), MEMORY_MANAGEMENT (1a), REGISTRY_FILTER_DRIVER_EXCEPTION (135), IRQL_NOT_LESS_OR_EQUAL (a)
here is another one more detailed.
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arg1: a3a01f5a6be8aa71, Reserved
Arg2: 0000000000000000, Reserved
Arg3: def415fc5883a396, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8026d35b780
ffffd000`2126efb8 00000000`00000000 : 00000000`00000109 a3a01f5a`6be8aa71 00000000`00000000 def415fc`5883a396 : nt!KeBugCheckEx