New build BSOD problem!!

[wilhemina]

Is Windows 7 . . .
- x86 (32-bit) or x64 ?: : x64
- the original installed OS on the system? : yes
- an OEM or full retail version? : Full retail
- What is the age of system (hardware)? : about 1 month
- What is the age of OS installation (have you re-installed the OS?) : about a month (YES)

Hello all. I've had this desktop build for a month and have been dealing with random bsods with a view to eliminating them at their source. So far having run the elementary checks numerous times (memtest, scandisk /SCANNOW, chkdsk /f/r etc), uninstalling avg, daemon tools gigabyte software and stuff and updating all my drivers (tis been a long dreary road). But it would seem now that the crashes have finally narrowed down to the elusive NTFS.SYS BUGCHECK code. Well I have attached the dump files that tell my tales of the journey. I really feel I am finally at the source of the problem . (As you can probably tell I am trying to go as far as possible without RMAing anything.lol). Well that's the story. I leave it in your capable hands. (Also I hope you can point out anything I may have missed. Either way it's all in the MinidumpDocuments.zip.

 

[wilhemina]

Recent update. Just had another bsod with new minidump added. So much for the 'narrowing down'. Now I got a system service exception. I guess something's gone bad but I dunno what it is. I'm also experiencing incessant IE and google chrome crashes (probably related but just thought I'd throw it out there). Anyway any help would be appreciated.

 

[usasma]

No memory dumps in the uploaded information. Please do the following:

Upload Dump Files:
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service . I recommend Windows Live SkyDrive - http://skydrive.live.com or another free, file-hosting service. Then post the link to it in your topic so that we can download it.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump

There's at least 2 STOP 0x24 and a STOP 0x27 in the MSINFO32 report. Please start with these free, bootable diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

 

[wilhemina]

Oh my bad. Here's the link to my skydrive:

My Documents - Windows Live

 

[Jonathan_King]

In the future, please follow these directions: http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

I suspect AVG is causing the issue. Please remove it with this tool: http://download.avg.com/filedir/util/avg_arv_sup_____.dir/avgremoverx64.exe

Be sure to use Microsoft Security Essentials instead.

Do a disk check. Open a command prompt and enter chkdsk /r.

If the BSODs continue, please enable driver verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 22 00:33:04.284 2010 (UTC - 4:00)
System Uptime: 0 days 5:06:49.564
BugCheck 3B, {c0000005, fffff80002faf0bf, fffff88003868ef0, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  lsass.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 21 09:43:01.745 2010 (UTC - 4:00)
System Uptime: 1 days 5:11:04.415
BugCheck 24, {1904fb, fffff8800a382d98, fffff8800a382600, fffff80002ebfff3}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2cc9 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 21 19:23:05.791 2010 (UTC - 4:00)
System Uptime: 0 days 0:38:15.461
BugCheck 24, {1904fb, fffff880097c55c8, fffff880097c4e30, fffff880012dcdaf}
Probably caused by : Ntfs.sys ( Ntfs!TxfAccessCheck+9f )
PROCESS_NAME:  mcbuilder.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 17 00:18:19.218 2010 (UTC - 4:00)
System Uptime: 0 days 0:48:03.888
BugCheck 3B, {c0000005, fffff80002ebe805, fffff88009c950b0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 16 23:29:45.453 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:48.123
BugCheck 3B, {c0000005, fffff9600012015f, fffff88009d3f740, 0}
Probably caused by : win32k.sys ( win32k!DereferenceClass+1f )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  windbg.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 16 23:25:27.397 2010 (UTC - 4:00)
System Uptime: 0 days 6:32:26.677
BugCheck 27, {baad0073, fffff8800b167388, fffff8800b166bf0, fffff80002e82805}
*** WARNING: Unable to verify timestamp for avgmfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx64.sys
Probably caused by : luafv.sys ( luafv!LuafvGenerateFileName+6d )
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x27
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 16 16:52:32.116 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:59.396
BugCheck 27, {baad0073, fffff8800840cdc8, fffff8800840c630, fffff880061e6068}
Probably caused by : mrxsmb10.sys ( mrxsmb10!SmbCeInitializeTransactExchange+1ac )
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x27
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 16 15:40:28.243 2010 (UTC - 4:00)
System Uptime: 0 days 21:59:04.523
BugCheck 3B, {c0000005, fffff80002ed2805, fffff8800a7a5aa0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 12 18:29:56.415 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:48.085
BugCheck 24, {1904fb, fffff880098063c8, fffff88009805c30, fffff880012b806b}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCreateScb+eb )
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 12 18:20:37.035 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:49.705
BugCheck 3B, {c0000005, fffff960001495b5, fffff88003b69130, 0}
Probably caused by : win32k.sys ( win32k!LFONTOBJ::ppfeMapFont+1d1 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[wilhemina]

Thanks for the replies!
I have already uninstalled AVG...but I'll rerun the tool to make sure that there are no left-behinds. I'll let you know what happens.

 

[wilhemina]

The system seems stable so far. I will give a bit of room for observation. It seems from your last reply (I hope) that RAM and hardware issues have become less likely? Or am I hoping too much? I've used the HD diagnostic estools with no errors and have done a memtest for 24 hours with both ram sticks and 7 hours with each. I also did an sfc /scannow as well as chkdsk /f/r, both with no issues. I really want to stop worrying about the hardware so are these tests at least relatively conclusive? The latest 3 bsods were after I uninstalled avg and installed mse. The annoying thing is that after I uninstalled avg, there was 4 days of 'peace' before the last 3 dumps showed up again (starting from July 21). So I'm really hoping that I can @ least stop worrying about some hardware issues. (I mean I could rma the whole computer for all it's worth but I'd like to know what still stands to be at risk). Thanks so much for the help.

 

[wilhemina]

Hello again. I've been observing the system for some time and everything seemed to be fine until now. This is the latest in the set of Bsods. Before this, I had run all the aforementioned tests and pretty much have been keeping an eye on the system. Suddenly just a few minutes ago, it gave 3 bsods in rapid succession. I have them attached as minidump2. I feel it may be pointing to a hardware issue. I was using internet explorer when it happened..

 

[Jonathan_King]

Please enable driver verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[wilhemina]

Hello. Thx for the prompt reply!
Okay after enabling driver verifier and running memtest one more time ( for 5 hours), I restarted the computer to get another bsod (just @ startup). This time a driver was highlighted. So i've put it up.

 

[Jonathan_King]

Good thing you enabled Driver Verifier, because it is now pointing to your Realtek Audio Drivers. See if you can find an update:

Timestamp:        Wed Oct 21 10:27:48 2009 (4ADF1A64)

It is recommended to download drivers from the computer manufacturer's website. However, if you can't find them, you can download some generic drivers directly from Realtek: Realtek

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 2 for Memdump3.zip\072710-21340-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`0304ae50
Debug session time: Tue Jul 27 05:43:15.839 2010 (GMT-4)
System Uptime: 0 days 0:00:23.524
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff9800bbc8d60, 0, fffff880064ba1ee, 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+b61ee )

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: fffff9800bbc8d60, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff880064ba1ee, 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 fffff800030b50e0
 fffff9800bbc8d60 

FAULTING_IP: 
RTKVHD64+b61ee
fffff880`064ba1ee 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:  fffff88003721290 -- (.trap 0xfffff88003721290)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880037214b8
rdx=fffff88003721420 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880064ba1ee rsp=fffff88003721420 rbp=0000000000000002
 r8=0000000000000000  r9=fffff880064ba1ee r10=0000000000000000
r11=fffff880009e8180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
RTKVHD64+0xb61ee:
fffff880`064ba1ee 8b4630          mov     eax,dword ptr [rsi+30h] ds:8180:00000000`00000030=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002efde54 to fffff80002e7d600

STACK_TEXT:  
fffff880`03721128 fffff800`02efde54 : 00000000`00000050 fffff980`0bbc8d60 00000000`00000000 fffff880`03721290 : nt!KeBugCheckEx
fffff880`03721130 fffff800`02e7b6ee : 00000000`00000000 fffff8a0`0172c110 fffffa80`06438500 fffff800`02eb020f : nt! ?? ::FNODOBFM::`string'+0x42877
fffff880`03721290 fffff880`064ba1ee : fffff880`037214b8 00000000`00000000 fffff8a0`0172c110 fffffa80`06ab1f40 : nt!KiPageFault+0x16e
fffff880`03721420 fffff880`037214b8 : 00000000`00000000 fffff8a0`0172c110 fffffa80`06ab1f40 00000000`00000000 : RTKVHD64+0xb61ee
fffff880`03721428 00000000`00000000 : fffff8a0`0172c110 fffffa80`06ab1f40 00000000`00000000 fffff800`00000000 : 0xfffff880`037214b8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTKVHD64+b61ee
fffff880`064ba1ee 8b4630          mov     eax,dword ptr [rsi+30h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  RTKVHD64+b61ee

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTKVHD64

IMAGE_NAME:  RTKVHD64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4adf1a64

FAILURE_BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+b61ee

BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+b61ee

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: fffff9800bbc8d60, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff880064ba1ee, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS:  fffff9800bbc8d60 

FAULTING_IP: 
RTKVHD64+b61ee
fffff880`064ba1ee 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:  fffff88003721290 -- (.trap 0xfffff88003721290)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880037214b8
rdx=fffff88003721420 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880064ba1ee rsp=fffff88003721420 rbp=0000000000000002
 r8=0000000000000000  r9=fffff880064ba1ee r10=0000000000000000
r11=fffff880009e8180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
RTKVHD64+0xb61ee:
fffff880`064ba1ee 8b4630          mov     eax,dword ptr [rsi+30h] ds:8180:00000000`00000030=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002efde54 to fffff80002e7d600

STACK_TEXT:  
fffff880`03721128 fffff800`02efde54 : 00000000`00000050 fffff980`0bbc8d60 00000000`00000000 fffff880`03721290 : nt!KeBugCheckEx
fffff880`03721130 fffff800`02e7b6ee : 00000000`00000000 fffff8a0`0172c110 fffffa80`06438500 fffff800`02eb020f : nt! ?? ::FNODOBFM::`string'+0x42877
fffff880`03721290 fffff880`064ba1ee : fffff880`037214b8 00000000`00000000 fffff8a0`0172c110 fffffa80`06ab1f40 : nt!KiPageFault+0x16e
fffff880`03721420 fffff880`037214b8 : 00000000`00000000 fffff8a0`0172c110 fffffa80`06ab1f40 00000000`00000000 : RTKVHD64+0xb61ee
fffff880`03721428 00000000`00000000 : fffff8a0`0172c110 fffffa80`06ab1f40 00000000`00000000 fffff800`00000000 : 0xfffff880`037214b8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTKVHD64+b61ee
fffff880`064ba1ee 8b4630          mov     eax,dword ptr [rsi+30h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  RTKVHD64+b61ee

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTKVHD64

IMAGE_NAME:  RTKVHD64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4adf1a64

FAILURE_BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+b61ee

BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+b61ee

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

1: kd> lmvm RTKVHD64
start             end                 module name
fffff880`06404000 fffff880`065ee080   RTKVHD64 T (no symbols)           
    Loaded symbol image file: RTKVHD64.sys
    Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
    Image name: RTKVHD64.sys
    Timestamp:        Wed Oct 21 10:27:48 2009 (4ADF1A64)
    CheckSum:         001FA0EE
    ImageSize:        001EA080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[wilhemina]

I've never been so happy to get blue screens. I dunno what driver verifier does, but the motherboard fans have been louder than usual. It really feels like my desktop is being tasked to the max. Anyway, there have been four more bsods. You will notice that they are similar and they seem to highlight the same drivers. After reading your email, I proceeded to uninstall the ati hdmi audio driver and update it to the version 6.0.1.6121. I had no issues with the replacement windows legacy drivers (which replaced it after installation) but when I tried to run the catalyst manager setup for the update I had 2 sets of bsods. One set of two just after the restart before the installation completed and another when I tried to update my amd chipset after I ran driveragent and according to it my usb controllers and ATISMBus were outdated (running the windows drivers). Dunno if I really know what those mean though..
Anyway that's the story. If the manufacturers installer is causing the bsod then maybe I should stick with the windows drivers?
Here are the dumps.

 

[Jonathan_King]

Now it's pointing to atdcm64a.sys as the cause, which is definitely ATi-related. If you have the Catalyst Control Center installed, be sure to remove it.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 2 for Minidumps4.zip\072710-26020-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`0304ae50
Debug session time: Tue Jul 27 19:47:19.844 2010 (GMT-4)
System Uptime: 0 days 0:34:05.530
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {20e, fffff88008df8432, fffff9801aa8aea0, 0}

Unable to load image \??\C:\ATI\Support\9-9_vista64_win7_64_dd_ccc_wdm_enu\Driver\Bin64\atdcm64a.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atdcm64a.sys
*** ERROR: Module load completed but symbols could not be loaded for atdcm64a.sys
Probably caused by : atdcm64a.sys ( atdcm64a+2432 )

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

 

[wilhemina]

Should I uninstall the ati hdmi audio driver as well (The one mentioned in the former bsod)?

 

[Jonathan_King]

Yep, go right ahead.

 

[wilhemina]

Hi again!
It's been a while. The good news is: it seems the system has been stable all this while. I kept it running for a week, and there was not a single BSOD until, well... 5 minutes ago. Pointing to something like NETIO.sys. I've kept driver verifier on all this while, restarted the system once and kept it going for a week straight, until this showed up. I don't know if it's time to turn verifier off because it supposedly induces more crashes. Any advice? Here's the dump:

 

[Jonathan_King]

Please remove 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

 

[wilhemina]

2 new memdumps. Is there no end?
I really appreciate your time in helping me deal with these annoyances. I had already uninstalled daemon tools as well as spdt.sys (unwittingly installed by a colleague). I hope my hardware is okay.
When would you consider a safe time to deactivate Driver Verifier?
Thanks.

 

[wilhemina]

There was another one just a minute ago: A constant symptom seems to be Google chrome malfunctioning.. if that helps.

Thanks a bunch!

 

[wilhemina]

It's raining dumps. Here's the latest one.