Bsod w7 please help!!!

https://www.sevenforums.com/crashes-d...dom-bsods.html

Why so many posts?

This will just delay our being able to help.

Try removing any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8000fa1bb0, ffff, 0}

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

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880031858d8, fffff88003185140, fffff880014fb72f}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+26f )

Followup: MachineOwner

-----------------------------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff781c0000000, 897b, 4897cfffffffe}

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

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

The following driver is out of date and should be updated..

Code:

fffff880`0514b000 fffff880`05187880   mcdbus   mcdbus.sys   Tue Feb 24 05:34:07 2009 (49A3CD1F) ... MagicISO ... MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor

These appear to be the same files as before... please empty your minidump folder, and upload the new files as they are generated...

Your latest .dmp file shows Rtkvhd64.sys (Realtek High Definition Audio Function Driver) as the probable cause for this crash.. Download and install the latest driver available for your system at Realtek

Code:

....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff9800e4a6d60, 0, fffff88006d617ea, 0}

Unable to load image \SystemRoot\system32\drivers\RTKVHD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys

Could not read faulting driver name
Probably caused by : RTKVHD64.sys ( RTKVHD64+d97ea )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff9800e4a6d60, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff88006d617ea, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb90e0
 fffff9800e4a6d60 

FAULTING_IP: 
RTKVHD64+d97ea
fffff880`06d617ea 8b4630          mov     eax,dword ptr [rsi+30h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD5

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002b262b0 -- (.trap 0xfffff88002b262b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88002b264d8
rdx=fffff88002b26440 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006d617ea rsp=fffff88002b26440 rbp=0000000000000002
 r8=0000000000000000  r9=fffff88006d617ea r10=0000000000000000
r11=fffff880009e8180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
RTKVHD64+0xd97ea:
fffff880`06d617ea 8b4630          mov     eax,dword ptr [rsi+30h] ds:8180:00000000`00000030=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d01f14 to fffff80002c81740

STACK_TEXT:  
fffff880`02b26148 fffff800`02d01f14 : 00000000`00000050 fffff980`0e4a6d60 00000000`00000000 fffff880`02b262b0 : nt!KeBugCheckEx
fffff880`02b26150 fffff800`02c7f82e : 00000000`00000000 fffff8a0`019e8116 fffffa80`053aa000 fffff800`02cb433f : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`02b262b0 fffff880`06d617ea : fffff880`02b264d8 00000000`00000000 fffff8a0`019e8116 fffffa80`068f4a90 : nt!KiPageFault+0x16e
fffff880`02b26440 fffff880`02b264d8 : 00000000`00000000 fffff8a0`019e8116 fffffa80`068f4a90 00000000`00000000 : RTKVHD64+0xd97ea
fffff880`02b26448 00000000`00000000 : fffff8a0`019e8116 fffffa80`068f4a90 00000000`00000000 fffff800`00000000 : 0xfffff880`02b264d8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTKVHD64+d97ea
fffff880`06d617ea 8b4630          mov     eax,dword ptr [rsi+30h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  RTKVHD64+d97ea

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTKVHD64

IMAGE_NAME:  RTKVHD64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c500000

FAILURE_BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+d97ea

BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+d97ea

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

Tews is currently busy, so I will offer my suggestions. The first is we have to take it slow, I know this is impportant to you, as 4 postings show, but we have others that are just as anxious.

That being said. You submitted a large number of minidumps, I examined several and they all show drivers as a potential problem. The reports give clues, not the answer.
Take the driver test and then post the results.
I would back up first, since there is a small possiblity that this test can cause problems and loss of personal documents.


Enable the Driver Verifier
www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html