Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after 10minutes While playing Crossfire!

19 Feb 2012   #21
devilron24

Windows 7 Professional SP1
 
 

Quote   Quote: Originally Posted by writhziden View Post
Does the advanced system care create a backup of the registry before cleaning it? I am not familiar with that program. If it made a backup, you could try restoring the registry settings.
I Don't Think the Advanced System Care Create Backup The Registry Before Cleaning it,,So What can i do nOW?


My System SpecsSystem Spec
.
19 Feb 2012   #22
writhziden

Windows 7 Home Premium 64 Bit
 
 

I am afraid the only recourse is to Repair Install Windows 7. Backup any important data just in case. The repair install should go smoothly and you more than likely will not lose any files, but it is still a good idea to do a backup. If you need any help with the repair install, let us know.
My System SpecsSystem Spec
21 Feb 2012   #23
devilron24

Windows 7 Professional SP1
 
 

Quote   Quote: Originally Posted by writhziden View Post
I am afraid the only recourse is to Repair Install Windows 7. Backup any important data just in case. The repair install should go smoothly and you more than likely will not lose any files, but it is still a good idea to do a backup. If you need any help with the repair install, let us know.
^^ Okay But I found my Nvidia Display Driver CD But it's old version so im just gonna update it i will let you know if i still have problems THANKS!!
My System SpecsSystem Spec
.

21 Feb 2012   #24
writhziden

Windows 7 Home Premium 64 Bit
 
 

Alright, best of luck!
My System SpecsSystem Spec
22 Feb 2012   #25
devilron24

Windows 7 Professional SP1
 
 
x

Quote   Quote: Originally Posted by writhziden View Post
Alright, best of luck!
Well i've updated my Nvidia GeForce Driver it's up to date now!! but i still have BSOD i think its realtek hd audio driver
Here are the Minidumps!
Attachment 199676
Here is another one
Attachment 199681
My System SpecsSystem Spec
22 Feb 2012   #26
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\devilron24\022212-17531-01\022212-17531-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x83410000 PsLoadedModuleList = 0x83550230 Debug session time: Wed Feb 22 05:21:05.000 2012 (GMT-7) System Uptime: 0 days 0:03:18.671 Loading Kernel Symbols ............................................................... ................................................................ ........... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 1, 834730bb} Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiGetDxgAdapterSafe+1c2 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 00000000, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 834730bb, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8356f828 Unable to read MiSystemVaType memory at 8354fd80 00000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KiSignalSynchronizationObjectEx+21 834730bb 8901 mov dword ptr [ecx],eax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: rundll32.exe TRAP_FRAME: 8eaa9b74 -- (.trap 0xffffffff8eaa9b74) ErrCode = 00000002 eax=00000000 ebx=86522ec4 ecx=00000000 edx=00000000 esi=00000000 edi=865a2ec4 eip=834730bb esp=8eaa9be8 ebp=8eaa9bfc iopl=0 nv up ei pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206 nt!KiSignalSynchronizationObjectEx+0x21: 834730bb 8901 mov dword ptr [ecx],eax ds:0023:00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 834730bb to 83448c3b STACK_TEXT: 8eaa9b74 834730bb badb0d00 00000000 836667a8 nt!KiTrap0E+0x2cf 8eaa9bfc 83472f97 83532d20 86522ebc 8eaa9c30 nt!KiSignalSynchronizationObjectEx+0x21 8eaa9c48 83472e76 00000000 00000001 00000000 nt!KeReleaseMutant+0x118 8eaa9c60 921f61c3 86522ebc 00000000 8eaa9cd4 nt!KeReleaseMutex+0x14 8eaa9c88 921f5b6a 8704cbc8 8eaa9cb4 97e8b858 dxgkrnl!DpiGetDxgAdapterSafe+0x1c2 8eaa9cb8 97cc341d 8eaa9cd4 19432d48 0069f7d4 dxgkrnl!DxgkOpenAdapter+0x7c 8eaa9d28 8344585a 0069f7d4 00000000 77c17094 win32k!NtGdiDdDDIOpenAdapterFromHdc+0x11c 8eaa9d28 77c17094 0069f7d4 00000000 77c17094 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 00000000 00000000 00000000 00000000 00000000 0x77c17094 STACK_COMMAND: kb FOLLOWUP_IP: dxgkrnl!DpiGetDxgAdapterSafe+1c2 921f61c3 8b1b mov ebx,dword ptr [ebx] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: dxgkrnl!DpiGetDxgAdapterSafe+1c2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78ffe FAILURE_BUCKET_ID: 0xA_dxgkrnl!DpiGetDxgAdapterSafe+1c2 BUCKET_ID: 0xA_dxgkrnl!DpiGetDxgAdapterSafe+1c2 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\devilron24\Minidump\022212-13984-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x83447000 PsLoadedModuleList = 0x83587230 Debug session time: Wed Feb 22 04:46:09.082 2012 (GMT-7) System Uptime: 0 days 0:03:15.753 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list .... Unable to load image \SystemRoot\system32\drivers\RTKVHDA.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for RTKVHDA.sys *** ERROR: Module load completed but symbols could not be loaded for RTKVHDA.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 97f47f90, 9c92549c, 0} Probably caused by : RTKVHDA.sys ( RTKVHDA+31cf90 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) 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: c0000005, The exception code that was not handled Arg2: 97f47f90, The address that the exception occurred at Arg3: 9c92549c, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: RTKVHDA+31cf90 97f47f90 8a87d2000000 mov al,byte ptr [edi+0D2h] TRAP_FRAME: 9c92549c -- (.trap 0xffffffff9c92549c) ErrCode = 00000000 eax=86cc5ee8 ebx=86cb7560 ecx=97e73630 edx=9c9254dc esi=86bbd128 edi=00000000 eip=97f47f90 esp=9c925510 ebp=9c92552c iopl=0 nv up ei ng nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282 RTKVHDA+0x31cf90: 97f47f90 8a87d2000000 mov al,byte ptr [edi+0D2h] ds:0023:000000d2=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: RtHDVCpl.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 97f43943 to 97f47f90 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 9c92552c 97f43943 86cc5ee8 00000000 86cb73f8 RTKVHDA+0x31cf90 9c925554 97f49563 86cb73f8 86cb7560 86cb73f8 RTKVHDA+0x318943 9c925594 97f0f14c 0001003e 86cbc008 87543dd8 RTKVHDA+0x31e563 9c9255fc 97ef0e02 86cb73f8 00000004 00000000 RTKVHDA+0x2e414c 9c92584c 97ef14b1 87560220 86d00758 856525d8 RTKVHDA+0x2c5e02 9c925a74 8fe655a2 87560220 87543de0 856efdf8 RTKVHDA+0x2c64b1 9c925a8c 8fe65438 856efdf8 856525d8 9502aa28 portcls!PcDispatchProperty+0x146 9c925ab4 8fdcd135 00000008 87543de0 87543dd8 portcls!PropertyItemPropertyHandler+0x2b 9c925b04 8fdd6183 856efdf8 00000015 9502aa28 ks!KspPropertyHandler+0x67c 9c925b28 8fe652e5 856efdf8 00000017 9502aa00 ks!KsPropertyHandler+0x19 9c925b40 8fe75784 006efdf8 00000017 9502aa00 portcls!PcHandlePropertyWithTable+0x49 9c925b88 8fe65060 856525c0 86c3ee08 856efdf8 portcls!CPortFilterWaveRT::DeviceIoControl+0xcf 9c925ba8 8fdcc48f 86c3eec0 856efdf8 9c925bd0 portcls!DispatchDeviceIoControl+0x5b 9c925bb8 8fe6b001 86c3ee08 856efdf8 856efe8c ks!KsDispatchIrp+0xb0 9c925bd0 8fe6bcc8 86c3ee08 856efdf8 9c925bfc portcls!KsoDispatchIrp+0x43 9c925be0 97eff00f 86c3ee08 856efdf8 877e3aa8 portcls!PcDispatchIrp+0x2d 9c925bfc 83476012 86c3ee08 c0000001 856efdf8 RTKVHDA+0x2d400f 9c925c14 8364ba5d 877e3aa8 856efdf8 856efe8c nt!IofCallDriver+0x63 9c925c34 8364de50 86c3ee08 877e3aa8 00000000 nt!IopSynchronousServiceTail+0x1f8 9c925cd0 83654dff 86c3ee08 856efdf8 00000000 nt!IopXxxControlFile+0x6aa 9c925d04 8347c85a 000003c4 00000000 00000000 nt!NtDeviceIoControlFile+0x2a 9c925d04 77a47094 000003c4 00000000 00000000 nt!KiFastCallEntry+0x12a 0012fa88 00000000 00000000 00000000 00000000 0x77a47094 STACK_COMMAND: kb FOLLOWUP_IP: RTKVHDA+31cf90 97f47f90 8a87d2000000 mov al,byte ptr [edi+0D2h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: RTKVHDA+31cf90 FOLLOWUP_NAME: MachineOwner MODULE_NAME: RTKVHDA IMAGE_NAME: RTKVHDA.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ee727b3 FAILURE_BUCKET_ID: 0x8E_RTKVHDA+31cf90 BUCKET_ID: 0x8E_RTKVHDA+31cf90 Followup: MachineOwner ---------
  3. Loading Dump File [D:\Kingston\BSODDmpFiles\devilron24\Minidump\022212-13078-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x83448000 PsLoadedModuleList = 0x83588230 Debug session time: Wed Feb 22 04:42:32.552 2012 (GMT-7) System Uptime: 0 days 0:52:49.208 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list ....... Unable to load image \SystemRoot\system32\drivers\RTKVHDA.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for RTKVHDA.sys *** ERROR: Module load completed but symbols could not be loaded for RTKVHDA.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 9432df90, 9f48341c, 0} *** WARNING: Unable to verify timestamp for XDva392.sys *** ERROR: Module load completed but symbols could not be loaded for XDva392.sys Probably caused by : RTKVHDA.sys ( RTKVHDA+31cf90 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) 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: c0000005, The exception code that was not handled Arg2: 9432df90, The address that the exception occurred at Arg3: 9f48341c, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: RTKVHDA+31cf90 9432df90 8a87d2000000 mov al,byte ptr [edi+0D2h] TRAP_FRAME: 9f48341c -- (.trap 0xffffffff9f48341c) ErrCode = 00000000 eax=86c9f0c8 ebx=86c9b400 ecx=94259630 edx=9f48345c esi=86b87128 edi=00000000 eip=9432df90 esp=9f483490 ebp=9f4834ac iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 RTKVHDA+0x31cf90: 9432df90 8a87d2000000 mov al,byte ptr [edi+0D2h] ds:0023:000000d2=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: RtHDVCpl.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 94329943 to 9432df90 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 9f4834ac 94329943 86c9f0c8 00000000 86c99498 RTKVHDA+0x31cf90 9f4834d4 9432f563 86c99498 86c9b400 86c99498 RTKVHDA+0x318943 9f483514 942f514c 0001003e 86c7e008 877cae60 RTKVHDA+0x31e563 9f48357c 942d6e02 86c99498 00000004 00000000 RTKVHDA+0x2e414c 9f4837cc 942d74b1 87786718 86cae2c8 86f0e698 RTKVHDA+0x2c5e02 9f4839f4 943e05a2 87786718 877cae68 87736480 RTKVHDA+0x2c64b1 9f483a0c 943e0438 87736480 86f0e698 948b5260 portcls!PcDispatchProperty+0x146 9f483a34 9131d135 00000008 877cae68 877cae60 portcls!PropertyItemPropertyHandler+0x2b 9f483a84 91326183 87736480 00000015 948b5260 ks!KspPropertyHandler+0x67c 9f483aa8 943e02e5 87736480 00000017 948b5238 ks!KsPropertyHandler+0x19 9f483ac0 943f0784 00736480 00000017 948b5238 portcls!PcHandlePropertyWithTable+0x49 9f483b08 943e0060 86f0e680 86c52d78 87736480 portcls!CPortFilterWaveRT::DeviceIoControl+0xcf 9f483b28 9131c48f 86c52e30 87736480 9f483b50 portcls!DispatchDeviceIoControl+0x5b 9f483b38 943e6001 86c52d78 87736480 87736514 ks!KsDispatchIrp+0xb0 9f483b50 943e6cc8 86c52d78 87736480 9f483b7c portcls!KsoDispatchIrp+0x43 9f483b60 942e500f 86c52d78 87736480 87abdcb8 portcls!PcDispatchIrp+0x2d 9f483b7c 83477012 86c52d78 c0000001 87736480 RTKVHDA+0x2d400f 9f483b94 8364ca5d 87abdcb8 87736480 87736514 nt!IofCallDriver+0x63 9f483bb4 8364ee50 86c52d78 87abdcb8 00000000 nt!IopSynchronousServiceTail+0x1f8 9f483c50 83655dff 86c52d78 87736480 00000000 nt!IopXxxControlFile+0x6aa 9f483c84 8c1a5fd0 000003f0 00000000 00000000 nt!NtDeviceIoControlFile+0x2a 9f483d04 8347d85a 000003f0 00000000 00000000 XDva392+0xfd0 9f483d04 77767094 000003f0 00000000 00000000 nt!KiFastCallEntry+0x12a 0012fa88 00000000 00000000 00000000 00000000 0x77767094 STACK_COMMAND: kb FOLLOWUP_IP: RTKVHDA+31cf90 9432df90 8a87d2000000 mov al,byte ptr [edi+0D2h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: RTKVHDA+31cf90 FOLLOWUP_NAME: MachineOwner MODULE_NAME: RTKVHDA IMAGE_NAME: RTKVHDA.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ee727b3 FAILURE_BUCKET_ID: 0x8E_RTKVHDA+31cf90 BUCKET_ID: 0x8E_RTKVHDA+31cf90 Followup: MachineOwner ---------
  1. Points to DirectX/graphics card/graphics card driver.
  2. Points to your RTKVHDA.sys Realtek HD Audio Codec Driver.
  3. MALWARE DETECTED!!!!!

Update your nVidia driver; it is outdated and pre-Windows 7. Refer to Graphics Driver - GeForce 295.73 Driver - GeForce for the drivers.

Update your Realtek drivers from Realtek PC Audio Codecs.

XDVA392.sys is malware. Scan for viruses with a full scan using the free version (do not start the trial) of Malwarebytes : Free anti-malware, anti-virus and spyware removal download and see the Good and Free system security combination. for better security steps and scanning tools.
My System SpecsSystem Spec
24 Feb 2012   #27
devilron24

Windows 7 Professional SP1
 
 

Quote   Quote: Originally Posted by writhziden View Post
Code:
  1. Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\devilron24\022212-17531-01\022212-17531-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x83410000 PsLoadedModuleList = 0x83550230 Debug session time: Wed Feb 22 05:21:05.000 2012 (GMT-7) System Uptime: 0 days 0:03:18.671 Loading Kernel Symbols ............................................................... ................................................................ ........... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 1, 834730bb} Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiGetDxgAdapterSafe+1c2 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 00000000, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 834730bb, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8356f828 Unable to read MiSystemVaType memory at 8354fd80 00000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KiSignalSynchronizationObjectEx+21 834730bb 8901 mov dword ptr [ecx],eax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: rundll32.exe TRAP_FRAME: 8eaa9b74 -- (.trap 0xffffffff8eaa9b74) ErrCode = 00000002 eax=00000000 ebx=86522ec4 ecx=00000000 edx=00000000 esi=00000000 edi=865a2ec4 eip=834730bb esp=8eaa9be8 ebp=8eaa9bfc iopl=0 nv up ei pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206 nt!KiSignalSynchronizationObjectEx+0x21: 834730bb 8901 mov dword ptr [ecx],eax ds:0023:00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 834730bb to 83448c3b STACK_TEXT: 8eaa9b74 834730bb badb0d00 00000000 836667a8 nt!KiTrap0E+0x2cf 8eaa9bfc 83472f97 83532d20 86522ebc 8eaa9c30 nt!KiSignalSynchronizationObjectEx+0x21 8eaa9c48 83472e76 00000000 00000001 00000000 nt!KeReleaseMutant+0x118 8eaa9c60 921f61c3 86522ebc 00000000 8eaa9cd4 nt!KeReleaseMutex+0x14 8eaa9c88 921f5b6a 8704cbc8 8eaa9cb4 97e8b858 dxgkrnl!DpiGetDxgAdapterSafe+0x1c2 8eaa9cb8 97cc341d 8eaa9cd4 19432d48 0069f7d4 dxgkrnl!DxgkOpenAdapter+0x7c 8eaa9d28 8344585a 0069f7d4 00000000 77c17094 win32k!NtGdiDdDDIOpenAdapterFromHdc+0x11c 8eaa9d28 77c17094 0069f7d4 00000000 77c17094 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 00000000 00000000 00000000 00000000 00000000 0x77c17094 STACK_COMMAND: kb FOLLOWUP_IP: dxgkrnl!DpiGetDxgAdapterSafe+1c2 921f61c3 8b1b mov ebx,dword ptr [ebx] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: dxgkrnl!DpiGetDxgAdapterSafe+1c2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78ffe FAILURE_BUCKET_ID: 0xA_dxgkrnl!DpiGetDxgAdapterSafe+1c2 BUCKET_ID: 0xA_dxgkrnl!DpiGetDxgAdapterSafe+1c2 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\devilron24\Minidump\022212-13984-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x83447000 PsLoadedModuleList = 0x83587230 Debug session time: Wed Feb 22 04:46:09.082 2012 (GMT-7) System Uptime: 0 days 0:03:15.753 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list .... Unable to load image \SystemRoot\system32\drivers\RTKVHDA.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for RTKVHDA.sys *** ERROR: Module load completed but symbols could not be loaded for RTKVHDA.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 97f47f90, 9c92549c, 0} Probably caused by : RTKVHDA.sys ( RTKVHDA+31cf90 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) 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: c0000005, The exception code that was not handled Arg2: 97f47f90, The address that the exception occurred at Arg3: 9c92549c, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: RTKVHDA+31cf90 97f47f90 8a87d2000000 mov al,byte ptr [edi+0D2h] TRAP_FRAME: 9c92549c -- (.trap 0xffffffff9c92549c) ErrCode = 00000000 eax=86cc5ee8 ebx=86cb7560 ecx=97e73630 edx=9c9254dc esi=86bbd128 edi=00000000 eip=97f47f90 esp=9c925510 ebp=9c92552c iopl=0 nv up ei ng nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282 RTKVHDA+0x31cf90: 97f47f90 8a87d2000000 mov al,byte ptr [edi+0D2h] ds:0023:000000d2=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: RtHDVCpl.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 97f43943 to 97f47f90 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 9c92552c 97f43943 86cc5ee8 00000000 86cb73f8 RTKVHDA+0x31cf90 9c925554 97f49563 86cb73f8 86cb7560 86cb73f8 RTKVHDA+0x318943 9c925594 97f0f14c 0001003e 86cbc008 87543dd8 RTKVHDA+0x31e563 9c9255fc 97ef0e02 86cb73f8 00000004 00000000 RTKVHDA+0x2e414c 9c92584c 97ef14b1 87560220 86d00758 856525d8 RTKVHDA+0x2c5e02 9c925a74 8fe655a2 87560220 87543de0 856efdf8 RTKVHDA+0x2c64b1 9c925a8c 8fe65438 856efdf8 856525d8 9502aa28 portcls!PcDispatchProperty+0x146 9c925ab4 8fdcd135 00000008 87543de0 87543dd8 portcls!PropertyItemPropertyHandler+0x2b 9c925b04 8fdd6183 856efdf8 00000015 9502aa28 ks!KspPropertyHandler+0x67c 9c925b28 8fe652e5 856efdf8 00000017 9502aa00 ks!KsPropertyHandler+0x19 9c925b40 8fe75784 006efdf8 00000017 9502aa00 portcls!PcHandlePropertyWithTable+0x49 9c925b88 8fe65060 856525c0 86c3ee08 856efdf8 portcls!CPortFilterWaveRT::DeviceIoControl+0xcf 9c925ba8 8fdcc48f 86c3eec0 856efdf8 9c925bd0 portcls!DispatchDeviceIoControl+0x5b 9c925bb8 8fe6b001 86c3ee08 856efdf8 856efe8c ks!KsDispatchIrp+0xb0 9c925bd0 8fe6bcc8 86c3ee08 856efdf8 9c925bfc portcls!KsoDispatchIrp+0x43 9c925be0 97eff00f 86c3ee08 856efdf8 877e3aa8 portcls!PcDispatchIrp+0x2d 9c925bfc 83476012 86c3ee08 c0000001 856efdf8 RTKVHDA+0x2d400f 9c925c14 8364ba5d 877e3aa8 856efdf8 856efe8c nt!IofCallDriver+0x63 9c925c34 8364de50 86c3ee08 877e3aa8 00000000 nt!IopSynchronousServiceTail+0x1f8 9c925cd0 83654dff 86c3ee08 856efdf8 00000000 nt!IopXxxControlFile+0x6aa 9c925d04 8347c85a 000003c4 00000000 00000000 nt!NtDeviceIoControlFile+0x2a 9c925d04 77a47094 000003c4 00000000 00000000 nt!KiFastCallEntry+0x12a 0012fa88 00000000 00000000 00000000 00000000 0x77a47094 STACK_COMMAND: kb FOLLOWUP_IP: RTKVHDA+31cf90 97f47f90 8a87d2000000 mov al,byte ptr [edi+0D2h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: RTKVHDA+31cf90 FOLLOWUP_NAME: MachineOwner MODULE_NAME: RTKVHDA IMAGE_NAME: RTKVHDA.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ee727b3 FAILURE_BUCKET_ID: 0x8E_RTKVHDA+31cf90 BUCKET_ID: 0x8E_RTKVHDA+31cf90 Followup: MachineOwner ---------
  3. Loading Dump File [D:\Kingston\BSODDmpFiles\devilron24\Minidump\022212-13078-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x83448000 PsLoadedModuleList = 0x83588230 Debug session time: Wed Feb 22 04:42:32.552 2012 (GMT-7) System Uptime: 0 days 0:52:49.208 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list ....... Unable to load image \SystemRoot\system32\drivers\RTKVHDA.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for RTKVHDA.sys *** ERROR: Module load completed but symbols could not be loaded for RTKVHDA.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 9432df90, 9f48341c, 0} *** WARNING: Unable to verify timestamp for XDva392.sys *** ERROR: Module load completed but symbols could not be loaded for XDva392.sys Probably caused by : RTKVHDA.sys ( RTKVHDA+31cf90 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) 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: c0000005, The exception code that was not handled Arg2: 9432df90, The address that the exception occurred at Arg3: 9f48341c, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: RTKVHDA+31cf90 9432df90 8a87d2000000 mov al,byte ptr [edi+0D2h] TRAP_FRAME: 9f48341c -- (.trap 0xffffffff9f48341c) ErrCode = 00000000 eax=86c9f0c8 ebx=86c9b400 ecx=94259630 edx=9f48345c esi=86b87128 edi=00000000 eip=9432df90 esp=9f483490 ebp=9f4834ac iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 RTKVHDA+0x31cf90: 9432df90 8a87d2000000 mov al,byte ptr [edi+0D2h] ds:0023:000000d2=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: RtHDVCpl.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 94329943 to 9432df90 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 9f4834ac 94329943 86c9f0c8 00000000 86c99498 RTKVHDA+0x31cf90 9f4834d4 9432f563 86c99498 86c9b400 86c99498 RTKVHDA+0x318943 9f483514 942f514c 0001003e 86c7e008 877cae60 RTKVHDA+0x31e563 9f48357c 942d6e02 86c99498 00000004 00000000 RTKVHDA+0x2e414c 9f4837cc 942d74b1 87786718 86cae2c8 86f0e698 RTKVHDA+0x2c5e02 9f4839f4 943e05a2 87786718 877cae68 87736480 RTKVHDA+0x2c64b1 9f483a0c 943e0438 87736480 86f0e698 948b5260 portcls!PcDispatchProperty+0x146 9f483a34 9131d135 00000008 877cae68 877cae60 portcls!PropertyItemPropertyHandler+0x2b 9f483a84 91326183 87736480 00000015 948b5260 ks!KspPropertyHandler+0x67c 9f483aa8 943e02e5 87736480 00000017 948b5238 ks!KsPropertyHandler+0x19 9f483ac0 943f0784 00736480 00000017 948b5238 portcls!PcHandlePropertyWithTable+0x49 9f483b08 943e0060 86f0e680 86c52d78 87736480 portcls!CPortFilterWaveRT::DeviceIoControl+0xcf 9f483b28 9131c48f 86c52e30 87736480 9f483b50 portcls!DispatchDeviceIoControl+0x5b 9f483b38 943e6001 86c52d78 87736480 87736514 ks!KsDispatchIrp+0xb0 9f483b50 943e6cc8 86c52d78 87736480 9f483b7c portcls!KsoDispatchIrp+0x43 9f483b60 942e500f 86c52d78 87736480 87abdcb8 portcls!PcDispatchIrp+0x2d 9f483b7c 83477012 86c52d78 c0000001 87736480 RTKVHDA+0x2d400f 9f483b94 8364ca5d 87abdcb8 87736480 87736514 nt!IofCallDriver+0x63 9f483bb4 8364ee50 86c52d78 87abdcb8 00000000 nt!IopSynchronousServiceTail+0x1f8 9f483c50 83655dff 86c52d78 87736480 00000000 nt!IopXxxControlFile+0x6aa 9f483c84 8c1a5fd0 000003f0 00000000 00000000 nt!NtDeviceIoControlFile+0x2a 9f483d04 8347d85a 000003f0 00000000 00000000 XDva392+0xfd0 9f483d04 77767094 000003f0 00000000 00000000 nt!KiFastCallEntry+0x12a 0012fa88 00000000 00000000 00000000 00000000 0x77767094 STACK_COMMAND: kb FOLLOWUP_IP: RTKVHDA+31cf90 9432df90 8a87d2000000 mov al,byte ptr [edi+0D2h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: RTKVHDA+31cf90 FOLLOWUP_NAME: MachineOwner MODULE_NAME: RTKVHDA IMAGE_NAME: RTKVHDA.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ee727b3 FAILURE_BUCKET_ID: 0x8E_RTKVHDA+31cf90 BUCKET_ID: 0x8E_RTKVHDA+31cf90 Followup: MachineOwner ---------
  1. Points to DirectX/graphics card/graphics card driver.
  2. Points to your RTKVHDA.sys Realtek HD Audio Codec Driver.
  3. MALWARE DETECTED!!!!!

Update your nVidia driver; it is outdated and pre-Windows 7. Refer to Graphics Driver - GeForce 295.73 Driver - GeForce for the drivers.

Update your Realtek drivers from Realtek PC Audio Codecs.

XDVA392.sys is malware. Scan for viruses with a full scan using the free version (do not start the trial) of Malwarebytes : Free anti-malware, anti-virus and spyware removal download and see the Good and Free system security combination. for better security steps and scanning tools.
Downloaded and Installed Malwarebytes Anti-Malware,SUPERAntiSpyware Professional And Scanned my PC and Cleaned it And Updated my Drivers Realtek HD Audio and Nvidia GeForce 8400GS into 295.73 Version for Windows 7 Ultimate 32bit but another Error or BSOD occured after that!! here's the dump!!
Attachment 199996
My System SpecsSystem Spec
24 Feb 2012   #28
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\devilron24\Windows_NT6_BSOD_jcgriff2\022412-16781-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x8340a000 PsLoadedModuleList = 0x8354a230 Debug session time: Fri Feb 24 05:04:07.706 2012 (UTC - 7:00) System Uptime: 0 days 0:01:12.377 Loading Kernel Symbols ............................................................... ................................................................ .............. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 1, 8345e83f} Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+109 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 00000000, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 8345e83f, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 83569828 Unable to read MiSystemVaType memory at 83549d80 00000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KeWaitForSingleObject+373 8345e83f 8939 mov dword ptr [ecx],edi CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: 9c092f7c -- (.trap 0xffffffff9c092f7c) ErrCode = 00000002 eax=861fc648 ebx=861fc640 ecx=00000000 edx=00000000 esi=878e91d8 edi=878e9298 eip=8345e83f esp=9c092ff0 ebp=9c093050 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!KeWaitForSingleObject+0x373: 8345e83f 8939 mov dword ptr [ecx],edi ds:0023:00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 8345e83f to 83442c3b STACK_TEXT: 9c092f7c 8345e83f badb0d00 00000000 a3c54970 nt!KiTrap0E+0x2cf 9c093050 834bacc0 861fc640 00000022 00000000 nt!KeWaitForSingleObject+0x373 9c093078 834a3e64 861fc634 00000000 89c4b3e9 nt!KiAcquireFastMutex+0x56 9c093084 89c4b3e9 879a36b8 879a3638 00000000 nt!ExAcquireFastMutex+0x1e 9c09309c 89c47e33 00000034 87a6cf80 9c0930d8 fltmgr!TargetedIOCtrlAttachAsFoCtx+0xbb 9c0930fc 89c49033 00000000 00000000 879a3638 fltmgr!FltpNormalizeNameFromCache+0x135 9c093128 89c49df4 019a3638 00000000 879a3638 fltmgr!FltpExpandShortNames+0x2b5 9c093144 89c4a505 879a0000 00000000 8790295c fltmgr!FltpGetNormalizedFileNameWorker+0xae 9c09315c 89c47765 879a3638 00000000 879a3638 fltmgr!FltpGetNormalizedFileName+0x19 9c093174 89c31b21 879a3638 00000000 00000000 fltmgr!FltpCreateFileNameInformation+0x81 9c0931a4 89c31fa3 87702f0c 00000000 9c09323c fltmgr!FltpGetFileNameInformation+0x321 9c0931cc 89c64c87 006d0068 00000401 9c093200 fltmgr!FltGetFileNameInformation+0x12b 9c09321c 89c64edd 876d0068 9c09323c 000013ac fileinfo!FIStreamGetInfo+0x109 9c093258 89c2b324 876d0068 9c09327c 47918016 fileinfo!FIPostCreateCallback+0x171 9c0932c0 89c2e512 006d0008 876d0008 1000000c fltmgr!FltpPerformPostCallbacks+0x24a 9c0932d4 89c2eb46 876d0008 87a6c938 9c093314 fltmgr!FltpProcessIoCompletion+0x10 9c0932e4 89c2f29c 86297ad8 87a6c938 876d0008 fltmgr!FltpPassThroughCompletion+0x98 9c093314 89c428c9 9c093334 00000000 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x33a 9c093360 83439012 86297ad8 862f8ae0 87a6b4a4 fltmgr!FltpCreate+0x2db 9c093378 8360cf03 bfdb53c7 9c093520 00000000 nt!IofCallDriver+0x63 9c093450 836100de 86260788 854ccd20 878e7d20 nt!IopParseDevice+0xed7 9c0934cc 8364eb23 00000000 9c093520 000002c0 nt!ObpLookupObjectName+0x4fa 9c093528 8360a4a4 9c09370c 854ccd20 89d1cc00 nt!ObOpenObjectByName+0x165 9c0935a4 836607a8 9c093728 80000000 9c09370c nt!IopCreateFile+0x673 9c0935ec 8343f85a 9c093728 80000000 9c09370c nt!NtOpenFile+0x2a 9c0935ec 8343dbc5 9c093728 80000000 9c09370c nt!KiFastCallEntry+0x12a 9c09367c 89916165 9c093728 80000000 9c09370c nt!ZwOpenFile+0x11 9c0936e4 89918523 9c093728 9c0937b0 a3b86b60 CI!CipMinCrypK_OpenFile+0x27 9c093730 8991a41b 9c093774 9c093780 9c093784 CI!I_MapAndSizeDataFile+0x4f 9c0937a8 8991a77e 9c093864 a3b86b30 00000000 CI!I_MapCatalog+0xfb 9c093884 8991a8c8 9c0938ac 9c09a9cb 9c093a98 CI!I_ReloadCatalogs+0x22e 9c0938d0 8991abfa 9c093ac4 00000000 00000001 CI!I_FindFileOrHeaderHashInCatalogs+0xcd 9c093900 8991708d 9c093ac4 00000001 00000000 CI!MinCrypK_FindPageHashesInCatalog+0x24 9c093960 89917cce 864f4570 9c093ac4 00008004 CI!CipGetPageHashesForFile+0xa9 9c093a68 89917ead 864f4570 9f040000 00001000 CI!CipValidatePageHash+0x1ac 9c093adc 835d30a3 864f4570 9f040000 00001000 CI!CiValidateImageHeader+0x14f 9c093af8 835d2f11 864f4570 9f040000 00001000 nt!SeValidateImageHeader+0x4d 9c093b74 8363f9cd 864f4570 87911e50 00000002 nt!MiValidateImageHeader+0x1a4 9c093c9c 8365d8ec 9c093cf0 00000007 00000000 nt!MmCreateSection+0x779 9c093d10 8343f85a 00125b8c 00000007 00000000 nt!NtCreateSection+0x16e 9c093d10 77517094 00125b8c 00000007 00000000 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 00125cac 00000000 00000000 00000000 00000000 0x77517094 STACK_COMMAND: kb FOLLOWUP_IP: fileinfo!FIStreamGetInfo+109 89c64c87 85c0 test eax,eax SYMBOL_STACK_INDEX: c SYMBOL_NAME: fileinfo!FIStreamGetInfo+109 FOLLOWUP_NAME: MachineOwner MODULE_NAME: fileinfo IMAGE_NAME: fileinfo.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18f FAILURE_BUCKET_ID: 0xA_fileinfo!FIStreamGetInfo+109 BUCKET_ID: 0xA_fileinfo!FIStreamGetInfo+109 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\devilron24\Windows_NT6_BSOD_jcgriff2\022412-16734-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x8344f000 PsLoadedModuleList = 0x8358f230 Debug session time: Fri Feb 24 05:01:50.913 2012 (UTC - 7:00) System Uptime: 0 days 0:04:16.584 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 89f02ddb, 9d0834fc, 0} Probably caused by : NETIO.SYS ( NETIO!CompareSublayers+11 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) 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: c0000005, The exception code that was not handled Arg2: 89f02ddb, The address that the exception occurred at Arg3: 9d0834fc, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: NETIO!CompareSublayers+11 89f02ddb 0fb74010 movzx eax,word ptr [eax+10h] TRAP_FRAME: 9d0834fc -- (.trap 0xffffffff9d0834fc) ErrCode = 00000000 eax=006f0072 ebx=85662ee0 ecx=855ea920 edx=8722e670 esi=859f05b8 edi=856628c4 eip=89f02ddb esp=9d083570 ebp=9d083570 iopl=0 nv up ei ng nz na pe cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287 NETIO!CompareSublayers+0x11: 89f02ddb 0fb74010 movzx eax,word ptr [eax+10h] ds:0023:006f0082=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 89f02d93 to 89f02ddb STACK_TEXT: 9d083570 89f02d93 859f05b8 8722e670 8566383c NETIO!CompareSublayers+0x11 9d083584 89f069c8 859f05b8 8722e670 9d0836b0 NETIO!WeightCompare+0x13 9d083594 89f0b921 856628c4 85662ee0 00000000 NETIO!WeightCompareEx+0x14 9d0836b0 89f06d6c 85660000 000012c0 00000004 NETIO!WFPQSort+0x121 9d0836d4 89f08a45 855e1b00 9d083740 9d083978 NETIO!SortMatchList+0x3e 9d0836f4 89f099e3 00000003 9d08380c 00000000 NETIO!FeEnumLayer+0xb8 9d083758 89f09e33 00000030 9d08380c 9d083950 NETIO!KfdGetLayerActionFromEnumTemplate+0x56 9d083778 8a062afe 00000030 9d08382c 9d08380c NETIO!KfdCheckAndCacheConnectBypass+0x26 9d083848 8a07981c 00000000 00005000 9d083950 tcpip!CheckConnectBypass+0xf7 9d0839ac 8a05fe84 00000030 862230a4 0000dafa tcpip!WfpAleAuthorizeConnect+0x20d 9d0839dc 8a064e0c 8a06016a 856396e0 855e2630 tcpip!InetInspectConnect+0x3c 9d083a30 8a07380e 856396e0 00000000 8563981c tcpip!TcpContinueCreateAndConnect+0x4dc 9d083a48 8a066a3d 856396e0 00000000 00000000 tcpip!TcpCreateAndConnectTcbInspectConnectRequestComplete+0xf8 9d083ab0 8a0697a9 8563981c 00000000 878fe8a0 tcpip!TcpCreateAndConnectTcbWorkQueueRoutine+0x4df 9d083b0c 89f8a6c9 86194f10 9d083b38 14ff7bdf tcpip!TcpCreateAndConnectTcb+0x82a 9d083bec 89f842bc 855c61b8 85d78328 9d083c14 afd!AfdConnect+0x825 9d083bfc 8347e012 85d78328 864fd320 864fd320 afd!AfdDispatchDeviceControl+0x3b 9d083c14 83653a5d 855c61b8 864fd320 864fd3fc nt!IofCallDriver+0x63 9d083c34 83655e50 85d78328 855c61b8 00000000 nt!IopSynchronousServiceTail+0x1f8 9d083cd0 8365cdff 85d78328 864fd320 00000000 nt!IopXxxControlFile+0x6aa 9d083d04 8348485a 000005cc 00000000 00000000 nt!NtDeviceIoControlFile+0x2a 9d083d04 76ec7094 000005cc 00000000 00000000 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 036ef4cc 00000000 00000000 00000000 00000000 0x76ec7094 STACK_COMMAND: kb FOLLOWUP_IP: NETIO!CompareSublayers+11 89f02ddb 0fb74010 movzx eax,word ptr [eax+10h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: NETIO!CompareSublayers+11 FOLLOWUP_NAME: MachineOwner MODULE_NAME: NETIO IMAGE_NAME: NETIO.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78963 FAILURE_BUCKET_ID: 0x8E_NETIO!CompareSublayers+11 BUCKET_ID: 0x8E_NETIO!CompareSublayers+11 Followup: MachineOwner ---------
  1. Appears to be hard disk related.
  2. Network related crash. Could still be disk related.
At this point, I would recommend going through the steps in HD Diagnostic to check your hard disk drive with the manufacturer's diagnostic utilities.



If no errors are found by diagnostics, repair install Windows 7.
My System SpecsSystem Spec
25 Feb 2012   #29
devilron24

Windows 7 Professional SP1
 
 

Quote   Quote: Originally Posted by writhziden View Post
Code:
  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\devilron24\Windows_NT6_BSOD_jcgriff2\022412-16781-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x8340a000 PsLoadedModuleList = 0x8354a230 Debug session time: Fri Feb 24 05:04:07.706 2012 (UTC - 7:00) System Uptime: 0 days 0:01:12.377 Loading Kernel Symbols ............................................................... ................................................................ .............. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 1, 8345e83f} Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+109 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 00000000, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 8345e83f, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 83569828 Unable to read MiSystemVaType memory at 83549d80 00000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KeWaitForSingleObject+373 8345e83f 8939 mov dword ptr [ecx],edi CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: 9c092f7c -- (.trap 0xffffffff9c092f7c) ErrCode = 00000002 eax=861fc648 ebx=861fc640 ecx=00000000 edx=00000000 esi=878e91d8 edi=878e9298 eip=8345e83f esp=9c092ff0 ebp=9c093050 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!KeWaitForSingleObject+0x373: 8345e83f 8939 mov dword ptr [ecx],edi ds:0023:00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 8345e83f to 83442c3b STACK_TEXT: 9c092f7c 8345e83f badb0d00 00000000 a3c54970 nt!KiTrap0E+0x2cf 9c093050 834bacc0 861fc640 00000022 00000000 nt!KeWaitForSingleObject+0x373 9c093078 834a3e64 861fc634 00000000 89c4b3e9 nt!KiAcquireFastMutex+0x56 9c093084 89c4b3e9 879a36b8 879a3638 00000000 nt!ExAcquireFastMutex+0x1e 9c09309c 89c47e33 00000034 87a6cf80 9c0930d8 fltmgr!TargetedIOCtrlAttachAsFoCtx+0xbb 9c0930fc 89c49033 00000000 00000000 879a3638 fltmgr!FltpNormalizeNameFromCache+0x135 9c093128 89c49df4 019a3638 00000000 879a3638 fltmgr!FltpExpandShortNames+0x2b5 9c093144 89c4a505 879a0000 00000000 8790295c fltmgr!FltpGetNormalizedFileNameWorker+0xae 9c09315c 89c47765 879a3638 00000000 879a3638 fltmgr!FltpGetNormalizedFileName+0x19 9c093174 89c31b21 879a3638 00000000 00000000 fltmgr!FltpCreateFileNameInformation+0x81 9c0931a4 89c31fa3 87702f0c 00000000 9c09323c fltmgr!FltpGetFileNameInformation+0x321 9c0931cc 89c64c87 006d0068 00000401 9c093200 fltmgr!FltGetFileNameInformation+0x12b 9c09321c 89c64edd 876d0068 9c09323c 000013ac fileinfo!FIStreamGetInfo+0x109 9c093258 89c2b324 876d0068 9c09327c 47918016 fileinfo!FIPostCreateCallback+0x171 9c0932c0 89c2e512 006d0008 876d0008 1000000c fltmgr!FltpPerformPostCallbacks+0x24a 9c0932d4 89c2eb46 876d0008 87a6c938 9c093314 fltmgr!FltpProcessIoCompletion+0x10 9c0932e4 89c2f29c 86297ad8 87a6c938 876d0008 fltmgr!FltpPassThroughCompletion+0x98 9c093314 89c428c9 9c093334 00000000 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x33a 9c093360 83439012 86297ad8 862f8ae0 87a6b4a4 fltmgr!FltpCreate+0x2db 9c093378 8360cf03 bfdb53c7 9c093520 00000000 nt!IofCallDriver+0x63 9c093450 836100de 86260788 854ccd20 878e7d20 nt!IopParseDevice+0xed7 9c0934cc 8364eb23 00000000 9c093520 000002c0 nt!ObpLookupObjectName+0x4fa 9c093528 8360a4a4 9c09370c 854ccd20 89d1cc00 nt!ObOpenObjectByName+0x165 9c0935a4 836607a8 9c093728 80000000 9c09370c nt!IopCreateFile+0x673 9c0935ec 8343f85a 9c093728 80000000 9c09370c nt!NtOpenFile+0x2a 9c0935ec 8343dbc5 9c093728 80000000 9c09370c nt!KiFastCallEntry+0x12a 9c09367c 89916165 9c093728 80000000 9c09370c nt!ZwOpenFile+0x11 9c0936e4 89918523 9c093728 9c0937b0 a3b86b60 CI!CipMinCrypK_OpenFile+0x27 9c093730 8991a41b 9c093774 9c093780 9c093784 CI!I_MapAndSizeDataFile+0x4f 9c0937a8 8991a77e 9c093864 a3b86b30 00000000 CI!I_MapCatalog+0xfb 9c093884 8991a8c8 9c0938ac 9c09a9cb 9c093a98 CI!I_ReloadCatalogs+0x22e 9c0938d0 8991abfa 9c093ac4 00000000 00000001 CI!I_FindFileOrHeaderHashInCatalogs+0xcd 9c093900 8991708d 9c093ac4 00000001 00000000 CI!MinCrypK_FindPageHashesInCatalog+0x24 9c093960 89917cce 864f4570 9c093ac4 00008004 CI!CipGetPageHashesForFile+0xa9 9c093a68 89917ead 864f4570 9f040000 00001000 CI!CipValidatePageHash+0x1ac 9c093adc 835d30a3 864f4570 9f040000 00001000 CI!CiValidateImageHeader+0x14f 9c093af8 835d2f11 864f4570 9f040000 00001000 nt!SeValidateImageHeader+0x4d 9c093b74 8363f9cd 864f4570 87911e50 00000002 nt!MiValidateImageHeader+0x1a4 9c093c9c 8365d8ec 9c093cf0 00000007 00000000 nt!MmCreateSection+0x779 9c093d10 8343f85a 00125b8c 00000007 00000000 nt!NtCreateSection+0x16e 9c093d10 77517094 00125b8c 00000007 00000000 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 00125cac 00000000 00000000 00000000 00000000 0x77517094 STACK_COMMAND: kb FOLLOWUP_IP: fileinfo!FIStreamGetInfo+109 89c64c87 85c0 test eax,eax SYMBOL_STACK_INDEX: c SYMBOL_NAME: fileinfo!FIStreamGetInfo+109 FOLLOWUP_NAME: MachineOwner MODULE_NAME: fileinfo IMAGE_NAME: fileinfo.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18f FAILURE_BUCKET_ID: 0xA_fileinfo!FIStreamGetInfo+109 BUCKET_ID: 0xA_fileinfo!FIStreamGetInfo+109 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\devilron24\Windows_NT6_BSOD_jcgriff2\022412-16734-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x8344f000 PsLoadedModuleList = 0x8358f230 Debug session time: Fri Feb 24 05:01:50.913 2012 (UTC - 7:00) System Uptime: 0 days 0:04:16.584 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 89f02ddb, 9d0834fc, 0} Probably caused by : NETIO.SYS ( NETIO!CompareSublayers+11 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) 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: c0000005, The exception code that was not handled Arg2: 89f02ddb, The address that the exception occurred at Arg3: 9d0834fc, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: NETIO!CompareSublayers+11 89f02ddb 0fb74010 movzx eax,word ptr [eax+10h] TRAP_FRAME: 9d0834fc -- (.trap 0xffffffff9d0834fc) ErrCode = 00000000 eax=006f0072 ebx=85662ee0 ecx=855ea920 edx=8722e670 esi=859f05b8 edi=856628c4 eip=89f02ddb esp=9d083570 ebp=9d083570 iopl=0 nv up ei ng nz na pe cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287 NETIO!CompareSublayers+0x11: 89f02ddb 0fb74010 movzx eax,word ptr [eax+10h] ds:0023:006f0082=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 89f02d93 to 89f02ddb STACK_TEXT: 9d083570 89f02d93 859f05b8 8722e670 8566383c NETIO!CompareSublayers+0x11 9d083584 89f069c8 859f05b8 8722e670 9d0836b0 NETIO!WeightCompare+0x13 9d083594 89f0b921 856628c4 85662ee0 00000000 NETIO!WeightCompareEx+0x14 9d0836b0 89f06d6c 85660000 000012c0 00000004 NETIO!WFPQSort+0x121 9d0836d4 89f08a45 855e1b00 9d083740 9d083978 NETIO!SortMatchList+0x3e 9d0836f4 89f099e3 00000003 9d08380c 00000000 NETIO!FeEnumLayer+0xb8 9d083758 89f09e33 00000030 9d08380c 9d083950 NETIO!KfdGetLayerActionFromEnumTemplate+0x56 9d083778 8a062afe 00000030 9d08382c 9d08380c NETIO!KfdCheckAndCacheConnectBypass+0x26 9d083848 8a07981c 00000000 00005000 9d083950 tcpip!CheckConnectBypass+0xf7 9d0839ac 8a05fe84 00000030 862230a4 0000dafa tcpip!WfpAleAuthorizeConnect+0x20d 9d0839dc 8a064e0c 8a06016a 856396e0 855e2630 tcpip!InetInspectConnect+0x3c 9d083a30 8a07380e 856396e0 00000000 8563981c tcpip!TcpContinueCreateAndConnect+0x4dc 9d083a48 8a066a3d 856396e0 00000000 00000000 tcpip!TcpCreateAndConnectTcbInspectConnectRequestComplete+0xf8 9d083ab0 8a0697a9 8563981c 00000000 878fe8a0 tcpip!TcpCreateAndConnectTcbWorkQueueRoutine+0x4df 9d083b0c 89f8a6c9 86194f10 9d083b38 14ff7bdf tcpip!TcpCreateAndConnectTcb+0x82a 9d083bec 89f842bc 855c61b8 85d78328 9d083c14 afd!AfdConnect+0x825 9d083bfc 8347e012 85d78328 864fd320 864fd320 afd!AfdDispatchDeviceControl+0x3b 9d083c14 83653a5d 855c61b8 864fd320 864fd3fc nt!IofCallDriver+0x63 9d083c34 83655e50 85d78328 855c61b8 00000000 nt!IopSynchronousServiceTail+0x1f8 9d083cd0 8365cdff 85d78328 864fd320 00000000 nt!IopXxxControlFile+0x6aa 9d083d04 8348485a 000005cc 00000000 00000000 nt!NtDeviceIoControlFile+0x2a 9d083d04 76ec7094 000005cc 00000000 00000000 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 036ef4cc 00000000 00000000 00000000 00000000 0x76ec7094 STACK_COMMAND: kb FOLLOWUP_IP: NETIO!CompareSublayers+11 89f02ddb 0fb74010 movzx eax,word ptr [eax+10h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: NETIO!CompareSublayers+11 FOLLOWUP_NAME: MachineOwner MODULE_NAME: NETIO IMAGE_NAME: NETIO.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78963 FAILURE_BUCKET_ID: 0x8E_NETIO!CompareSublayers+11 BUCKET_ID: 0x8E_NETIO!CompareSublayers+11 Followup: MachineOwner ---------
  1. Appears to be hard disk related.
  2. Network related crash. Could still be disk related.
At this point, I would recommend going through the steps in HD Diagnostic to check your hard disk drive with the manufacturer's diagnostic utilities.



If no errors are found by diagnostics, repair install Windows 7.
well i have Western Data LifeGuard Diagnostics DLGDIAG for Windows
and here is the result

Quote:
Test Option: QUICK TEST
Model Number: WDC WD1600AAJS-00B4A0
Unit Serial Number: WD-WCAT1D441284
Firmware Number: 01.03A01
Capacity: 160.04 GB
SMART Status: PASS
Test Result: FAIL
Test Error Code: 06-Quick Test on drive 1 did not complete! Status code = 07 (Failed read test element), Failure Checkpoint = 97 (Unknown Test) SMART self-test did not complete on drive 1!
Test Time: 12:53:59, February 25, 2012

Test Option: EXTENDED TEST
Model Number: WDC WD1600AAJS-00B4A0
Unit Serial Number: WD-WCAT1D441284
Firmware Number: 01.03A01
Capacity: 160.04 GB
SMART Status: PASS
Test Result: FAIL
Test Error Code: 08-Error was detected while repairing bad sectors.
Test Time: 13:29:52, February 25, 2012


Test Option: QUICK TEST
Model Number: WDC WD1600AAJS-00B4A0
Unit Serial Number: WD-WCAT1D441284
Firmware Number: 01.03A01
Capacity: 160.04 GB
SMART Status: PASS
Test Result: FAIL
Test Error Code: 06-Quick Test on drive 1 did not complete! Status code = 07 (Failed read test element), Failure Checkpoint = 97 (Unknown Test) SMART self-test did not complete on drive 1!
Test Time: 13:31:32, February 25, 2012
My System SpecsSystem Spec
25 Feb 2012   #30
writhziden

Windows 7 Home Premium 64 Bit
 
 

You should also try the DOS utility. Sometimes the Windows utility fails and the DOS utility is able to complete. Sorry to see the fails, though. That may be a bad sign.
My System SpecsSystem Spec
Reply

 BSOD after 10minutes While playing Crossfire!




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Black Screen every 10minutes after using HDMI
Hi So i today i switched from VGA to HDMI now everything is set fine the sceen looks way better than what i had on VGA but every 5min or 10 the screen goes black for 1-2 seconds then returns any ideas ? thanks
Hardware & Devices
FRAPS lag spikes while playing crossfire
I am trying to record some crossfire game play for a clan video but while recording i am getting huge fps drops. I sit around 200+ and while recording sometimes drop to 17 whats going on and what settings should i use to get it optimal while still looking good. I am running a GTX 660 TI SC 3GB with...
Gaming
BSOD 0x0000000A while playing crossfire
While playing Crossfire i got a BSOD in the middle of a game
BSOD Help and Support
Graphic Card radeon hd 5470 playing Crossfire , problem with scaling
Hi there. My problem is.. i play Crossfire game in full screen (dextop and in game) and after one hour my fps is decrease 100+ normal to 50-14 and after my dextop resolution 1366x768 is go on resolution 640x480 and scaling "Full Screen" is changing. So.. i have black borders but not on game ,...
Graphic Cards
BSOD after 10minutes
Hi. My brand new computer had a BSOD error about 5 minutes after I started up Windows. I was running a game at the time and the computer restarted with the BSOD error. Then about 15 minutes later it happened again just on the desktop. I have Windows 7. I attached the .dmp file.
BSOD Help and Support
Playing crossfire
when i start up crossfire , it doesnt go full screen , instead it just goes into like a small window on the TOP LEFT Corner , i can still be able to play , but i want it to be full screen to be able to see the surroundings clearly? Untitled on Flickr - Photo Sharing! Looks like that
Gaming


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:44.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App