Crashes after sleep sometimes

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > Haus of Tech Support > Crashes after sleep sometimes

Anything is Fine: Jul 11, 2012

Problem description: I have been having issues with my computer waking up from sleep. It seems like after the computer sleeps for �a long time� (tends to be overnight) it crashes with a KERNEL_STACK_INPAGE_ERROR, which according to the crash dump was �Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1ecfd )�. My computer was fine until I experimented with Linux�s Xen server. My experimenting required the addition of a spare video card and modification of bois settings. After I finished my experimentation, I reset the bios to the optimized defaults and reinstalled Windows (from an image I had made when I originally set up the computer) and it would no longer wake up from sleep.

Attempted fixes:
1. Resetting the bios
2. Installing all the drivers for the Mobo and Graphics card
3. Replaced the HDD (the SMART claimed that it had gone bad)
4. Replaced SATA cable attached the HDD
5. Ran MemTest86+ for 12 hours
6. Stress tested the Graphics card and CPU
7. Fresh install of Windows
8. Replaced video card with a spare video card
9. Upgraded the BIOS

Recent changes: I shifted hardware around in the PC. Removed the AMD video card replacing it with an NVidia card (I have sense put the AMD one back in). Reconfigured the BIOS settings to enable Xen server and then loaded the optimized defaults when I was done.

Operating system: e.g. Windows 8.1 Pro U1 x64

System specs:
Mobo: Asus M5A99FX Pro R2.0
CPU: AMD FX-8320 Eight-Core Processor
Memory: 1 KHX1600C10D3B/8G module, 1/2 KVR 1333D3N9K2/4G kit for a total of 10GB
Graphics Card: AMD Radeon HD 6700
HDD: Seagate Hybrid Drive ST1000DX001

Location: USA

I have Googled and read the FAQ: Yes. I couldn�t find anything other than a security FAQ.

Other relevant information
Event log entries:
1. �The AODDriver4.3 service failed to start due to the following error: The system cannot find the file specified.�
2. �The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4). This can result in reduced resume performance.�
An Error which occurred on resume of sleep:
�The instruction at 0x00007FFA4AD167D5 referenced memory at 0x00007FFA226C40100. The required data was not placed into memory because of an I/O error status of 0xc000000e.�

Crash Dump (I can post the actual Memory.dmp file if necessary):

code:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       symsrv*symsrv.dll*c:\localsymbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Symbol search path is: symsrv*symsrv.dll*c:\localsymbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is: 
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff803`ee418000 PsLoadedModuleList = 0xfffff803`ee6e22d0
Debug session time: Wed Sep 17 11:14:48.743 2014 (UTC - 7:00)
System Uptime: 0 days 14:57:00.106
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff5`ffffd018).  Type ".hh dbgerr001" for details
Loading unloaded module list
........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fac0080000, ffffffffc00000c0, adcc2880, fffff58010000000}

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

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

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

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


ERROR_CODE: (NTSTATUS) 0xc00000c0 - This device does not exist.

BUGCHECK_STR:  0x7a_c00000c0

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  RtkNGUI64.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME:  ffffd0011f6b34f0 -- (.trap 0xffffd0011f6b34f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=fffff580108042e8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803ee816924 rsp=ffffd0011f6b3680 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffff58010000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiCommitPageTablesForVad+0x1c0:
fffff803`ee816924 410fa302        bt      dword ptr [r10],eax ds:fffff580`10000000=00000000
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff803ee59b1ad to fffff803ee56bfa0

STACK_TEXT:  
ffffd001`1f6b31f8 fffff803`ee59b1ad : 00000000`0000007a fffff6fa`c0080000 ffffffff`c00000c0 00000000`adcc2880 : nt!KeBugCheckEx
ffffd001`1f6b3200 fffff803`ee4a05f8 : 00000000`00000002 ffffd001`1f6b3368 ffffe001`2e329a98 ffffd001`00000000 : nt! ?? ::FNODOBFM::`string'+0x1ecfd
ffffd001`1f6b32f0 fffff803`ee47f5f5 : ffffe001`2ed03080 ffffe001`2e329a98 00000000`c0033333 fffff803`00000000 : nt!MiIssueHardFault+0x184
ffffd001`1f6b33b0 fffff803`ee57622f : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd001`1f6b34f0 : nt!MmAccessFault+0x3d5
ffffd001`1f6b34f0 fffff803`ee816924 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff803`eeba769a : nt!KiPageFault+0x12f
ffffd001`1f6b3680 fffff803`ee486ed4 : fffff6fa`c0080000 00000000`00000001 00000000`00000001 00000000`00000001 : nt!MiCommitPageTablesForVad+0x1c0
ffffd001`1f6b36f0 fffff803`ee81563c : ffffe001`2effa1b0 00000000`00000001 ffffd001`1f6b3b00 00000000`00000004 : nt!MiCommitExistingVad+0x314
ffffd001`1f6b3810 fffff803`ee5777b3 : ffffe001`2ed03080 00000000`0013fdf8 ffffd001`1f6b3a28 00000001`401dd250 : nt!NtAllocateVirtualMemory+0x46c
ffffd001`1f6b3a10 00007ffd`e84717fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0013e9a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`e84717fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+1ecfd
fffff803`ee59b1ad cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+1ecfd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  53388e13

BUCKET_ID_FUNC_OFFSET:  1ecfd

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

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

ANALYSIS_SOURCE:  KM

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

FAILURE_ID_HASH:  {90f07b7f-b6ca-d03a-b3d4-2f5aff8f8644}

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

Anything is Fine fucked around with this message at 23:24 on Sep 17, 2014

# ? Sep 17, 2014 23:02

Adbot: ADBOT LOVES YOU

# ? Apr 27, 2024 02:56

Alereon: Feb 6, 2004; Dehumanize yourself and face to Trumpshed; College Slice

Remove the 2GB memory module and retest. RAM needs to be installed in matched pairs, using only one module or an incorrect memory configuration cuts memory bandwidth in half, murdering system performance, so if that does fix the problem getting a second 8GB module that matches the one you have is your best bet. In the future always buy RAM in dual-channel kits.

# ? Sep 18, 2014 00:14

Zarc: Jul 25, 2014

Also, 3rd party drivers tend to have problems with sleep mode and causing BSOD's coming out of it due to poor coding, though with it seeming to be time related, the memory bit Alereon mentioned the most likely cause

# ? Sep 18, 2014 00:55

Anything is Fine: Jul 11, 2012

Alereon posted:

Remove the 2GB memory module and retest. RAM needs to be installed in matched pairs, using only one module or an incorrect memory configuration cuts memory bandwidth in half, murdering system performance, so if that does fix the problem getting a second 8GB module that matches the one you have is your best bet. In the future always buy RAM in dual-channel kits.

I just pulled out the 2gb stick and was able to reproduce the crashing issue. I have also tried it with the other stick in the past and seen the same issue.

Zarc posted:

Also, 3rd party drivers tend to have problems with sleep mode and causing BSOD's coming out of it due to poor coding, though with it seeming to be time related, the memory bit Alereon mentioned the most likely cause

I have tried it with both the Microsoft Drivers (the drivers collected from Windows Update) and the ASUS provided drivers. Neither have seemed to make much difference. Is there any way that I can have Windows provide me with a list of installed drivers?

Anything is Fine fucked around with this message at 00:59 on Sep 18, 2014

# ? Sep 18, 2014 00:56

Zarc: Jul 25, 2014

Microsoft drivers are generally pretty good and unlikely to have sleep issues. It's far more likely for something like DRM drivers (Sony rootkit fiasco) to have problems.

How old are your graphics drivers, what version? ATI has a boom/bust history with their driver quality.

p.s. A crystal disk info report on your hard drives would be helpful. Some of the info you posted could be indicative of hard drive problems

# ? Sep 18, 2014 01:55

Anything is Fine: Jul 11, 2012

Zarc posted:

Microsoft drivers are generally pretty good and unlikely to have sleep issues. It's far more likely for something like DRM drivers (Sony rootkit fiasco) to have problems.

When I tried the fresh install of Windows 8.1, I did not use anything other than the standard Microsoft drivers provided by Windows Update.

Zarc posted:

How old are your graphics drivers, what version? ATI has a boom/bust history with their driver quality.

14.4 which was released on 4/24/2014. This is the current version according to the AMD site. I have also tried the ones from Windows Update to no avail.

Zarc posted:

p.s. A crystal disk info report on your hard drives would be helpful. Some of the info you posted could be indicative of hard drive problems

code:

----------------------------------------------------------------------------
CrystalDiskInfo 6.2.1 (C) 2008-2014 hiyohiyo
                                Crystal Dew World : [url]http://crystalmark.info/[/url]
----------------------------------------------------------------------------

    OS : Windows 8.1 Pro [6.3 Build 9600] (x64)
  Date : 2014/09/17 19:42:55

-- Controller Map ----------------------------------------------------------
 + Standard SATA AHCI Controller [ATA]
   - TSSTcorp CDDVDW SH-222BB
 - Microsoft Storage Spaces Controller [SCSI]
 + Asmedia 106x SATA Controller [SCSI]
   - ST1000DX001-1CM162

-- Disk List ---------------------------------------------------------------
 (1) ST1000DX001-1CM162 : 1000.2 GB [0/1/0, pd1] - st

----------------------------------------------------------------------------
 (1) ST1000DX001-1CM162
----------------------------------------------------------------------------
           Model : ST1000DX001-1CM162
        Firmware : CC43
   Serial Number : Z1DD1TLD
       Disk Size : 1000.2 GB (8.4/137.4/1000.2/1000.2)
     Buffer Size : Unknown
     Queue Depth : 32
    # of Sectors : 1953525168
   Rotation Rate : 7200 RPM
       Interface : Serial ATA
   Major Version : ACS-2
   Minor Version : ACS-3 Revision 3b
   Transfer Mode : SATA/600 | SATA/600
  Power On Hours : 181 hours
  Power On Count : 159 count
     Temperature : 33 C (91 F)
   Health Status : Good
        Features : S.M.A.R.T., APM, 48bit LBA, NCQ
       APM Level : 8080h [ON]
       AAM Level : ----

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
01 108 _99 __6 000000E01168 Read Error Rate
03 _98 _97 __0 000000000000 Spin-Up Time
04 100 100 _20 000000000087 Start/Stop Count
05 100 100 _10 000000000000 Reallocated Sectors Count
07 _69 _60 _30 000000917BE7 Seek Error Rate
09 100 100 __0 0000000000B5 Power-On Hours
0A 100 100 _97 000000000000 Spin Retry Count
0C 100 100 _20 00000000009F Power Cycle Count
B7 100 100 __0 000000000000 Vendor Specific
B8 100 100 _99 000000000000 End-to-End Error
BB 100 100 __0 000000000000 Reported Uncorrectable Errors
BC 100 _99 __0 000400040006 Command Timeout
BD 100 100 __0 000000000000 High Fly Writes
BE _67 _65 _45 000022200021 Airflow Temperature
BF 100 100 __0 000000000000 G-Sense Error Rate
C0 100 100 __0 00000000001D Power-off Retract Count
C1 100 100 __0 0000000001B8 Load/Unload Cycle Count
C2 _33 _40 __0 001700000021 Temperature
C5 100 100 __0 000000000000 Current Pending Sector Count
C6 100 100 __0 000000000000 Uncorrectable Sector Count
C7 200 200 __0 000000000000 UltraDMA CRC Error Count
F0 100 253 __0 FD7100000112 Head Flying Hours
F1 100 253 __0 0000EFB7C102 Total Host Writes
F2 100 253 __0 000082BDBD25 Total Host Reads

-- IDENTIFY_DEVICE ---------------------------------------------------------
        0    1    2    3    4    5    6    7    8    9
000: 0C5A 3FFF C837 0010 0000 0000 003F 0000 0000 0000
010: 2020 2020 2020 2020 2020 2020 5A31 4444 3154 4C44
020: 0000 0000 0004 4343 3433 2020 2020 5354 3130 3030
030: 4458 3030 312D 3143 4D31 3632 2020 2020 2020 2020
040: 2020 2020 2020 2020 2020 2020 2020 8010 4000 2F00
050: 4000 0200 0200 0007 3FFF 0010 003F FC10 00FB 0110
060: FFFF 0FFF 0000 0007 0003 0078 0078 0078 0078 0000
070: 0000 0000 0000 0000 0000 001F 850E 0006 004C 0040
080: 03F0 001F 346B 7D09 4163 3469 BC09 4163 207F 0032
090: 0032 8080 FFFE 0000 D0D0 0000 0000 0000 0000 0000
100: 6DB0 7470 0000 0000 0000 0000 6003 0000 5000 C500
110: 7909 F09D 0000 0000 0000 0000 0000 0000 0000 401E
120: 401C 0000 0000 0000 0000 0000 0000 0000 0029 6DB0
130: 7470 6DB0 7470 2020 0002 0140 0100 5000 3C06 3C0A
140: 0000 003C 0000 0008 0000 0000 05FF 0280 0000 0000
150: 0008 0000 0000 0000 0000 0001 0000 0000 5800 8806
160: 0000 0000 0000 0000 0000 0000 0000 0000 0002 0000
170: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
180: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
190: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
200: 0000 0000 0000 0000 0000 0000 1081 0000 0000 4000
210: 0000 0000 0000 0000 0000 0000 0000 1C20 0000 0000
220: 0000 0000 107E 0000 0000 0000 0000 0000 0000 0000
230: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
240: 0000 0000 0000 0003 0000 0000 0000 0000 0000 0000
250: 0000 0000 0000 0000 0000 A8A5

-- SMART_READ_DATA ---------------------------------------------------------
     +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 0A 00 01 0F 00 6C 63 68 11 E0 00 00 00 00 03 03
010: 00 62 61 00 00 00 00 00 00 00 04 32 00 64 64 87
020: 00 00 00 00 00 00 05 33 00 64 64 00 00 00 00 00
030: 00 00 07 0F 00 45 3C E7 7B 91 00 00 00 00 09 32
040: 00 64 64 B5 00 00 00 00 00 00 0A 13 00 64 64 00
050: 00 00 00 00 00 00 0C 32 00 64 64 9F 00 00 00 00
060: 00 00 B7 32 00 64 64 00 00 00 00 00 00 00 B8 32
070: 00 64 64 00 00 00 00 00 00 00 BB 32 00 64 64 00
080: 00 00 00 00 00 00 BC 32 00 64 63 06 00 04 00 04
090: 00 00 BD 3A 00 64 64 00 00 00 00 00 00 00 BE 22
0A0: 00 43 41 21 00 20 22 00 00 00 BF 32 00 64 64 00
0B0: 00 00 00 00 00 00 C0 32 00 64 64 1D 00 00 00 00
0C0: 00 00 C1 32 00 64 64 B8 01 00 00 00 00 00 C2 22
0D0: 00 21 28 21 00 00 00 17 00 00 C5 12 00 64 64 00
0E0: 00 00 00 00 00 00 C6 10 00 64 64 00 00 00 00 00
0F0: 00 00 C7 3E 00 C8 C8 00 00 00 00 00 00 00 F0 00
100: 00 64 FD 12 01 00 00 71 FD 2B F1 00 00 64 FD 02
110: C1 B7 EF 00 00 00 F2 00 00 64 FD 25 BD BD 82 00
120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
160: 00 00 00 00 00 00 00 00 00 00 00 00 3F 02 00 73
170: 03 00 01 00 01 69 02 00 00 00 00 00 00 00 00 00
180: 00 00 00 00 00 00 00 00 07 03 03 03 03 03 03 03
190: 02 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00
1A0: 00 00 00 00 00 00 00 00 48 B3 C3 CE 97 00 00 00
1B0: 00 00 00 00 01 00 F6 06 02 C1 B7 EF 00 00 00 00
1C0: 25 BD BD 82 00 00 00 00 00 00 00 00 00 00 00 00
1D0: 00 00 00 00 00 00 00 00 8E 1C 00 00 01 00 00 00
1E0: 00 00 00 00 18 03 01 00 00 00 00 00 00 00 00 01
1F0: 00 00 00 00 00 00 00 00 00 00 14 18 00 00 00 FB

-- SMART_READ_THRESHOLD ----------------------------------------------------
     +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 01 00 01 06 00 00 00 00 00 00 00 00 00 00 03 00
010: 00 00 00 00 00 00 00 00 00 00 04 14 00 00 00 00
020: 00 00 00 00 00 00 05 0A 00 00 00 00 00 00 00 00
030: 00 00 07 1E 00 00 00 00 00 00 00 00 00 00 09 00
040: 00 00 00 00 00 00 00 00 00 00 0A 61 00 00 00 00
050: 00 00 00 00 00 00 0C 14 00 00 00 00 00 00 00 00
060: 00 00 B7 00 00 00 00 00 00 00 00 00 00 00 B8 63
070: 00 00 00 00 00 00 00 00 00 00 BB 00 00 00 00 00
080: 00 00 00 00 00 00 BC 00 00 00 00 00 00 00 00 00
090: 00 00 BD 00 00 00 00 00 00 00 00 00 00 00 BE 2D
0A0: 00 00 00 00 00 00 00 00 00 00 BF 00 00 00 00 00
0B0: 00 00 00 00 00 00 C0 00 00 00 00 00 00 00 00 00
0C0: 00 00 C1 00 00 00 00 00 00 00 00 00 00 00 C2 00
0D0: 00 00 00 00 00 00 00 00 00 00 C5 00 00 00 00 00
0E0: 00 00 00 00 00 00 C6 00 00 00 00 00 00 00 00 00
0F0: 00 00 C7 00 00 00 00 00 00 00 00 00 00 00 F0 00
100: 00 00 00 00 00 00 00 00 00 00 F1 00 00 00 00 00
110: 00 00 00 00 00 00 F2 00 00 00 00 00 00 00 00 00
120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FD

Update: I just ran SeaTools on it and it failed the "Short Drive Self Test" but has currently passed the "Short Generic Test". Is this a sign that the drive might be bad?

Anything is Fine fucked around with this message at 06:02 on Sep 18, 2014

# ? Sep 18, 2014 03:52

Alereon: Feb 6, 2004; Dehumanize yourself and face to Trumpshed; College Slice

Yes, the drive has failed and will need to be replaced.

# ? Sep 18, 2014 20:25

Zarc: Jul 25, 2014

Anything is Fine posted:

Update: I just ran SeaTools on it and it failed the "Short Drive Self Test" but has currently passed the "Short Generic Test". Is this a sign that the drive might be bad?

Yeah, I agree with alereon. Backup your data while you still can and get a new drive

# ? Sep 18, 2014 20:27

Anything is Fine: Jul 11, 2012

Alereon posted:

Yes, the drive has failed and will need to be replaced.

Zarc posted:

Yeah, I agree with alereon. Backup your data while you still can and get a new drive

I attempted to rerun the tests using the DOS SeaTools. The DOS tools were unable to discover my hard drive, so I moved it from a SATA port labeled in the manual as "ASMedia Serial ATA 6.0 Gb/s connectors (7-pin SATA6G_E12 [navy blue])" to another port labeled "AMD Serial ATA 6.0 Gb/s connectors (7-pin SATA6G_1-5 [gray])". At this point, I reran the SeaTools test and it passed. I have so far been unable to replicate my crashing issues. What is the difference between these two kinds of SATA ports? Is it still necessary to look into replacing my hard drive?

# ? Sep 20, 2014 07:12

Mo_Steel: Mar 7, 2008; Let's Clock Into The Sunset Together; Fun Shoe

Anything is Fine posted:

I attempted to rerun the tests using the DOS SeaTools. The DOS tools were unable to discover my hard drive, so I moved it from a SATA port labeled in the manual as "ASMedia Serial ATA 6.0 Gb/s connectors (7-pin SATA6G_E12 [navy blue])" to another port labeled "AMD Serial ATA 6.0 Gb/s connectors (7-pin SATA6G_1-5 [gray])". At this point, I reran the SeaTools test and it passed. I have so far been unable to replicate my crashing issues. What is the difference between these two kinds of SATA ports? Is it still necessary to look into replacing my hard drive?

Typically motherboard manufacturers want more ports on a standard motherboard than a single integrated controller is capable of handling / specified for. In order to get the number of ports they want they put a third-party controller with additional ports onto the motherboard. Generally the manufacturer recommends using the main controller for boot devices and the third party for other media. According to the motherboard manual you should only use the ASMedia ports for data drives:

As for the drive, I'd say backup your data to be safe and then keep an eye on it. If it keeps passing S.M.A.R.T. checks and stops crashing I'd suspect ASMedia drivers were at fault. If it fails then you have a backup and can proceed to buy a replacement drive.

# ? Sep 21, 2014 13:02

Adbot: ADBOT LOVES YOU

# ? Apr 27, 2024 02:56

Anything is Fine: Jul 11, 2012

Mo_Steel posted:

Typically motherboard manufacturers want more ports on a standard motherboard than a single integrated controller is capable of handling / specified for. In order to get the number of ports they want they put a third-party controller with additional ports onto the motherboard. Generally the manufacturer recommends using the main controller for boot devices and the third party for other media. According to the motherboard manual you should only use the ASMedia ports for data drives:

As for the drive, I'd say backup your data to be safe and then keep an eye on it. If it keeps passing S.M.A.R.T. checks and stops crashing I'd suspect ASMedia drivers were at fault. If it fails then you have a backup and can proceed to buy a replacement drive.

Thanks Mo_Steel. I will keep my drive on the integrated controller and keep a backup of the data. And thanks Alereon and Zarc, your information was very helpful. I've been trying to solve this problem for a couple of months, and your information led me to an answer.

# ? Sep 24, 2014 05:03

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > Haus of Tech Support > Crashes after sleep sometimes