BSOD when waking from sleep

Files dont exist. The ntfs stop error, if its 0x24, can mean a failing hdd. Or the files on it are corrupt

Run tdsskiller on it, see if it picks up any rootkits

http://media.kaspersky.com/utilities/VirusUtilities/EN/tdsskiller.exe

Cool

Looks like hiber_iaStorA.sys is crashing with win32k.sys and ntoskrnl.exe.

See if there are any updates for your SATA drivers. Or Intel rapid storage drivers

Theyre crashing the system

Theres a few screwed up files on the hdd with no names

個櫵㯆벪��鞽⩬ᐌ쯰␖䳲紩ጪꔎὖᥝ냚뭵�Ꙓ濍଎≋摮벎쥣➩뭎䠉�〈 is one of them

and 羌㺈ﾌ羌罠륑爫쁛颽ᓿ틋噃袴柏ꩡ཈嵜咿ꌂ�攳⠵ꠅꠥꠅ畎큧苓ꮽ咮轰銯䱸䁅

And Unknown_Module_fffff800`b6fbf000

Theres like 35-40 unknown files, some like the above like Chinese characters

If I were you I would replace the hdd

update the BIOS, I saw the memory corruption in the debug image. The corruption is most likely only in the memory image not in the actual files on the hard drive. The bug should be in the BIOS, or maybe the cpu chipset drivers (for the sata controller) If the actual files on the hard drive were corrupted, you would be getting a bugcheck on a cold boot rather than on resume from a low power state.

Sorry, this is not much help but your system is much better with the BIOS update. The fact that asus turned off sleep on the SATA ports may indicate they have some problems in their electronics circuits.
-----------

overall, I would make sure I have all the windows 8.1 updates installed and all the ASUS 8.1 drivers installed. and I would remove the AiCHarger.sys (just because of bugs on other systems I have seen. It may be fine on your system)

if you can please change your memory dump from a minidump to kernel memory dump.
and use verifier.exe to turn on debugging info.

http://www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html



remove this driver
AiCharger.sys Thu Sep 22 19:04:40 2011

- second bugcheck looks like a program was trying to unblank the display and sent bad values and cause a crash. you have a custom asus driver
C:\Program Files\ASUS\P4G\plctrl.sys Wed Jul 10 20:23:44 2013
I would look for a update.

well, the BIOS update turned off sleep mode for your SATA ports and now the memory image is not corrupted on disk. So that is very good progress. I am looking at your bugcheck 24NTFS_FILE_SYSTEM (24)
and it looks like a metro subsystem problem trying at access the filesystem with bad addresses.

I will look at the other bugcheck.

new bugcheck 24 indicates AiCharger.sys
\SystemRoot\system32\DRIVERS\AiCharger.sys Thu Sep 22 19:04:40 2011

as the problem.
pick up the 2014 update from the asus site, install reboot and see if your problem goes away.
-------------
you might consider removing Asus instant on program running on your computer
InsOnWMI.exe it does some custom hybrid type of sleep function. It could have bugs
-------------
make sure armsvc.exe is you adobe update service and not a trojan
run malwarebytes scan





--------------------
downloading the new memory dump now.
I looked at the asus site for your system, there is a new aicharger.sys in the utilities section
dated this year. The older version tended to corrupt driver memory. You should remove it or update the driver. Take a list of the utilities and remove any that you don't use or update any that have a update. if you have the power4gear running you should update the drivers or remove it to see if it is the root cause of your problem.

I would uninstall not update Aicharger. It is a known cause of crashes

from what I can tell your system is lacking all of the custom Asus driver updates for your system dated after 8/22/2013
go down the list and install them and reboot
http://www.asus.com/Notebooks_Ultrabooks/ASUS_ZENBOOK_UX302LG/HelpDesk_Download/
I think one of the old asus drivers is stomping on some of windows kernel memory structure.
It is more likely a direct root cause of your various failures.
most likely because of the type of failure, it will not be your actual hard drive. (the input output from the drive did not fail, the data stored in memory was corrupted, easy to do with a bad driver)



BugCheck 7A, {1, ffffffffc0000005, ffffe0013530b900, fffff6fac000c000}
KERNEL_DATA_INPAGE_ERROR (7a)

the current process was sdiagnhost.exe (it think it is Microsoft scripted host diagnostics)
basically the system keeps a map of how it maps your physical RAM to your pagefile.sys
and the map was corrupted so the virtual address it got from the table was invalid and the system called a bugcheck.

the system tried to page from address fffff6fac000c000 but could not because it is a invalid pagetable entry



for a error like this you would confirm memtest86 works on its own boot disk.
if it does run without failures then you have to:
run verifier.exe and set global debugging flags
see http://www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html
then set your memory dump from a mini dump to a kernel or full memory dump
reboot and wait for the next bugcheck
with a mini dump the proper debugging info is just not saved to figure out the cause of the bad page table entry.

verifier.exe may catch a process that is corrupting the page table entry (if it is a driver corruption), or it can be faulty hardware

-------------
looking at your driver list you might remove this file
C:\Program Files (x86)\ASUS\ATK Package\ATKGFNEX\ASMMAP64.sys Thu Jul 02 02:13:26 2009
it is a asus hot key driver. it is very old. the rest of your drivers have a reasonable file date.

you have the driver
\SystemRoot\system32\drivers\AmPeStor.sys Mon Oct 07 02:18:33 2013
Alocr Micro PCIE Card Reader Driver. there is a update to the driver on the asus website
this driver is not in widespread use. install the 2014 update under card readers
http://www.asus.com/Notebooks_Ultrabooks/ASUS_ZENBOOK_UX302LG/HelpDesk_Download/

also update your asustp.sys (asus touchpad driver) lots of bugchecks caused by the version you are running
\SystemRoot\System32\drivers\AsusTP.sys Tue Sep 17 02:28:40 2013
get the version dated 4/24/2014 on the asus website.

Look through the list of updates on the asus website. your system files are mostly from 2013 but asus has more current driver fixes. Any of these older drivers could corrupt memory of the other drivers and cause your failures.

basically it looks like you need all of the asus updates dated after 8/22/2013