Random BSOD's on Windows 8.1

JumBie

Golden Member
May 2, 2011
1,645
1
71
My specs are as follows:

Intel G3220 3.0Ghz
4GB (2x2GB) Corsair ballistix
Biostar hi-fi H81S2
Samsung PM810 (470) 120GB SSD
Toshiba 500GB HDD (Storage)
Cooler Master 550w PSU
XFX 270x DD edition

I remember over a month ago I got a random BSOD while playing World of Tanks, I did not think much of it and just decided to carry on. During February I noticed that the crashes were becoming more frequent, once every week or 2 weeks to be exact.

A week ago upon turning on the computer I noticed that I was unable to boot into Windows. Nothing worked and I was forced to perform a clean reformat. I was then able to boot into windows but the BSOD's persisted. I am unable to replicate a situation to where a BSOD might occur. They seem to happen randomly, whether it be at the desktop, while watching a video, or while gaming. The following errors are the most common:

On Mon 3/9/2015 10:07:04 PM GMT your computer crashed
crash dump file: C: \WINDOWS\Minidump\030915-5703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0x7A (0xFFFFF6FB402DFB10, 0xFFFFFFFFC000003F, 0x8C229880, 0xFFFFF6805BF62000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C: \WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 3/9/2015 10:07:04 PM GMT your computer crashed
crash dump file: C: \WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7A (0xFFFFF6FB402DFB10, 0xFFFFFFFFC000003F, 0x8C229880, 0xFFFFF6805BF62000)
Error: KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


They have however on occasion pointed towards atikmdag.sys and my realtek audio driver. Both of those have stopped however after updating these drivers individually. I am aware that the two main errors (ntoskrnl.exe and ntkrnlmp.exe) can be caused by a failing hard drive or ram, but can also be the result of bad drivers.

I scanned the SSD last month using CHKDSK and it found some errors and apparently windows was able to fix them (the day after the scan my computer would not boot to windows). Should I just assume that the SSD is the culprit? I am just confused as the BSOD's are random in nature. The computer may run fine for a whole week without a BSOD, or I may find that its blue screening every day, sometimes every hour. A push in the right direction would be much appreciated.
 

Ketchup

Elite Member
Sep 1, 2002
14,545
236
106
Either the drive or RAM. Some options:

1. Run a S.M.A.R.T test. It may tell you right off if there is a problem:
http://crystalmark.info/software/CrystalDiskInfo/index-e.html

2. If you run chkdsk now, is it finding errors? If so,

3. Did you delete the partition or just format it? If a re-install isn't too big a pain at this point, you may want to delete the partition a then install Windows. If you did install on a new partition, the SSD is the culprit.

4. If no additional errors are found, swap out RAM to see if the problem goes away, or download memtest and see if it finds errors: http://www.memtest.org/
 

JumBie

Golden Member
May 2, 2011
1,645
1
71
Either the drive or RAM. Some options:

1. Run a S.M.A.R.T test. It may tell you right off if there is a problem:
http://crystalmark.info/software/CrystalDiskInfo/index-e.html

2. If you run chkdsk now, is it finding errors? If so,

3. Did you delete the partition or just format it? If a re-install isn't too big a pain at this point, you may want to delete the partition a then install Windows. If you did install on a new partition, the SSD is the culprit.

4. If no additional errors are found, swap out RAM to see if the problem goes away, or download memtest and see if it finds errors: http://www.memtest.org/

vANwegO.png


I am going to run a memtest and chkdsk tonight. Also when I went to reformat all I did was click on the drive in the windows setup and click "format". I decided to analyze the DMP file from the most recent crash:

Code:
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: fffff6fb402dfb10, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000003f, error status (normally i/o status code)
Arg3: 000000008c229880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff6805bf62000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000003f - {Bad CRC}  A cyclic redundancy check (CRC) checksum error occurred.

ADDITIONAL_DEBUG_TEXT:  Memory Manager detected corruption of a pagefile page while performing an in-page operation.The data read from storage does not match the original data written.This indicates the data was corrupted by the storage stack, or device hardware.

BUGCHECK_STR:  0x7a_c000003f

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  CCC.exe

CURRENT_IRQL:  0

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

LAST_CONTROL_TRANSFER:  from fffff802823e9717 to fffff802823cf0a0

STACK_TEXT:  
ffffd000`214892c8 fffff802`823e9717 : 00000000`0000007a fffff6fb`402dfb10 ffffffff`c000003f 00000000`8c229880 : nt!KeBugCheckEx
ffffd000`214892d0 fffff802`822b7a6c : 00000000`00000000 00000000`00000000 ffffe000`0238cde8 ffffe000`00000000 : nt! ?? ::FNODOBFM::`string'+0xa187
ffffd000`214893c0 fffff802`8231d958 : 00000000`00000000 00000000`00000000 ffffd000`214894c1 ffffd000`21489451 : nt!MiPfCompletePrefetchIos+0x98
ffffd000`21489420 fffff802`8266ae3b : 00000000`00000009 ffffe000`03793600 00000000`00000000 00000000`00000001 : nt!MiPrefetchVirtualMemory+0x33c
ffffd000`21489520 fffff802`8266930e : 00000000`00001125 00000000`00001125 00000000`00001125 00000000`00000000 : nt!MmPrefetchVirtualMemory+0xe3
ffffd000`21489610 fffff802`82664dd2 : ffffd000`21489720 00000000`00000000 ffffd000`00000004 00000000`00000004 : nt!PfpPrefetchPrivatePages+0x1f2
ffffd000`214896d0 fffff802`8266493a : ffffc000`0ae36000 ffffc000`0ae36000 ffffd000`214898f0 00000000`00000000 : nt!PfpPrefetchRequestPerform+0x22a
ffffd000`21489840 fffff802`82667426 : 00000000`00000001 00000000`00000001 ffffc000`0ae36000 ffffe000`02bf6420 : nt!PfpPrefetchRequest+0x11e
ffffd000`214898c0 fffff802`82666830 : 00000001`589dfd20 00000000`00000000 00000000`00000000 ffffd000`201e0101 : nt!PfSetSuperfetchInformation+0x14a
ffffd000`214899a0 fffff802`823da8b3 : ffffe000`02add880 0000002b`5987f850 00000000`00000000 00000000`00000000 : nt!NtSetSystemInformation+0x1dc
ffffd000`21489c00 00007ffd`f7b6934a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000002a`589dfcb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`f7b6934a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+a187
fffff802`823e9717 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+a187

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5215d156

IMAGE_VERSION:  6.3.9600.16384

BUCKET_ID_FUNC_OFFSET:  a187

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

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

ANALYSIS_SOURCE:  KM

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

FAILURE_ID_HASH:  {35f7dc2f-9d4e-79ab-5aab-b1994d114d0f}

It seems to point to CCC.exe (amd control panel)...not sure what to make of this.
 

JumBie

Golden Member
May 2, 2011
1,645
1
71
Installed the AMD 14.4 drivers (terrible performance) and changed the SATA cable to the SSD. Two days now and not a single crash during video watching, surfing, and gaming. I feel like I am jinxing myself by coming here to report the "good news".
 

Ketchup

Elite Member
Sep 1, 2002
14,545
236
106
Great! and interesting. So are you going to try a better driver, or leave well enough alone?

I am glad you thought of the cable. I forgot to mention it on this one.
 

JumBie

Golden Member
May 2, 2011
1,645
1
71
Great! and interesting. So are you going to try a better driver, or leave well enough alone?

I am glad you thought of the cable. I forgot to mention it on this one.

I want to, actually, I need to change the drivers because the performance with these drivers is unacceptable, there are major differences in FPS while playing certain games. However, I am scared to even touch anything. I don't want to install the newer ones in fear that I will end up having to fool around with drivers again and/or reformat the HDD.
 

JumBie

Golden Member
May 2, 2011
1,645
1
71
Turned on the computer today, it started to "repair windows" after it was completed it booted into the windows 8 recovery options you know; repair, recover, reset, etc.... This was the same screen that I was greeted with before when windows failed to load. I restarted the computer via power button and it booted into windows perfectly fine. Which leaves me wondering, what the hell actually happened? Like seriously, it repaired windows, then deemed it unrecoverable but upon restart it worked perfectly fine. I have no idea whats going on.
 

mikeymikec

Lifer
May 19, 2011
17,581
9,273
136
As ketchup79 suggested, I'd check the disk and RAM.

chkdsk C: /f /v /r

memtest86+ for a few passes.

Normally a full disk check on a 128GB SSD takes about 5-10 minutes, at least on the SSDs I use.
 

JumBie

Golden Member
May 2, 2011
1,645
1
71
As ketchup79 suggested, I'd check the disk and RAM.

chkdsk C: /f /v /r

memtest86+ for a few passes.

Normally a full disk check on a 128GB SSD takes about 5-10 minutes, at least on the SSDs I use.

No errors on the SSD or on the two sticks of ram (ran them both separately).
 
Last edited:

JumBie

Golden Member
May 2, 2011
1,645
1
71
Update:

The issue that occurred on the 14th was the last one to affect this computer. The one in which the computer booted and tried to repair the SSD, failed, and then gave me Win 8 options to either; reset, refresh or restore. Not sure still to this day why that just randomly happened on boot up.

Ever since then its been smooth sailing, boots up fine, shuts down fine. No problems running software, videos, games, or just general use and browsing. Could we still assume that the SSD is defective?

My last real solution was to change the SATA cord and to reformat the drive, after that no BSODs have occurred, the only issue being that one that was previously mentioned. Should I cross my fingers and pray nothing happens? Could symptoms of a bad SSD really remain dormant for this long before showing face once again?
 

redzo

Senior member
Nov 21, 2007
547
5
81
No errors on the SSD or on the two sticks of ram (ran them both separately).

You should test RAM according to your use case: leave both modules installed. Fire up memtest86+ in the evening and check the results in the morning!
 

Charlie98

Diamond Member
Nov 6, 2011
6,292
62
91
Personally, I would be thinking about replacing that SSD anyway. I know it says it has plenty of life left, and the SMART looked pretty good (with very little writes, per se) but that ~30K hour thing bugs me, and it's starting to burn up some reserve blocks.

Definitely run both RAM sticks with memtest.
 

Puffnstuff

Lifer
Mar 9, 2005
16,015
4,785
136
Ditto on memtest because problems just don't correct themselves. Best to know for sure what caused the problem and address it properly so it doesn't come back and bite you later.
 

JumBie

Golden Member
May 2, 2011
1,645
1
71
You should test RAM according to your use case: leave both modules installed. Fire up memtest86+ in the evening and check the results in the morning!

Personally, I would be thinking about replacing that SSD anyway. I know it says it has plenty of life left, and the SMART looked pretty good (with very little writes, per se) but that ~30K hour thing bugs me, and it's starting to burn up some reserve blocks.

Definitely run both RAM sticks with memtest.

Ditto on memtest because problems just don't correct themselves. Best to know for sure what caused the problem and address it properly so it doesn't come back and bite you later.

Ran memtest on both sticks at the same time over night, no errors what so ever.

Still haven't had any problems since the 14th. I was thinking about replacing the SSD but I think I am going to give it another shot. If anything happens in the near future I guess it will be the first piece of hardware I replace.
 

JumBie

Golden Member
May 2, 2011
1,645
1
71
So its been 18 days and the BSOD's started back up again. Tried to launch a game an noticed that it was freezing, relaunching it didn't give a different result. I decided to restart the computer but noticed that it was hanging on "shutting down" for 10 minutes. I took matters into my own hands and manually shut the computer down via the power button. Computer booted up just fine, after a few minutes of gaming the first BSOD occurred.

On Wed 4/1/2015 3:09:29 PM GMT your computer crashed
crash dump file: C: \WINDOWS\Minidump\040115-6031-01.dmp
This was probably caused by the following module: luafv.sys (luafv+0x19010)
Bugcheck code: 0x7A (0xFFFFF6FC000180C8, 0xFFFFFFFFC000003F, 0x3C3A1880, 0xFFFFF80003019010)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C: \WINDOWS\system32\drivers\luafv.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: LUA File Virtualization Filter Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

After the computer started up again I decided to test out the same game, and sure enough after about 30 minutes the computer blue screened again.

On Wed 4/1/2015 4:47:18 PM GMT your computer crashed
crash dump file: C: \WINDOWS\Minidump\040115-5859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0x7A (0xFFFFF6FB4037FD78, 0xFFFFFFFFC000003F, 0x266C8880, 0xFFFFF6806FFAF000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C: \WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

So here we are 14 days later and the problem seems to have magically come back to life. Not sure what steps to take now.

It appears that if I don't open up any games and strictly use the computer for browsing and video then the computer will not bsod.
 
Last edited:

Ketchup

Elite Member
Sep 1, 2002
14,545
236
106
This bug check indicates that the requested page of kernel data from the paging file could not be read into memory

Sounds like it's the drive then. That error is indicating that the data was corrupted when brought into memory from the page file. Disabling the page file "may" work around this issue until you are able to get a new drive. If you hadn't already replaced the cord, I would recommend giving that a shot as well.
 

JumBie

Golden Member
May 2, 2011
1,645
1
71
Sounds like it's the drive then. That error is indicating that the data was corrupted when brought into memory from the page file. Disabling the page file "may" work around this issue until you are able to get a new drive. If you hadn't already replaced the cord, I would recommend giving that a shot as well.

Turning off the paging file seems to have stopped the BSODs. None have occurred since the incident.
 

Ketchup

Elite Member
Sep 1, 2002
14,545
236
106
Turning off the paging file seems to have stopped the BSODs. None have occurred since the incident.

And there are those that would argue even using the page file with an SSD and plenty of RAM (I wouldn't recommend making it permanent with only 4 GB). But at least you aren't living with consistent blue screens until you are ready for a new drive.
 

inachu

Platinum Member
Aug 22, 2014
2,387
2
41
As a test you could get another drive and put that swap file onto that new drive and dedicate it just for the sap file and nothing else. If you still do not get any BSOD from using the swap file on that new drive then that further confirms the C: could be going bad.

But even knowing that disabling the swapfile stops the BSOD would put a smile on my face.


One other tests to confirm some more would be to disable the restore feature while swap file is enabled.
 
Last edited: