The long and short of it is this error involves either a buggy driver, or more likely given this is a "gaming" laptop, defective hardware.
I'd start by upgrading all the drivers for your system and if you still get the problem you're going to need to send it in for repair. In the latter case, do yourself a favor and create a free Gmail account or something with a Chinese sounding last name. You will be much more likely to get better service from ASUS that way.
Knew someone who worked there and somehow despite being located in one of the most racially and ethnically diverse areas of the US, their workforce is like 95% Asian... And not just Asian, your sort of stereotypical East Asian. This person I know, who's white, was regularly harassed by Asian coworkers and when they complained about the harassment, ASUS retaliated against them. So there's a clear bias in that company -- at least that's my interpretation of the evidence, and I've yet to come across anyone who can offer up an explanation for the employee demographics that doesn't involve institutional racism -- towards persons of Asian descent. Meaning if you want to get better service, adopt a nom de plume that is Chinese. If you have an easily identifiable Anglo-Saxon or Hispanic name, and you use that instead of a fake name, expect to have to fight a steep uphill battle.
At seemingly random times while using my new laptop, an ASUS G56JK, I get a BSOD and my computer restarts. This problem is really annoying and makes my computer a hassle to use. If anyone knows how to fix this, I'd love some help.
This is what I got from the DMP:
<div> Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`71a8d000 PsLoadedModuleList = 0xfffff802`71d572d0
Debug session time: Sun Aug 31 23:40:15.812 2014 (UTC - 4:00)
System Uptime: 1 days 11:46:01.891
*******************************************************************************
* *
* 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: ffffe000b57e43f0, Physical Device Object of the stack
Arg3: ffffd00048538930, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffe000b88fc010, The blocked IRP
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: ffffe000b5734060
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53089439
MODULE_NAME: pci
FAULTING_MODULE: fffff801adf15000 pci
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
ffffd000`485388f8 fffff802`71c89c1e : 00000000`0000009f 00000000`00000003 ffffe000`b57e43f0 ffffd000`48538930 : nt!KeBugCheckEx
ffffd000`48538900 fffff802`71c89b3e : ffffe000`b92def08 00000000`ffffffff ffffe000`b92def48 fffff802`71aea240 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`48538960 fffff802`71ae6810 : 00000000`00000000 ffffd000`48538ab0 ffffe000`b92def40 ffffd000`00000002 : nt!PopIrpWatchdog+0x32
ffffd000`485389b0 fffff802`71be4aea : ffffd000`4850e180 ffffd000`4850e180 ffffd000`4851a3c0 ffffe000`ba569700 : nt!KiRetireDpcList+0x4f0
ffffd000`48538c60 00000000`00000000 : ffffd000`48539000 ffffd000`48533000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_pci.sys
BUCKET_ID: X64_0x9F_3_IMAGE_pci.sys
Followup: MachineOwner
</div>
Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic