Hi good day,

I currently own an ASUS Zenbook USX32V with Win 8 preinstalled, I bought this PC around one and a half years ago. 

Last year I updated it to Win 8.1 and after that, I've been having the same BSOD with error: Kernel_Data_Inpage_Error and need to restart my computer. It happens everytime I wake it up from sleep or hibernation.

I've read some of the articles in this forum as well as other ones and I've read that it is advised to run a CHKDSK in command prompt as well as a SFC. I've performed both of them and I've got the following message for SFC:

"Windows Resource Protection found currupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios."

When I tried to perform the CHKDSK and restarted my computer, it got stuck at "Scanning and Repairing (C:) 27% completed."

I had to skip the scan and after that, my computer started properly, nevertheless the BSOD still appears as the scanning and repairing process did not completed successfully.

I've also tried to refresh/restore/reset my computer back to a previous point or to the OEM settings with no success due to the error "Restore drive could not be found."

Could you guys please help me with this issue? I would like to format my computer back to it's manufacturing settings but I cannot do it either.

Thanks in advance for any help provided.

Regards,
Alan Francke

If you are having that message come up after using the sfc /scannow then try this:

1- Run CMD as administrator

2- type DISM /online /Cleanup-Image /RestoreHealth

NOTE: You need to be connected to the internet for this

3 - If you have a Windows installation media then type this:

DISM /online /Cleanup-Image /RestoreHealth /source:wim:D\sources\install.wim:1 /limitaccess

Replace D: with whatever drive your installation media is on.

 We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here If you have any questions about the procedure please ask

In order to diagnose your problem we need to run Windows performance toolkit the instructions for which can be found in this wiki If you have any questions feel free to ask
Please run the trace when you are experiencing the problem

Ok, so I've managed to make my way through the compression issue and I've got the compressed files ready and uploaded, here's the link:

https://onedrive.live.com/redir?resid=4BC00AB8D5462AD!644&authkey=!AHJmytrlEHnOApI&ithint=file%2czip

I've also added the System Information file in the Zip.

Hope you guys can help me with the issue.

Let me know the updates!

Regards,
Alan Francke

Alan

Two possibilities.  First there is a HD controller error which may or may not be important.  I would run CHKDSK and go to the HD maker and download and run their HD checking utility.  CHKDSK checks the file system, their utility checks the actual HD

Second this may also be an OS issue so I would run a system file check and if that comes back ok, I would run verifier to find the underling issue

1-CHKDSK

CHKDSK /R 
Chkdsk disclaimer: While performing chkdsk on the hard drive if any bad sectors are found  any data available on that sector might be lost so as usual backup your data.
Run CHKDSK /R  from an elevated (Run as administrator) Command Prompt.
Do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.
It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.
http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/


 See "CHKDSK LogFile" below in order to check the results of the test.

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post. 

2-SFC

Please run a system file check (SFC)
All instructions are in our Wiki article below...
Should you have any questions please ask us.

System file check (SFC) Scan and Repair System Files

3-verifier

These crashes were related to memory corruption (probably caused by a driver). 

Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless you want to.

   If you are over-clockinganything reset to default before running these tests.
In other words STOP!!!

If you do not know what this means you probably are not

 
1-Driver verifier (for complete directions see our wikihere)  
2-Memtest. (You can read more about running memtesthere)

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Ken\Desktop\New folder\021615-29625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is: 
SRV*e:\symbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
Machine Name:
Kernel base = 0xfffff802`84a05000 PsLoadedModuleList = 0xfffff802`84cde250
Debug session time: Mon Feb 16 09:47:38.968 2015 (UTC - 5:00)
System Uptime: 0 days 12:23:07.844
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {4, 0, ffffe000afa20550, e01d8a2478}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+154fb )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000004, lock type that was held (value 1,2,3, or PTE address)
Arg2: 0000000000000000, error status (normally i/o status code)
Arg3: ffffe000afa20550, current process (virtual address for lock type 3, or PTE)
Arg4: 000000e01d8a2478, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0 - STATUS_SUCCESS

BUGCHECK_STR:  0x7a_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80284b7b3ab to fffff80284b559a0

STACK_TEXT:  
ffffd000`22d76788 fffff802`84b7b3ab : 00000000`0000007a 00000000`00000004 00000000`00000000 ffffe000`afa20550 : nt!KeBugCheckEx
ffffd000`22d76790 fffff802`84a367f8 : 00000000`00000002 ffffd000`22d768f8 ffffe000`af00edd8 ffffd000`00000000 : nt! ?? ::FNODOBFM::`string'+0x154fb
ffffd000`22d76880 fffff802`84a6fb7a : ffffe000`af00edd8 ffffe000`af064080 00000000`00000001 ffffe000`0000000d : nt!MiIssueHardFault+0x184
ffffd000`22d76940 fffff802`84b5fc2f : 00000000`00000001 000000e0`1cfadb00 000000e0`00000001 ffffe000`af258a20 : nt!MmAccessFault+0x5ba
ffffd000`22d76b00 00007ffd`518e29ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f
000000e0`1ca9ded0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`518e29ac


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+154fb
fffff802`84b7b3ab cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+154fb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  54b0c2f7

IMAGE_VERSION:  6.3.9600.17630

BUCKET_ID_FUNC_OFFSET:  154fb

FAILURE_BUCKET_ID:  0x7a_0_nt!_??_::FNODOBFM::_string_

BUCKET_ID:  0x7a_0_nt!_??_::FNODOBFM::_string_

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7a_0_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH:  {87ed9903-76d8-bd16-10fb-61b59edbe1ad}

Followup: MachineOwner
---------