New
#1
Minidump Bugcheck Analysis
I just had two crashes in the last 2 days. I found the minidump file and it says this ...
Code:Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Unique Expertise, Guaranteed Results) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 8 Kernel Version 16299 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff803`3928b000 PsLoadedModuleList = 0xfffff803`395f2110 Debug session time: Tue Feb 20 23:45:54.733 2018 (UTC - 5:00) System Uptime: 1 days 9:44:26.466 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time (usually 10 minutes). Arguments: Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem. Arg2: 000000000000012c, Timeout in seconds. Arg3: ffffe504ed748040, The thread currently holding on to the Pnp lock. Arg4: fffff8033b85d910, nt!TRIAGE_9F_PNP on Win7 Debugging Details: ------------------ Implicit thread is now ffffe504`ed748040 TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 DRVPOWERSTATE_SUBCODE: 4 FAULTING_THREAD: ffffe504ed748040 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 BAD_PAGES_DETECTED: 1105e LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80339403d1a STACK_TEXT: fffff803`3b85dc60 00000000`00000000 : fffff803`3b85e000 fffff803`3b858000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: .thread 0xffffe504ed748040 ; kb SYMBOL_NAME: PAGE_NOT_ZERO FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: PAGE_NOT_ZERO Followup: MachineOwner --------- *** Memory manager detected 69726 instance(s) of page corruption, target is likely to have memory corruption.
Any idea what is going on and what I can do to fix it?
Last edited by Brink; 22 Feb 2018 at 20:30. Reason: code box