0

This seems to be happening in and around 3ds max but i dont feel like the problem is local to that program. I have looked through internet surgestions to solve the crash, all the drivers on the machine are uptodate in device manager. I also ran a memtest from a usb boot that indicated no cpu or ram errors. many thanks for your consideration and perhaps help.

Windows 8 Kernel Version 17763 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 17763.1.amd64fre.rs5_release.180914-1434 Machine Name: Kernel base = 0xfffff8015b49f000 PsLoadedModuleList = 0xfffff8015b8baad0 Debug session time: Fri Feb 22 10:01:55.226 2019 (UTC - 5:00) System Uptime: 0 days 0:35:29.190


  • *
  • 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: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: ffffb105a6e65570, Physical Device Object of the stack Arg3: ffffc180fb4bf7d0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack Arg4: ffffb105b0835050, The blocked IRP

Debugging Details:

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 27f44328

MODULE_NAME: pci

FAULTING_MODULE: fffff80fcf5b0000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
ffffc180fb4bf798 fffff8015b770e06 : 000000000000009f 0000000000000003 ffffb105a6e65570 ffffc180fb4bf7d0 : nt!KeBugCheckEx ffffc180fb4bf7a0 fffff8015b770d12 : ffffb105afa3e608 ffffc180fb4bf910 000000000000005e ffff86812917c180 : nt!PopIrpWatchdogBugcheck+0xea ffffc180fb4bf810 fffff8015b556659 : ffffb105afa3e640 00000000000000ff ffffc180fb4bfa18 0000000000000008 : nt!PopIrpWatchdog+0x22 ffffc180fb4bf860 fffff8015b5575a7 : 0000000000000012 0000000000989680 ffff86812918c300 0000000000000019 : nt!KiProcessExpiredTimerList+0x159 ffffc180fb4bf950 fffff8015b655e5a : 0000000000000000 ffff86812917c180 0000000000000000 ffff86812918c300 : nt!KiRetireDpcList+0x4a7 ffffc180fb4bfb60 0000000000000000 : ffffc180fb4c0000 ffffc180fb4b9000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_nvlddmkm_IMAGE_pci.sys

BUCKET_ID: OLD_IMAGE_pci.sys

Followup: MachineOwner

Crash 2 feb 22 18:44pm


  • *
  • Bugcheck Analysis *
  • *

DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. The offending component can usually be identified with a stack trace. Arg2: 0000000000001e00, The watchdog period. Arg3: fffff8002b7ef380 Arg4: 0000000000000000

Debugging Details:

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

BAD_PAGES_DETECTED: 11d90

LAST_CONTROL_TRANSFER: from fffff8002b5031d5 to fffff8002b460440

STACK_TEXT:
fffff8002e3f5ba8 fffff8002b5031d5 : 0000000000000133 0000000000000001 0000000000001e00 fffff8002b7ef380 : nt!KeBugCheckEx fffff8002e3f5bb0 fffff8002b3d0daf : 000005ecca5729d6 fffff8002a052180 0000000000000286 000000000002dd33 : nt!KeAccumulateTicks+0x12edb5 fffff8002e3f5c10 fffff8002b21747c : 0000000000000000 fffff8002b27d6e0 fffff8002e3e5cd0 fffff8002b27d790 : nt!KeClockInterruptNotify+0xcf fffff8002e3f5f30 fffff8002b2ef8b5 : fffff8002b27d6e0 0000000000000010 ffffbcbfb5630c46 ffffbcbfb5630db6 : hal!HalpTimerClockIpiRoutine+0x1c fffff8002e3f5f60 fffff8002b461e3a : fffff8002e3e5cd0 fffff8002b27d6e0 ffffdf021d411000 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5 fffff8002e3f5fb0 fffff8002b462387 : ffffdf021d411ff8 fffff80044d7a0dc ffffdf021d411000 fffff8002e3e62b8 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff8002e3e5c50 fffff80044d59ce1 : fffff80044d7d388 ffffdf021d411000 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff8002e3e5de8 fffff80044d7d388 : ffffdf021d411000 0000000000000000 0000000000000000 0000000000000001 : nvlddmkm+0x1e9ce1 fffff8002e3e5df0 ffffdf021d411000 : 0000000000000000 0000000000000000 0000000000000001 fffff80000000020 : nvlddmkm+0x20d388 fffff8002e3e5df8 0000000000000000 : 0000000000000000 0000000000000001 fffff80000000020 fffff8002e3e5e30 : 0xffffdf02`1d411000

STACK_COMMAND: 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 73104 instance(s) of page corruption, target is likely to have memory corruption.

Crash 3

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 8 Kernel Version 17763 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 17763.1.amd64fre.rs5_release.180914-1434 Machine Name: Kernel base = 0xfffff8043a2b3000 PsLoadedModuleList = 0xfffff8043a6cead0 Debug session time: Thu Feb 21 12:48:08.894 2019 (UTC - 5:00) System Uptime: 0 days 4:53:44.859


  • *
  • Bugcheck Analysis *
  • *

DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. The offending component can usually be identified with a stack trace. Arg2: 0000000000001e00, The watchdog period. Arg3: fffff8043a7f5380 Arg4: 0000000000000000

Debugging Details:

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

LAST_CONTROL_TRANSFER: from fffff8043a5091d5 to fffff8043a466440

STACK_TEXT:
fffff8043d3f5ba8 fffff8043a5091d5 : 0000000000000133 0000000000000001 0000000000001e00 fffff8043a7f5380 : nt!KeBugCheckEx fffff8043d3f5bb0 fffff8043a3d6daf : 0000236bdcbee54e fffff80438f6a180 0000000000000286 0000000000113637 : nt!KeAccumulateTicks+0x12edb5 fffff8043d3f5c10 fffff8043a21d47c : 0000000000000000 fffff8043a2836e0 fffff8043d3e5cd0 fffff8043a283790 : nt!KeClockInterruptNotify+0xcf fffff8043d3f5f30 fffff8043a2f58b5 : fffff8043a2836e0 0000000000000010 ffffee694ed0a623 ffffee694ed0a7d3 : hal!HalpTimerClockIpiRoutine+0x1c fffff8043d3f5f60 fffff8043a467e3a : fffff8043d3e5cd0 fffff8043a2836e0 ffff9e8c19388000 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5 fffff8043d3f5fb0 fffff8043a468387 : ffff9e8c19388ff8 fffff80455c29944 ffff9e8c19388000 fffff8043d3e62b8 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff8043d3e5c50 fffff80455c095a1 : fffff80455c2cbe8 ffff9e8c19388000 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff8043d3e5de8 fffff80455c2cbe8 : ffff9e8c19388000 0000000000000000 0000000000000000 0000000000000001 : nvlddmkm+0x1e95a1 fffff8043d3e5df0 ffff9e8c19388000 : 0000000000000000 0000000000000000 0000000000000001 fffff80400000020 : nvlddmkm+0x20cbe8 fffff8043d3e5df8 0000000000000000 : 0000000000000000 0000000000000001 fffff80400000020 fffff8043d3e5e30 : 0xffff9e8c`19388000

STACK_COMMAND: kb

FOLLOWUP_IP: nvlddmkm+1e95a1 fffff804`55c095a1 c3 ret

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: nvlddmkm+1e95a1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5c52037f

FAILURE_BUCKET_ID: X64_0x133_nvlddmkm+1e95a1

BUCKET_ID: X64_0x133_nvlddmkm+1e95a1

Followup: MachineOwner

next crash

rash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 8 Kernel Version 17763 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff8037201f000 PsLoadedModuleList = 0xfffff8037243aad0 Debug session time: Sat Mar 2 08:28:56.718 2019 (UTC - 5:00) System Uptime: 0 days 0:23:27.681


  • *
  • 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: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: ffffc08eadfb5570, Physical Device Object of the stack Arg3: fffff00f560bf7d0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack Arg4: ffffc08eb4fb08e0, The blocked IRP

Debugging Details:

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 27f44328

MODULE_NAME: pci

FAULTING_MODULE: fffff8006e470000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

BAD_PAGES_DETECTED: 116b7

STACK_TEXT:
fffff00f560bf798 fffff803722f0e06 : 000000000000009f 0000000000000003 ffffc08eadfb5570 fffff00f560bf7d0 : nt!KeBugCheckEx fffff00f560bf7a0 fffff803722f0d12 : ffffc08eb6a82608 fffff00f560bf910 00000000000000da ffffe00084d7c180 : nt!PopIrpWatchdogBugcheck+0xea fffff00f560bf810 fffff803720d6659 : ffffc08eb6a82640 00000000000000ff fffff00f560bfa18 0000000000000008 : nt!PopIrpWatchdog+0x22 fffff00f560bf860 fffff803720d75a7 : 0000000000000006 0000000000989680 ffffe00084d8c300 0000000000000019 : nt!KiProcessExpiredTimerList+0x159 fffff00f560bf950 fffff803721d5e5a : ffffffff00000000 ffffe00084d7c180 0000000000000000 ffffe00084d8c300 : nt!KiRetireDpcList+0x4a7 fffff00f560bfb60 0000000000000000 : fffff00f560c0000 fffff00f560b9000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_nvlddmkm_IMAGE_pci.sys

BUCKET_ID: OLD_IMAGE_pci.sys

Followup: MachineOwner

*** Memory manager detected 71351 instance(s) of page corruption, target is likely to have memory corruption.

  • 1
    It does look like the issue is revolving around the video card. Being it’s a laptop, it is probably shared video memory (shares with the system RAM). This type of problem is difficult to troubleshoot. But extensive testing and logical process of elimination can do it. It could be the OS, RAM, Motherboard, heat, etc. I know that is vague, but this is not the type of thing that can really be explained. It’s more of a learned skill. Intermittent problems have to be approached very logically making sure each “change” is thoroughly tested as either a “success” or “failure.” – Appleoddity Mar 2 at 15:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.