BSOD using Asus Update on Asus Suite II

Sour · 02 Jan 2012

Whenever I click on the Asus Update on Asus Suite II it automatically gives me a BSOD. It then tells me to update the driver. I uninstalled Asus Suite II and installed the latest version from the Asus website. It still gave a BSOD when I clicked Update.

A little bit about my comp:
64 Bit Windows 7 put together by myself.
It is fairly new. Maybe 3 months max. Got BSOD since the start. Trying to update BIOS atm.
My OS installation is the same age.

I also have another thread:
https://www.sevenforums.com/crashes-d...bernation.html

Still haven't figured this dang BSOd out.

BTW: Motherboard is
P8Z68-V PRO

usasma · 02 Jan 2012

NOTE: I have severe eye problems. If I do not respond to your postings, please PM another staff member for assistance.

I suggest starting all troubleshooting with the following diagnostic tests (located at this link: Hardware Diagnostics ). They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
Hard Drive Diagnostics (read the details at the link) - Test ALL of the hard drives.

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Resources (read the details at the link)
There are also free, bootable antivirus disks at this link: Free Online AntiMalware Resources - Bootable Disks

No memory dumps from later than Oct 2011
Service Pack 1 isn't installed, please do the following:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
5. Visit Windows Update and get any other available updates

No memory dumps in the WER section of MSINFO32 after Oct 2011

More to follow once the memory dumps are finished running....

usasma · 02 Jan 2012

Looks like the hard drive. Many of the October dump files point to "hardware_disk" as the source of the error.
Please run the diagnostics at the top of the previous post.

Make sure that you turn Driver Verifier off. It's no longer required and it'll continue to cause BSOD's while it's running.

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-20108-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 23 21:14:38.111 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:43.141
BugCheck F4, {3, fffffa8009b16b30, fffffa8009b16e10, fffff80002f8c300}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_VRF_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`09b16b30 fffffa80`09b16e10 fffff800`02f8c300
BiosVersion = 0606
BiosReleaseDate = 06/24/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-20529-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 23 20:45:36.595 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:33.015
BugCheck F4, {3, fffffa8009b36b30, fffffa8009b36e10, fffff80002f92300}
Probably caused by : hardware_disk
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xF4_IOERR_C000000E
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000000E_VRF_IMAGE_hardware_disk
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`09b36b30 fffffa80`09b36e10 fffff800`02f92300
BiosVersion = 0606
BiosReleaseDate = 06/24/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-20124-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 23 20:16:44.611 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:13.032
BugCheck F4, {3, fffffa80099eeb30, fffffa80099eee10, fffff80002fcd300}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_VRF_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`099eeb30 fffffa80`099eee10 fffff800`02fcd300
BiosVersion = 0606
BiosReleaseDate = 06/24/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-21060-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 23 19:48:13.138 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:20.168
BugCheck F4, {3, fffffa8009aa0b30, fffffa8009aa0e10, fffff80002fc4300}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_VRF_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`09aa0b30 fffffa80`09aa0e10 fffff800`02fc4300
BiosVersion = 0606
BiosReleaseDate = 06/24/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-23103-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 23 19:19:33.915 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:12.335
BugCheck F4, {3, fffffa8009a6cb30, fffffa8009a6ce10, fffff80002f87300}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_VRF_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`09a6cb30 fffffa80`09a6ce10 fffff800`02f87300
BiosVersion = 0606
BiosReleaseDate = 06/24/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-23056-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 23 18:51:02.979 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:27.399
BugCheck F4, {3, fffffa80097dfb30, fffffa80097dfe10, fffff80002fc8300}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_VRF_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`097dfb30 fffffa80`097dfe10 fffff800`02fc8300
BiosVersion = 0606
BiosReleaseDate = 06/24/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-32822-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 23 18:14:20.607 2011 (UTC - 5:00)
System Uptime: 0 days 4:21:49.011
BugCheck F4, {3, fffffa8008fd2b30, fffffa8008fd2e10, fffff80002fce300}
Probably caused by : hardware_disk
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_IOERR_C000009D
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000009D_IMAGE_hardware_disk
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`08fd2b30 fffffa80`08fd2e10 fffff800`02fce300
BiosVersion = 0606
BiosReleaseDate = 06/24/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-23431-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 23 13:51:17.710 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:52.115
BugCheck F4, {3, fffffa8008cb7b30, fffffa8008cb7e10, fffff80002fdb300}
Probably caused by : hardware_disk
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_IOERR_C000009D
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000009D_IMAGE_hardware_disk
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`08cb7b30 fffffa80`08cb7e10 fffff800`02fdb300
BiosVersion = 0606
BiosReleaseDate = 06/24/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-34710-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 23 13:21:54.607 2011 (UTC - 5:00)
System Uptime: 0 days 3:41:41.012
BugCheck F4, {3, fffffa8008f88b30, fffffa8008f88e10, fffff80002fdc300}
Probably caused by : hardware_disk
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_IOERR_C000009D
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000009D_IMAGE_hardware_disk
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`08f88b30 fffffa80`08f88e10 fffff800`02fdc300
BiosVersion = 0606
BiosReleaseDate = 06/24/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-28672-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 23 09:39:00.610 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:27.015
BugCheck F4, {3, fffffa8008fa6b30, fffffa8008fa6e10, fffff80002fd2300}
Probably caused by : hardware_disk
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_IOERR_C000009D
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000009D_IMAGE_hardware_disk
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`08fa6b30 fffffa80`08fa6e10 fffff800`02fd2300
BiosVersion = 0606
BiosReleaseDate = 06/24/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-25630-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 23 09:10:21.148 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:33.178
BugCheck F4, {3, fffffa8009081b30, fffffa8009081e10, fffff80002f86300}
Probably caused by : hardware_disk
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_IOERR_C000000E
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`09081b30 fffffa80`09081e10 fffff800`02f86300
BiosVersion = 0606
BiosReleaseDate = 06/24/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-28719-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 23 08:41:34.686 2011 (UTC - 5:00)
System Uptime: 0 days 0:17:28.091
BugCheck F4, {3, fffffa8009140b30, fffffa8009140e10, fffff80002f86300}
Probably caused by : hardware_disk
PROCESS_NAME:  wininit.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_IOERR_C000000E
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`09140b30 fffffa80`09140e10 fffff800`02f86300
BiosVersion = 0606
BiosReleaseDate = 06/24/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-33228-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 23 03:50:22.999 2011 (UTC - 5:00)
System Uptime: 0 days 0:28:53.029
BugCheck F4, {3, fffffa80092fab30, fffffa80092fae10, fffff80002f80300}
Probably caused by : hardware_disk
PROCESS_NAME:  wininit.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_IOERR_C000000E
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`092fab30 fffffa80`092fae10 fffff800`02f80300
BiosVersion = 0606
BiosReleaseDate = 06/24/2011
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Sour · 02 Jan 2012

I forgot to say that my HardDrive is actually fairly old. The rest of my equipment is 3 months old. Also my Video Card is fairly new.

I can't find the exact hard drive test for it. What should I do?

Btw, I found this.
ASUSTeK Computer Inc. -Support- FAQ P8Z68-V PRO

It is pretty much exactly what is happening, when I try to download the hotfix and run it, it says
"The update is not applicable to your computer."

In the requirements it says if the HDD is over 1TB, mine is only 500GB though.

I also did about 3 memory tests when I posted the other thread. One time I got one error. The next two times I ran it for over 12+ hours and I got no errors.

usasma · 02 Jan 2012

Run the Western Digital hard drive test.
If that doesn't work for you, then try the Seagate Seatools
If that doessn't work, then try the Hitach Drive Fitness Test

The actual article from Microsoft ( You receive various Stop error messages in Windows 7 or in Windows Server 2008 R2 when you try to resume a computer that has a large SATA hard disk ) doesn't specify a size for the HDD - it just states a "large" hard drive.
But regardless - 500 gB just isn't a large hard drive no matter how you slice it. The update doesn't apply to you.

Sour · 02 Jan 2012

I have a Western Digital HardDrive, but the Western Digital test refuses to find my harddrive. I followed the instructions for it.

I will try to do the other two tests soon, but just wanted to point the above problem out. Maybe it means something.

usasma · 02 Jan 2012

At work we've had a lot of problems with the W-D test working
So we use the Seagate Seatools or the Hitachi DFT

Sour · 08 Jan 2012

Sorry that I haven't been on recently to reply to this thread. Anyways, I just tried the Seagate test and it also did not detect my HD. I am wondering if something is wrong with it now. No test has found it ;o

usasma · 09 Jan 2012

First, if you're able, backup your data from the old hard drive. The longer that you wait, the less likely it is that you'll be able to recover it.

Then try several other hard drive tests to see if you can detect it.
Then try another hard drive. If you have to purchase one, purchase it from a store where you can return it if it's not needed (check first).

Good Luck!

Corriador · 26 Jan 2014

I was not intending to post on BSOD and have not had that occur. Just trying to solve sound issue.

BSOD using Asus Update on Asus Suite II

BSOD using Asus Update on Asus Suite II

Bsod