Windows 8 Ongoing BSOD; Static?

badconduct

New Member
Joined
Feb 11, 2014
Hello,

I've been getting an ongoing BSOD. I believe it's caused by static charge when I move by the tower, but I am not certain.

Doesn't seem to be impacted by heavy load; potentially related to removing USB devices (which is why I believe it's static)

I attempted to Debug, but I was getting various errors with the MS Symbols location.

I attached all the BSODs, most are the same errors.

CRITICAL_PROCESS_DIED
0x000000ef

With a few
KERNEL_DATA_INPAGE_ERROR
0x0000007a
(2/1/2014 9:53:36 AM)
 

Attachments

  • 010114-24500-01.dmp
    294.3 KB · Views: 293
  • 010314-23625-01.dmp
    298.7 KB · Views: 317
  • 010414-23140-01.dmp
    302.3 KB · Views: 302
  • 011114-24625-01.dmp
    294.3 KB · Views: 307
  • 012614-12234-01.dmp
    290.3 KB · Views: 281
  • 020114-12531-01.dmp
    306.2 KB · Views: 271
  • 020114-12656-01.dmp
    310.2 KB · Views: 290
  • 020114-12953-01.dmp
    310.6 KB · Views: 312
  • 020314-12578-01.dmp
    310.5 KB · Views: 302
  • 021114-11937-01.dmp
    290.3 KB · Views: 294
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc0001d3b8, ffffffffc000000e, 27aed1860, fffff80003a77460}

Unable to load image \SystemRoot\System32\drivers\atapi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
GetPointerFromAddress: unable to read from fffff802071c7100
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption

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

Hi,
the above is showing that the error lay in your systems disk subsystem. You might need to check on corrupt RAID arrays or if your using a SSD update the firmware.

BiosVersion = 2005
BiosReleaseDate = 09/16/2013
Latest Bios is 2104 with improvements to system stability:
https://www.asus.com/Motherboards/SABERTOOTH_990FX_R20/#support

As memory corruption is mentioned please download and run:
http://www.memtest.org/

AsIO.sys Wed Aug 22 10:54:47 2012:
AsUpIO.sys Tue Aug 03 03:47:59 2010:
ASUS hardware monitoring software related updates for which can be found in the utility section:
https://www.asus.com/Motherboards/SABERTOOTH_990FX_R20/#support

ctaud2k.sys Tue Dec 18 12:02:52 2012: Belongs to Creative Audio drivers. Please update:
http://support.creative.com/

Rt630x64.sys Fri Jun 21 10:29:10 2013: Realtek PCI/PCIe Adapters
http://www.realtek.com.tw/Downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

Post any new dmp files.
 
Have everything up to date at the moment.

Currently using two RAIDs:
One "Hardware" RAID0 on the motherboard. Two Kingston 120 SSD
One software RAID0 through Windows disk management; two Veliciraptors 150GB disks.

Creative Drivers are up to date, but I'd consider removing the sound card if it's a possible cause.

Ran Memtest recently

System IS overclocked though. Monitored often, no issues with heat. Generally doesn't crash during heavy load. I can run Battlefield 4 all day. However; it bluescreen when I was watching a video and unplugged the mouse from USB.
 
So are you saying you updated everything and it's still blue screening?

You could try removing the overclock but as I pointed out the dmp file mentions the disk subsystem as the culprit.
 
Yes, I keep my whole system up to date. Windows is up to date, the firmware and drivers are up to date.

I am starting to think it's one of the SATA cables has a kink in it.
 
If you have a recent dump file then send. If you've updated everything then the dmp file may show something different.
 
Back
Top Bottom