Hello,
I've just experienced three BSODs (two different types) on my new Asus UX32VD bought a couple of months back.
Here's the first minidump file:
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 9600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505 Machine Name: Kernel base = 0xfffff800`84087000 PsLoadedModuleList = 0xfffff800`8434b990 Debug session time: Wed Mar 12 11:54:14.172 2014 (UTC - 4:00) System Uptime: 2 days 2:27:09.047 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) 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. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80000c010f0, The address that the exception occurred at Arg3: ffffd000219462e8, Parameter 0 of the exception Arg4: ffffd00021945af0, Parameter 1 of the exception 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: NETIO!WfpNblInfoGet+0 fffff800`00c010f0 488b81e0000000 mov rax,qword ptr [rcx+0E0h] EXCEPTION_PARAMETER1: ffffd000219462e8 EXCEPTION_PARAMETER2: ffffd00021945af0 WRITE_ADDRESS: fffff80084339340: Unable to get special pool info fffff80084339340: Unable to get special pool info GetUlongFromAddress: unable to read from fffff800843d4208 ffffd00021945af0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". BUGCHECK_STR: 0x1e_c0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 EXCEPTION_RECORD: 0000000000000001 -- (.exr 0x1) Cannot read Exception record @ 0000000000000001 TRAP_FRAME: ffffe000001508a0 -- (.trap 0xffffe000001508a0) Unable to read trap frame at ffffe000`001508a0 LAST_CONTROL_TRANSFER: from fffff8008425aebf to fffff800841d4ca0 CONTEXT: 90909090c3fce083 -- (.cxr 0x90909090c3fce083) Unable to read context, Win32 error 0n30 STACK_TEXT: ffffd000`21945288 fffff800`8425aebf : 00000000`0000001e ffffffff`c0000005 fffff800`00c010f0 ffffd000`219462e8 : nt!KeBugCheckEx ffffd000`21945290 fffff800`841e5c66 : ffffe000`0506e880 00000000`0000000e ffffb000`0b4c0000 fffff800`840f1b45 : nt!KiFatalFilter+0x1f ffffd000`219452d0 fffff800`841c3da6 : 00000000`00000000 ffffc000`009f30b8 00000000`00001000 00000000`00001000 : nt! ?? ::FNODOBFM::`string'+0xac6 ffffd000`21945320 fffff800`841dc1ed : 00000000`00000000 ffffd000`219454c0 ffffd000`219462e8 fffff800`00d5a628 : nt!_C_specific_handler+0x86 ffffd000`21945390 fffff800`84162595 : 00000000`00000003 ffffd000`219454c0 fffff800`00f416c0 ffffc000`00040000 : nt!RtlpExecuteHandlerForException+0xd ffffd000`219453c0 fffff800`8416345b : ffffd000`219462e8 ffffd000`21945ff0 ffffd000`219462e8 00000000`00000000 : nt!RtlDispatchException+0x455 ffffd000`21945ac0 fffff800`841e08c2 : 00000000`00000001 fffff800`84317900 ffffe000`001508a0 00000000`2a677641 : nt!KiDispatchException+0x61f ffffd000`219461b0 fffff800`841df014 : 00000000`00000000 00000000`00000000 ffffe000`00608c00 ffffd000`21946390 : nt!KiExceptionDispatch+0xc2 ffffd000`21946390 fffff800`00c010f0 : fffff800`01292042 ffffd000`21946548 00000000`00000000 fffffff6`00000002 : nt!KiPageFault+0x214 ffffd000`21946528 fffff800`01292042 : ffffd000`21946548 00000000`00000000 fffffff6`00000002 00000001`ffffffff : NETIO!WfpNblInfoGet ffffd000`21946530 fffff800`012fe586 : 00000000`00000000 00000000`00000000 ffffe000`0024f840 ffffd000`21946b30 : fwpkclnt!FwppNetBufferListEventNotify+0x32 ffffd000`21946600 fffff800`00ec8cc1 : 00000000`00000000 00000000`00000000 ffffe000`0506e880 00000001`ffffffff : wfplwfs!LwfLowerReturnNetBufferLists+0x56 ffffd000`21946650 fffff800`8413f3f9 : fffffff6`00000002 00000001`ffffffff ffffd000`208c0180 ffffe000`001a29f0 : ndis!ndisDataPathExpandStackCallback+0x31 ffffd000`21946690 fffff800`00ec9025 : fffff800`00ec8c90 ffffd000`21946840 00000000`00000000 fffff800`841370d8 : nt!KeExpandKernelStackAndCalloutInternal+0xe9 ffffd000`219467e0 fffff800`00ec907a : 00000000`000004d0 fffff800`841ac7f4 00000000`0010cd3d ffffe000`0c7d7eb0 : ndis!ndisExpandStack+0x19 ffffd000`21946820 fffff800`00ecc535 : 00000000`00000000 ffffe000`0adc0f40 ffffe000`0c7d79f0 00000000`00000000 : ndis!ndisExpandDataPathStack+0x4a ffffd000`21946880 fffff800`00ecc154 : 00000000`00000001 00000000`00000012 00000000`00000000 fffff800`01f1e8b7 : ndis!ndisInvokeNextReceiveCompleteHandler+0xf445 ffffd000`21946910 fffff800`01f213ab : ffffe000`0b764830 ffffe000`0d34d400 ffffe000`c0000001 00000000`00000000 : ndis!NdisFReturnNetBufferLists+0x273 ffffd000`21946990 ffffe000`0b764830 : ffffe000`0d34d400 ffffe000`c0000001 00000000`00000000 00000000`00000000 : avgfwd6a+0x43ab ffffd000`21946998 ffffe000`0d34d400 : ffffe000`c0000001 00000000`00000000 00000000`00000000 ffff5709`46551026 : 0xffffe000`0b764830 ffffd000`219469a0 ffffe000`c0000001 : 00000000`00000000 00000000`00000000 ffff5709`46551026 ffffe000`00632dd0 : 0xffffe000`0d34d400 ffffd000`219469a8 00000000`00000000 : 00000000`00000000 ffff5709`46551026 ffffe000`00632dd0 ffffe000`00730140 : 0xffffe000`c0000001 FOLLOWUP_IP: NETIO!WfpNblInfoGet+0 fffff800`00c010f0 488b81e0000000 mov rax,qword ptr [rcx+0E0h] SYMBOL_STACK_INDEX: 9 SYMBOL_NAME: NETIO!WfpNblInfoGet+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: NETIO IMAGE_NAME: NETIO.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 5215f7e4 STACK_COMMAND: .cxr 0x90909090c3fce083 ; kb FAILURE_BUCKET_ID: X64_0x1e_c0000005_NETIO!WfpNblInfoGet+0 BUCKET_ID: X64_0x1e_c0000005_NETIO!WfpNblInfoGet+0 Followup: MachineOwner ---------
The second one has a .dmp with 0 KB, presumably because the third one which occurred a few days after the second one is of the same nature. Here's the third:
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 9600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505 Machine Name: Kernel base = 0xfffff801`b5a0e000 PsLoadedModuleList = 0xfffff801`b5cd2990 Debug session time: Thu Mar 20 01:07:47.693 2014 (UTC - 4:00) System Uptime: 3 days 15:09:18.569 ******************************************************************************* * * * 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: ffffe0000046cb70, Physical Device Object of the stack Arg3: fffff801b7b08840, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack Arg4: ffffe0000a96cc80, 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: ntkrnlmp DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAULTING_MODULE: fffff80001850000 taphss6 DEVICE_OBJECT: ffffe00005159050 DRIVER_OBJECT: ffffe0000531f670 IRP_ADDRESS: ffffe0000a96cc80 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 STACK_TEXT: fffff801`b7b08808 fffff801`b5c051a6 : 00000000`0000009f 00000000`00000003 ffffe000`0046cb70 fffff801`b7b08840 : nt!KeBugCheckEx fffff801`b7b08810 fffff801`b5c050c6 : ffffe000`09dfa860 00000000`00000008 00000000`00000005 fffff801`b5a6aa04 : nt!PopIrpWatchdogBugcheck+0xde fffff801`b7b08870 fffff801`b5abbf64 : ffffe000`09dfa898 fffff801`b7b08939 ffffe000`09dfa8d8 00000000`00000002 : nt!PopIrpWatchdog+0x32 fffff801`b7b088c0 fffff801`b5abc478 : 00000000`00000001 ffffe000`0eb4c748 fffff801`b5cfc180 fffff801`b5d009e0 : nt!KiProcessExpiredTimerList+0x1d8 fffff801`b7b089a0 fffff801`b5b18478 : fffff801`b5cfc180 00000000`001ac2de 00000000`00b6a1ab 00000000`00b6a1c3 : nt!KiExpireTimerTable+0x218 fffff801`b7b08a40 fffff801`b5a68abc : ffffe000`00000000 00001f80`00000001 000002da`86ae5220 00000000`00000002 : nt!KiTimerExpiration+0x148 fffff801`b7b08af0 fffff801`b5b5f7ea : fffff801`b5cfc180 fffff801`b5cfc180 00000000`001a3fc0 fffff801`b5d54a80 : nt!KiRetireDpcList+0x19c fffff801`b7b08c60 00000000`00000000 : fffff801`b7b09000 fffff801`b7b03000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: ntkrnlmp FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp Followup: MachineOwner ---------
So what are the problems and how do I go about fixing them?
I'm not very experienced with troubleshooting and all that. So simple instructions to solve these problems would be really great and appreciated.