New windows 7 install BSOD problems

Hi,

I've recently decided to take the leap and buy windows 7. Yesterday, I finally got round to installing it (on a different partition, so that I can still keep my old XP installs). However, I'm having problems with seemingly random BSODs. I have not yet figured out what triggers them. These BSODs do not happen in XP, so I assume it is a windows 7 driver issue.

After installing the OS, I let the automatic updates install. I tried to install the latest graphics driver for my 4870 - CCC 9.11, but I had BSOD problems installing this. Tried CCC 9.8, same problem. Have now managed to install CCC 9.10. However, I got a BSOD when I opened CCC. I don't know whether the random BSODs are actually anything to do with the graphics driver or not.

The only other hardware I have in place are a USB wireless dongle (which was automatically detected, so I didn't manually install any drivers) and an Audigy 2 zs sound card (which I have not yet installed the drivers for, as I thought I should solve any existing problems first!). I have not installed any other drivers manually.

Following the advice that I read somewhere else in this forum, I have attached a zipped copy of my minidump directory.

Any help would be greatly appreciated!

Thanks in advance,
Robb

An update - I've just had another BSOD when I clicked on the 'system performance rating' thing in the system menu, if that helps...

Thanks for your quick response! I will do that.

Thanks again!
Robb

robb1 said:

Hi,

I've recently decided to take the leap and buy windows 7. Yesterday, I finally got round to installing it (on a different partition, so that I can still keep my old XP installs). However, I'm having problems with seemingly random BSODs. I have not yet figured out what triggers them. These BSODs do not happen in XP, so I assume it is a windows 7 driver issue.

After installing the OS, I let the automatic updates install. I tried to install the latest graphics driver for my 4870 - CCC 9.11, but I had BSOD problems installing this. Tried CCC 9.8, same problem. Have now managed to install CCC 9.10. However, I got a BSOD when I opened CCC. I don't know whether the random BSODs are actually anything to do with the graphics driver or not.

The only other hardware I have in place are a USB wireless dongle (which was automatically detected, so I didn't manually install any drivers) and an Audigy 2 zs sound card (which I have not yet installed the drivers for, as I thought I should solve any existing problems first!). I have not installed any other drivers manually.

Following the advice that I read somewhere else in this forum, I have attached a zipped copy of my minidump directory.

Any help would be greatly appreciated!

Thanks in advance,
Robb

Hi Rob and welcome

info on a hotfix for the clfd.sys is here http://support.microsoft.com/kb/9397....com/kb/939720

While my learned colleague is correct, I would also

download and run memtestx86 for several hours at least
run a system file check (to verify and repair) your system files
type cmd in search>right click and run as admin>sfc /scannow

If you are overclocking stop
if you have a raid update its driver
update the drivers listed below

Code:

secdrv.SYS        fffff880`05d65000    fffff880`05d70000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
emupia2k.sys        fffff880`04760000    fffff880`047b2000    0x00052000    0x461a3aba    4/9/2007 8:08:10 AM                        
ctsfm2k.sys        fffff880`047b2000    fffff880`047fc000    0x0004a000    0x461a3abb    4/9/2007 8:08:11 AM                        
ctoss2k.sys        fffff880`03d91000    fffff880`03dcc000    0x0003b000    0x461a3abe    4/9/2007 8:08:14 AM                        
ha10kx2k.sys        fffff880`04e0c000    fffff880`04fc5000    0x001b9000    0x461a3abf    4/9/2007 8:08:15 AM                        
hap16v2k.sys        fffff880`0471e000    fffff880`04760000    0x00042000    0x461a3ac1    4/9/2007 8:08:17 AM                        
ctaud2k.sys        fffff880`03c1e000    fffff880`03cef000    0x000d1000    0x461a3acd    4/9/2007 8:08:29 AM                        
ctprxy2k.sys        fffff880`03dcc000    fffff880`03dd4000    0x00008000    0x461a3ace    4/9/2007 8:08:30 AM                        
COMMONFX.DLL        fffff880`04fc5000    fffff880`04ff0000    0x0002b000    0x461a3ad6    4/9/2007 8:08:38 AM                        
CTAUDFX.DLL        fffff880`05438000    fffff880`054e7000    0x000af000    0x461a3ad7    4/9/2007 8:08:39 AM                        
CTSBLFX.DLL        fffff880`054e7000    fffff880`05592000    0x000ab000    0x461a3ada    4/9/2007 8:08:42 AM

Code:

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


Loading Dump File [C:\Users\K\Desktop\121509-17004-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02860000 PsLoadedModuleList = 0xfffff800`02a9de50
Debug session time: Tue Dec 15 10:04:05.387 2009 (GMT-5)
System Uptime: 0 days 0:05:30.963
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, fffff800028db18c}

Probably caused by : CLFS.SYS ( CLFS!CClfsContainer::WriteSector+3ac )

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

1: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff800028db18c, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b080e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeWaitForSingleObject+17c
fffff800`028db18c 4c8938          mov     qword ptr [rax],r15

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800623a200 -- (.trap 0xfffff8800623a200)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88005062bb8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028db18c rsp=fffff8800623a390 rbp=0000000000000000
 r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
r11=fffff880009e5180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x17c:
fffff800`028db18c 4c8938          mov     qword ptr [rax],r15 ds:6000:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800028d1469 to fffff800028d1f00

STACK_TEXT:  
fffff880`0623a0b8 fffff800`028d1469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0623a0c0 fffff800`028d00e0 : 00000000`00000000 00000000`00000000 fffff880`05062bb0 fffffa80`06236040 : nt!KiBugCheckDispatch+0x69
fffff880`0623a200 fffff800`028db18c : 00000000`00000294 00000000`73666c43 00000103`00000000 fffffa80`0689fc20 : nt!KiPageFault+0x260
fffff880`0623a390 fffff880`00ca4f98 : 00000000`00000000 fffffa80`00000000 fffffa80`04d0c400 00000000`00007a00 : nt!KeWaitForSingleObject+0x17c
fffff880`0623a430 fffff880`00c9e90b : 00000000`00007a00 fffff880`05062bb0 fffffa80`0665ac00 fffff8a0`0074b000 : CLFS!CClfsContainer::WriteSector+0x3ac
fffff880`0623a4d0 fffff880`00c9e642 : fffffa80`05056590 fffffa80`05056590 00000000`00000001 fffff8a0`00001a01 : CLFS!CClfsBaseFilePersisted::WriteMetadataBlock+0x24b
fffff880`0623a560 fffff880`00c82335 : fffffa80`05056590 00000000`00000001 00000000`00000000 00000000`00000000 : CLFS!CClfsBaseFilePersisted::FlushImage+0x3a
fffff880`0623a5a0 fffff880`00caf2fd : 00000000`00000000 00000000`00000000 fffffa80`03a09b30 00000000`00000000 : CLFS!CClfsLogFcbPhysical::FlushMetadata+0xe1
fffff880`0623a5f0 fffff880`00cabd57 : fffffa80`050626e0 fffff8a0`00001a60 fffffa80`03a2e000 00000000`00000000 : CLFS!CClfsLogFcbVirtual::Cleanup+0x231
fffff880`0623a690 fffff880`00ca8c52 : fffffa80`050626e0 fffff880`0623aaa0 fffffa80`03a09b30 00000000`00000000 : CLFS!CClfsLogCcb::Cleanup+0x147
fffff880`0623a6e0 fffff880`00cc24be : fffffa80`06111580 fffffa80`06111580 00000000`00000001 fffffa80`04e752d0 : CLFS!CClfsRequest::Cleanup+0x5e
fffff880`0623a730 fffff880`00c9aa09 : fffffa80`06111580 00000000`00000000 fffffa80`03a2e060 00000000`00000000 : CLFS!ClfsDispatchIoRequest+0x32
fffff880`0623a780 fffff800`02be568f : fffffa80`06111580 fffffa80`03a09b30 00000000`00000000 fffffa80`04e752d0 : CLFS!CClfsDriver::LogIoDispatch+0x21
fffff880`0623a7b0 fffff800`02bcb304 : 00000000`00000000 fffffa80`03a09b30 fffff880`00c94110 fffff880`00c84b99 : nt!IopCloseFile+0x11f
fffff880`0623a840 fffff800`02be5181 : fffffa80`03a09b30 fffffa80`00000001 fffff8a0`00001a60 00000000`00000002 : nt!ObpDecrementHandleCount+0xb4
fffff880`0623a8c0 fffff800`02be5094 : 00000000`0000014c fffffa80`03a09b30 fffff8a0`00001a60 00000000`0000014c : nt!ObpCloseHandleTableEntry+0xb1
fffff880`0623a950 fffff800`028d1153 : fffffa80`06236040 fffff880`0623aa20 fffff880`00c94110 fffff880`00cb59d7 : nt!ObpCloseHandle+0x94
fffff880`0623a9a0 fffff800`028cd6f0 : fffff880`00cc9476 ffffffff`fffef800 00000000`00000000 fffff8a0`0046c3c0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0623ab38 fffff880`00cc9476 : ffffffff`fffef800 00000000`00000000 fffff8a0`0046c3c0 00000000`00000000 : nt!KiServiceLinkage
fffff880`0623ab40 fffff800`02b5d5e2 : fffffa80`05058510 fffffa80`050625c0 00000000`00000000 00000000`00000000 : CLFS!ClfsCloseLogFileObject+0x7a
fffff880`0623ab80 fffff800`029cf289 : fffffa80`05058510 00000000`00000000 00000000`00000000 00000000`00aa0000 : nt!TmpTmOffline+0xe6
fffff880`0623abd0 fffff800`02b5c877 : fffffa80`05058510 fffffa80`056be940 00000000`00000000 00000000`00000000 : nt!TmpShutdownTransactionManager+0x9
fffff880`0623ac00 fffff800`029a13f0 : fffff800`02a4a9e0 fffff800`02a755a0 00000000`00000001 ffffe62d`923f7900 : nt!TmpNamespaceForEach+0x8f
fffff880`0623ac40 fffff800`02b1ffa0 : 00000000`00000001 00000000`00000001 fffff880`0623ace8 fffffa80`04e373d0 : nt!TmShutdownSystem+0x60
fffff880`0623ac70 fffff800`028df161 : fffff800`02b1fe50 fffff800`02bcb504 fffffa80`06236040 00000000`00000000 : nt!PopGracefulShutdown+0x150
fffff880`0623acb0 fffff800`02b75166 : 00000000`05fe2afe fffffa80`06236040 00000000`00000080 fffffa80`03a09b30 : nt!ExpWorkerThread+0x111
fffff880`0623ad40 fffff800`028b0486 : fffff880`009e5180 fffffa80`06236040 fffffa80`06237040 fffff880`0125a534 : nt!PspSystemThreadStartup+0x5a
fffff880`0623ad80 00000000`00000000 : fffff880`0623b000 fffff880`06235000 fffff880`02708b60 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
CLFS!CClfsContainer::WriteSector+3ac
fffff880`00ca4f98 89442434        mov     dword ptr [rsp+34h],eax

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  CLFS!CClfsContainer::WriteSector+3ac

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CLFS

IMAGE_NAME:  CLFS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11d

FAILURE_BUCKET_ID:  X64_0xA_CLFS!CClfsContainer::WriteSector+3ac

BUCKET_ID:  X64_0xA_CLFS!CClfsContainer::WriteSector+3ac

Followup: MachineOwner

---------