BSOD, lots of hanging and freezing - Windows 8 x64

[dwolfe]

OS - Windows 8 OEM
· x64
· Windows 8 originally came pre-installed, I attempted Windows 8 repair which failed, then did a Restore (from internal pre-install files) around the end of july

In December this laptop was 1 year old

It is an Acer Aspire S3 model# MS2346

I will work on instructions in #6, thank you!

 

[Jared]

This is interesting.

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:
[COLOR="#FF0000"]Arg1: 0000000000000004, lock type that was held (value 1,2,3, or PTE address)[/COLOR]
[COLOR="#800080"]Arg2: 0000000000000000, error status (normally i/o status code)[/COLOR]
Arg3: fffffa8004be20e0, current process (virtual address for lock type 3, or PTE)
Arg4: 000000000f66752c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

We have a Kernel inpage error meaning the requested kernel data couldn't be read into memory, this is usually caused by failing drives or bad disk controllers.
However, this seems to be a software issue (which is rare) as there was a lock that was being held and there was no error status.
A Kernel memory dump would be much more useful in finding the cause.

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:

C:\Windows\memory.dmp

Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.

 

[dwolfe]

I have not worked in an IT dept for over 10 years so I know some things but not terribly much more than a regular user. I've become like the users to whom I used to say: You know enough to be dangerous, but not enough to fix anything. Why did this happen to me, I'm a good user?! I feel like my wife is in the hospital, my whole life is on hold with my computer!

I agree with you on the inPage error. I believed my RAM was going bad, so I actually paid a local computer repair gal with whom I network to fix it. She never opened the guts of my laptop, but has looked at it twice and both times assured me it wasn't a hard drive or RAM problem. Which makes sense because I don't let my kids use it, I'm careful with it, etc. Maybe I don't surf as safely as some, but I have no fear of swiping and reloading windows (grew up circa Win95, so........).

I also ran chkdsk several times, including at startup. It didn't find any bad sectors.

As for the dump and minidump files, I had tons of huge one them and deleted them after I did steps 1-5 for how to post on this thread (I skipped #6 bec I don't have a CD drive). I figured they were so large because when the crashing started was when I was working on huge word, excel, and pdf files all at the same time. (only 1.7 ghz, apparently not enough for office 365 and files that big). Don't know if any of this matters.

Getting the dump now.

 

[Jared]

The size of the dump file depends on how much is recorded and the type of dump file, the latter is tied with the first reason as the Kernel memory dump contains far more information than the minidump which is why it's larger.

 

[dwolfe]

Well.... it didn't make a memory.dmp file, I'm assuming that's because I haven't had another crash...? I wasn't able to use the computer much today to know if it might be fixed. :huh: