SoftK56 Modem Driver:
VSTCNXT6.SYS Thu Oct 16 06:22:22 2008
VSTDPV6.SYS Thu Oct 16 06:27:45 2008
VSTBS26.SYS Thu Oct 16 06:24:06 2008
[B][COLOR=#ff0000]RTCore64.sys Wed May 25 12:09:12 2005[/COLOR][/B] - Afterburner (Very important should update to remove it)
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff68000020fd8
Arg3: feb000004c8de867
Arg4: ffffc68000020fd8
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_403
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002f407d8 to fffff80002ece700
STACK_TEXT:
fffff880`04f3b7b8 fffff800`02f407d8 : 00000000`0000001a 00000000`00000403 fffff680`00020fd8 feb00000`4c8de867 : nt!KeBugCheckEx
fffff880`04f3b7c0 fffff800`02eff401 : 00000000`00000000 fffff680`00020ff8 fffffa80`01948630 00000000`00048093 : nt! ?? ::FNODOBFM::`string'+0x31eb2
fffff880`04f3b970 fffff800`02f1016a : 00000000`00000000 00000000`04f95fff fffffa80`00000000 fffffa80`00000000 : nt!MiDeleteVirtualAddresses+0x408
fffff880`04f3bb30 fffff800`02ecd953 : ffffffff`ffffffff 00000000`0145ebf8 00000000`0145ebf0 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`04f3bc20 00000000`7782f89a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0145ebb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7782f89a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+31eb2
fffff800`02f407d8 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+31eb2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd34
FAILURE_BUCKET_ID: X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31eb2
BUCKET_ID: X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31eb2
Followup: MachineOwner
---------
Unable to load image \SystemRoot\system32\DRIVERS\VKbms.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VKbms.sys
Note: The first SFC I ran was interrupted at around 50% by a "Memory Management" bluescreen. I was on FirefoxVerification 100% complete.
Windows Resource Protection did not find any integrity violations.
In my experience if this is a hardware fault it's invariably memory ?
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
Unloaded modules:
fffff880`03aff000 fffff880`03b6f000 CAXHWBS2.sys
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
Run the drive test again and see if giving errors about bad sectors.
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