M
MauroItaly
Hi,
two days ago I updated my DELL XPS 435T/9000 from 1709 to 1803.
Everything when fine but suspension behaviour.
I used it a lot in previous versions.
Now, my pc goes to sleep correctly but cannot restart.
When I restart it, CPU wake up (I hear fans running) , the screen remains black (it doesn't become blue), and after 5-10 secs it powers off and leaves a minidump (see below).
I suspected some driver (wifi, video) and made all possibile test I could imagine (update, degrades, removed drivers): no results.
Hidernations works perfectly.
Current BIOS is AMI A16, quite old (2010), but I got no problem when 1709 was running.
I changed ACPI from S3 to the only other alternative: S1. With S1, wakeup after suspension doesn't power off with minidump. The PC wakes up and stay powered, but the screen remains black.
I have no other idea but to forget suspension and use hinernation for the future, but I have bad feelings when my "work" PC has some problem.
How can I understand which driver could cause the problem?
Could 1803 version raise problem with a BIOS working with 1709?
Any idea will be appreciated.
Thank you in advance
Mauro
--------------------------
This is the minidump analisys:
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 8 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff800`fbe9f000 PsLoadedModuleList = 0xfffff800`fc24d170
Debug session time: Sun Aug 26 06:35:22.562 2018 (UTC - 4:00)
System Uptime: 0 days 0:04:31.351
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800fbf25780, The address that the exception occurred at
Arg3: ffffc700baaeae48, Exception Record Address
Arg4: ffffc700baaea690, Context Record Address
Debugging Details:
------------------
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".
FAULTING_IP:
nt!MiDemoteCombinedPte+40
fffff800`fbf25780 498378f001 cmp qword ptr [r8-10h],1
EXCEPTION_RECORD: ffffc700baaeae48 -- (.exr 0xffffc700baaeae48)
ExceptionAddress: fffff800fbf25780 (nt!MiDemoteCombinedPte+0x0000000000000040)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffc700baaea690 -- (.cxr 0xffffc700baaea690)
rax=ffffff7fbfdfe000 rbx=000000000000006f rcx=ffffdf85feade940
rdx=ffffff6217480300 rsi=ffffff6217480300 rdi=ffffff6217480300
rip=fffff800fbf25780 rsp=ffffc700baaeb080 rbp=ffff9b8000000000
r8=8000000000000000 r9=0000000000000000 r10=0000000fffffffff
r11=0000000000000000 r12=ffffff7fbfdfe7f8 r13=ffff9b8000000000
r14=8000000000000000 r15=ffffdf85feade940
iopl=0 nv up ei ng nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287
nt!MiDemoteCombinedPte+0x40:
fffff800`fbf25780 498378f001 cmp qword ptr [r8-10h],1 ds:002b:7fffffff`fffffff0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
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
ffffffffffffffff
FOLLOWUP_IP:
nt!MiDemoteCombinedPte+40
fffff800`fbf25780 498378f001 cmp qword ptr [r8-10h],1
BUGCHECK_STR: AV
EXCEPTION_STR: 0x0
LAST_CONTROL_TRANSFER: from fffff800fc00254c to fffff800fbf25780
STACK_TEXT:
ffffc700`baaeb080 fffff800`fc00254c : fffffb27`e92e4e2a ffffc700`baaeb670 00000000`00000000 00000000`00000002 : nt!MiDemoteCombinedPte+0x40
ffffc700`baaeb150 fffff800`fbefd259 : ffffc700`baaeb239 00000000`0000006f ffffc700`baaeb239 00000000`00000000 : nt!MiResetAccessBitPte+0x37c
ffffc700`baaeb1c0 fffff800`fbefd662 : ffffc700`baaeb670 ffffff62`17480300 ffffc700`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x299
ffffc700`baaeb2a0 fffff800`fbefd662 : ffffc700`baaeb670 ffffff7f`b10ba400 ffffc700`00000001 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
ffffc700`baaeb380 fffff800`fbefd662 : ffffc700`baaeb670 ffffff7f`bfd885d0 ffffc700`00000002 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
ffffc700`baaeb460 fffff800`fbefb367 : ffffc700`baaeb670 ffffff7f`bfdfec40 00000000`00000003 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
ffffc700`baaeb540 fffff800`fc007eeb : ffffc700`baaeb670 00000000`00000001 fffff800`00000001 ffffc700`00000000 : nt!MiWalkPageTables+0x1e7
ffffc700`baaeb630 fffff800`fbef9255 : ffffc881`ab5d9bc0 ffffdf86`0b869640 ffffdf85`feade940 ffffdf86`0b869640 : nt!MiCaptureAndResetWorkingSetAccessBits+0xe3
ffffc700`baaeb920 fffff800`fbef8183 : fffff800`fc26df80 ffffc700`baaebbc0 ffffdf85`fea90010 fffff800`00000000 : nt!MiTrimOrAgeWorkingSet+0x6f5
ffffc700`baaeb9f0 fffff800`fbf881ff : fffff800`fc26df80 fffff800`fc26df80 00000000`00000144 00000000`00000000 : nt!MiProcessWorkingSets+0x233
ffffc700`baaebba0 fffff800`fc015527 : 00000000`00000004 00000000`00000004 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0x9f
ffffc700`baaebc60 fffff800`fbf98e37 : ffffdf85`feb6d040 00000000`00000080 fffff800`fc0153d0 00000004`ad1b3ffe : nt!KeBalanceSetManager+0x157
ffffc700`baaebd50 fffff800`fc04f116 : ffffc881`a8fa8180 ffffdf85`feb6d040 fffff800`fbf98df0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffc700`baaebda0 00000000`00000000 : ffffc700`baaec000 ffffc700`baae6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiDemoteCombinedPte+40
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5b63c7b5
STACK_COMMAND: .cxr 0xffffc700baaea690 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_AV_nt!MiDemoteCombinedPte+40
BUCKET_ID: X64_AV_nt!MiDemoteCombinedPte+40
Followup: MachineOwner
Continue reading...
two days ago I updated my DELL XPS 435T/9000 from 1709 to 1803.
Everything when fine but suspension behaviour.
I used it a lot in previous versions.
Now, my pc goes to sleep correctly but cannot restart.
When I restart it, CPU wake up (I hear fans running) , the screen remains black (it doesn't become blue), and after 5-10 secs it powers off and leaves a minidump (see below).
I suspected some driver (wifi, video) and made all possibile test I could imagine (update, degrades, removed drivers): no results.
Hidernations works perfectly.
Current BIOS is AMI A16, quite old (2010), but I got no problem when 1709 was running.
I changed ACPI from S3 to the only other alternative: S1. With S1, wakeup after suspension doesn't power off with minidump. The PC wakes up and stay powered, but the screen remains black.
I have no other idea but to forget suspension and use hinernation for the future, but I have bad feelings when my "work" PC has some problem.
How can I understand which driver could cause the problem?
Could 1803 version raise problem with a BIOS working with 1709?
Any idea will be appreciated.
Thank you in advance
Mauro
--------------------------
This is the minidump analisys:
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 8 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff800`fbe9f000 PsLoadedModuleList = 0xfffff800`fc24d170
Debug session time: Sun Aug 26 06:35:22.562 2018 (UTC - 4:00)
System Uptime: 0 days 0:04:31.351
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800fbf25780, The address that the exception occurred at
Arg3: ffffc700baaeae48, Exception Record Address
Arg4: ffffc700baaea690, Context Record Address
Debugging Details:
------------------
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".
FAULTING_IP:
nt!MiDemoteCombinedPte+40
fffff800`fbf25780 498378f001 cmp qword ptr [r8-10h],1
EXCEPTION_RECORD: ffffc700baaeae48 -- (.exr 0xffffc700baaeae48)
ExceptionAddress: fffff800fbf25780 (nt!MiDemoteCombinedPte+0x0000000000000040)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffc700baaea690 -- (.cxr 0xffffc700baaea690)
rax=ffffff7fbfdfe000 rbx=000000000000006f rcx=ffffdf85feade940
rdx=ffffff6217480300 rsi=ffffff6217480300 rdi=ffffff6217480300
rip=fffff800fbf25780 rsp=ffffc700baaeb080 rbp=ffff9b8000000000
r8=8000000000000000 r9=0000000000000000 r10=0000000fffffffff
r11=0000000000000000 r12=ffffff7fbfdfe7f8 r13=ffff9b8000000000
r14=8000000000000000 r15=ffffdf85feade940
iopl=0 nv up ei ng nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287
nt!MiDemoteCombinedPte+0x40:
fffff800`fbf25780 498378f001 cmp qword ptr [r8-10h],1 ds:002b:7fffffff`fffffff0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
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
ffffffffffffffff
FOLLOWUP_IP:
nt!MiDemoteCombinedPte+40
fffff800`fbf25780 498378f001 cmp qword ptr [r8-10h],1
BUGCHECK_STR: AV
EXCEPTION_STR: 0x0
LAST_CONTROL_TRANSFER: from fffff800fc00254c to fffff800fbf25780
STACK_TEXT:
ffffc700`baaeb080 fffff800`fc00254c : fffffb27`e92e4e2a ffffc700`baaeb670 00000000`00000000 00000000`00000002 : nt!MiDemoteCombinedPte+0x40
ffffc700`baaeb150 fffff800`fbefd259 : ffffc700`baaeb239 00000000`0000006f ffffc700`baaeb239 00000000`00000000 : nt!MiResetAccessBitPte+0x37c
ffffc700`baaeb1c0 fffff800`fbefd662 : ffffc700`baaeb670 ffffff62`17480300 ffffc700`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x299
ffffc700`baaeb2a0 fffff800`fbefd662 : ffffc700`baaeb670 ffffff7f`b10ba400 ffffc700`00000001 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
ffffc700`baaeb380 fffff800`fbefd662 : ffffc700`baaeb670 ffffff7f`bfd885d0 ffffc700`00000002 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
ffffc700`baaeb460 fffff800`fbefb367 : ffffc700`baaeb670 ffffff7f`bfdfec40 00000000`00000003 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
ffffc700`baaeb540 fffff800`fc007eeb : ffffc700`baaeb670 00000000`00000001 fffff800`00000001 ffffc700`00000000 : nt!MiWalkPageTables+0x1e7
ffffc700`baaeb630 fffff800`fbef9255 : ffffc881`ab5d9bc0 ffffdf86`0b869640 ffffdf85`feade940 ffffdf86`0b869640 : nt!MiCaptureAndResetWorkingSetAccessBits+0xe3
ffffc700`baaeb920 fffff800`fbef8183 : fffff800`fc26df80 ffffc700`baaebbc0 ffffdf85`fea90010 fffff800`00000000 : nt!MiTrimOrAgeWorkingSet+0x6f5
ffffc700`baaeb9f0 fffff800`fbf881ff : fffff800`fc26df80 fffff800`fc26df80 00000000`00000144 00000000`00000000 : nt!MiProcessWorkingSets+0x233
ffffc700`baaebba0 fffff800`fc015527 : 00000000`00000004 00000000`00000004 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0x9f
ffffc700`baaebc60 fffff800`fbf98e37 : ffffdf85`feb6d040 00000000`00000080 fffff800`fc0153d0 00000004`ad1b3ffe : nt!KeBalanceSetManager+0x157
ffffc700`baaebd50 fffff800`fc04f116 : ffffc881`a8fa8180 ffffdf85`feb6d040 fffff800`fbf98df0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffc700`baaebda0 00000000`00000000 : ffffc700`baaec000 ffffc700`baae6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiDemoteCombinedPte+40
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5b63c7b5
STACK_COMMAND: .cxr 0xffffc700baaea690 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_AV_nt!MiDemoteCombinedPte+40
BUCKET_ID: X64_AV_nt!MiDemoteCombinedPte+40
Followup: MachineOwner
Continue reading...