BSOD Might be Hardware, but I can't tell

Hello there,

Seems like the new dump file is referring to hard drive and reg booster. Do you any external HDD connected? If so remove it. If there is any then run Hard drive Diagnostic. You'll find the tool in manufacture's website.

Code:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000006, The exception code that was not handled
Arg2: fffff80002f513ef, The address that the exception occurred at
Arg3: fffff880009a97f8, Exception Record Address
Arg4: fffff880009a9060, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0xlx" referenced memory at "0xlx". The required data was not placed into memory because of an I/O error status of "0xlx".

FAULTING_IP: 
nt!_report_gsfailure+5f
fffff800`02f513ef 3a0c10          cmp     cl,byte ptr [rax+rdx]

EXCEPTION_RECORD:  fffff880009a97f8 -- (.exr 0xfffff880009a97f8)
ExceptionAddress: fffff80002f513ef (nt!_report_gsfailure+0x000000000000005f)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000770f5855
   Parameter[2]: 00000000c0000428
Inpage operation failed at 00000000770f5855, due to I/O error 00000000c0000428

CONTEXT:  fffff880009a9060 -- (.cxr 0xfffff880009a9060)
rax=fffff80003398aa0 rbx=0000000076fe0000 rcx=0000000000000052
rdx=0000080073d5cdb5 rsi=fffff880009a9ad0 rdi=fffff80003398aa0
rip=fffff80002f513ef rsp=fffff880009a9a38 rbp=fffff80003398aa0
 r8=00000000000000f7  r9=00000000770ec3a4 r10=000000000000007b
r11=00000000770ed8f0 r12=fffff80003387838 r13=0000000000000000
r14=0000000000000007 r15=0000000000000002
iopl=0         nv up ei pl nz na pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010203
nt!_report_gsfailure+0x5f:
fffff800`02f513ef 3a0c10          cmp     cl,byte ptr [rax+rdx] ds:002b:00000000`770f5855=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0xlx" referenced memory at "0xlx". The required data was not placed into memory because of an I/O error status of "0xlx".

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000770f5855

EXCEPTION_PARAMETER3:  00000000c0000428

IO_ERROR: (NTSTATUS) 0xc0000428 - <Unable to get error code text>

BUGCHECK_STR:  0x7E

EXCEPTION_STR:  0xc0000006_c0000428

FOLLOWUP_IP: 
+1a7952f009adfdc
00000000`770f5855 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0x7E_VRF_IMAGE_hardware_disk

BUCKET_ID:  X64_0x7E_VRF_IMAGE_hardware_disk

Followup: MachineOwner

Since I am still learning about Dump files, I wonder about things such as drivers that have been unloaded. The one below seems to show up and appears to be from Conexant:

Unloaded modules:
fffff880`03aff000 fffff880`03b6f000 CAXHWBS2.sys

Captain is right about the rdyboost indication, but that is a Microsoft system file so perhaps something else if at the root of the problem.

MODULE_NAME: rdyboost
IMAGE_NAME: rdyboost.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc48a
FAILURE_BUCKET_ID: X64_0xD0_VRF_rdyboost!SmdMdlAllocate+31
BUCKET_ID: X64_0xD0_VRF_rdyboost!SmdMdlAllocate+31

I have gotten Verifier to give me a blue screen on my 32 bit system for a Microsoft driver. SP1 seems to have fixed it since that no longer happens. But basically, Verifier might show blue screens on something that would not otherwise cause problems, even though the driver might be deficient. So you might disable the verifier, whenever you are ready, to see if the blue screens continue.

Thanks again for the responses.

Captain: I do not have any external drives (unless you count my Archos 5, which has a 160 gb hd on it...hmmm, that's disconnected now) and I went to Western Digital's website for their Diagnostics program. I was able to use Speccy to get the model of my HD, so I got the correct version of the Diagnostics for it. Upon running the program, it was unable to tell me the hard drives serial number.

I ran a "quick test" and it came back with no errors; however, upon running what I think was called the "Full Test" it was not so error free. The test itself ran fine, and ended with this screen.



I then clicked repair (seeing as I already have everything backed up) and got this:




So can we now say for sure it is a hard drive error? I can admit that I may be to blame. A few months ago either the hard drive or the fan started getting loud (like a playing card in a bike wheel kind of noise) so I would give 'er a slap and it would quiet it down. This never resulted in a immediate blue screen, but I can see how that would cause problems.

Also, let me ask if "writing zeros" would help at all.


Thanks.

As for Salt Grass: I had blue screens before enabling, during, and after using Driver Verifier.


I can attach the dumps I've been getting, if more research is needed.

Do I have the green light to buy a new Hard Drive? I was thinking about getting either a velocoraptor drive from WD or a SSD as my OS Drive, and a 2tb WD drive for data. But if the Hard Drive is not the problem, I will put the money elsewhere.

Run the drive test again and see if giving errors about bad sectors.

Originally Posted by Captain Jack

Run the drive test again and see if giving errors about bad sectors.

I ran an HP complete hardware test from a CD that came with my computer. It's self-booting so I didn't need to load to Windows (Which is become increasingly difficult to do). RAM, CPU, and GPU all reported back with-out errors, but once again errors popped up in the hard drive department. I took a picture on my phone, but I'll just type what it said:

Disk 0 Smart Self-Test Short.............
The read element failed
Model: WDC WD5000AAKS-65YGA0 / SN: WD-WCAS82913404 / Rev:12.0
Test ID = HD&12
Error Code: HD521-2
Disc 0 Smart Self-Test Short FAILED

EDIT: Forgot to add that I don't want to run the Western Digital Diagnostics if I don't have too, it's nearly impossible to boot now, at least 30 tries if ever to get in.

Thanks for the reply!

Yup .. That's a green light, backup your data and replace your HDD as soon as you can.

Thanks for all your help mate! You've been a huge help. Congrats on the 700 posts btw, anything I can do that will increase your profile REP or whatever this forum uses?

Thanks Mate We don't use REP system in this forum. You kind words is are more than enough.