cdfs.sys blue screen stop error WinXP

[jstevens]

Anyone seen this cdfs error? Randomly when I use cd's in my new Sony cdrw / dvd drive I get this. I just loaded up a new system with an MSI K8N Neo 4 Platinum SLI.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000014, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f2a899c6, address which referenced memory

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


READ_ADDRESS: 00000014

CURRENT_IRQL: 2

FAULTING_IP:
Cdfs!CdCheckForDismount+82
f2a899c6 83781401 cmp dword ptr [eax+0x14],0x1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f2a89b00 to f2a899c6

STACK_TEXT:
f48418c0 f2a89b00 857d9e08 856f8601 00000000 Cdfs!CdCheckForDismount+0x82
f4841908 f2a887dc 857d9e08 857073a0 86c49b50 Cdfs!CdPerformVerify+0xde
f484194c f2a88611 857d9e08 857073a0 80000016 Cdfs!CdProcessException+0x15b
f48419a0 804eeeb1 856f8620 857073a0 8570762c Cdfs!CdFsdDispatch+0x164
f48419d8 ec2037f0 856f8620 86a25640 f4841a10 nt!MiAddViewsForSection+0x38
WARNING: Stack unwind information not available. Following frames may be wrong.
f48419f4 ec1fc8b9 f4841a10 804efd76 ec1fc97a SYMEVENT+0xe7f0
f4841a30 804eeeb1 86d60078 857073a0 857073a0 SYMEVENT+0x78b9
f4841a70 804eeeb1 86a4c1a0 85707608 857073a0 nt!MiAddViewsForSection+0x38
f4841b60 805bdd08 86c49b50 00000000 856f1478 nt!MiAddViewsForSection+0x38
f4841bd8 805ba390 00000000 f4841c18 00000040 nt!NtCreatePagingFile+0x418
f4841c2c 80574e37 00000000 00000000 08fd3401 nt!CcPfParametersRead+0x87
f4841ca8 805757ae 0108fdb0 00100001 0108fd60 nt!FsRtlIsNameInExpression+0x40
f4841d04 80578f6d 0108fdb0 00100001 0108fd60 nt!HvMarkCellDirty+0xb8
f4841d44 8054060c 0108fdb0 00100001 0108fd60 nt!NtOpenMutant+0x4a
f4841d64 7c90eb94 badb0d00 0108fd3c 00000000 nt!RtlIpv4StringToAddressA+0xfd
f4841d78 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
Cdfs!CdCheckForDismount+82
f2a899c6 83781401 cmp dword ptr [eax+0x14],0x1

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Cdfs!CdCheckForDismount+82

MODULE_NAME: Cdfs

IMAGE_NAME: Cdfs.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41107eb1

FAILURE_BUCKET_ID: 0xD1_Cdfs!CdCheckForDismount+82

BUCKET_ID: 0xD1_Cdfs!CdCheckForDismount+82


Thanks
Jason

 

[jstevens]

Big help this is

http://support.microsoft.com/kb/293077/en-us

SYMPTOMS
You may receive the following error message on a blue screen:
STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x0,0x0,0x0,0x0)
Back to the top

Parameters
1 - memory that is referenced
2 - IRQL
3 - value 0 = read operation, 1 = write operation
4 - address that referenced memory
Back to the top

CAUSE
This issue can occur when the Driver Verifier feature is enabled and a driver has used an improper address. Note that the driver that is causing this issue may be listed in the error message.
Back to the top

RESOLUTION
To resolve this issue: 1. Disable all third-party filter drivers, such as backup programs, virus scanning programs, and disk utilities.
2. Make sure that you are using hardware that appears on the Windows Hardware Compatibility List (HCL). To view the latest Windows HCL, visit the following Microsoft Web site:

http://www.microsoft.com/hwdq/hcl/

(

http://www.microsoft.com/hwdq/hcl/)

 

[linney]

Have a look at any relevant posts here.

http://www.google.com/search?source...LG,GGLG:2005-48,GGLG:en&q=Cdfs.sys+irql+xp+cd

HOW TO: Verify Unsigned Device Drivers in Windows XP

http://support.microsoft.com/support/kb/articles/q308/5/14.asp

DRIVER_IRQL_NOT_LESS_OR_EQUAL error
thread779-308429


These next threads will lead you in to "Debugging" if you want to go down that track?


Getting more friendly logs from Drwatson.
thread779-947690

Windows Debugger, part of Never-Ending-Problem
thread779-1064535

Third copy attempt on 2GB data files = BSOD!
thread779-1025514

 

[jstevens]

Thanks for the reply but like most others, it only points in a direction. I know its a driver but which one is the question.

I think its either the Nvidia Nforce IDE drivers which I chose to install over the standard Windows ones or My Symantec av driver. I dont think its actuall bad hardware.

But you never know. It may also be related to MSI's DOT dynamic overclocking technology of the CPU. When I leave it disabled I get much less stop errors. Dunno I will keep testing.

Thanks

J

 

[linney]

The loading of specific drivers can be disabled via the Recovery Console, see the Disable and Enable commands.

Safe Mode will not load any drivers at all.

These are helpful too.

310353 - How to Perform a Clean Boot in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;310353&FR=1&PA=1&SD=HSCH

316434 - HOW TO: Perform Advanced Clean-Boot Troubleshooting in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;316434&FR=1&PA=1&SD=HSCH

310560 - How to Troubleshoot By Using the Msconfig Utility in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;310560&FR=1&PA=1&SD=HSCH

I am not familiar with "MSI's DOT dynamic overclocking technology of the CPU" but have you tried updating your Bios or setting it to any "Safe Defaults" setting?

I wish you success in your endeavors but as you know all things like this involve the hard grind of elimination and testing to discover the cause. Do let us know the solution when you find it as it may help the next person who has the same problem.

 

[jstevens]

Well I found the issue a while ago but thought I would post here just to update.

I had connected my SATA primary hard drive to the first port on my mainboard. However this was not the first SATA port but was SATA port 2.

When I moved my hardrive to SATA 1, access between the CDROM and HD is fine now. Seems like on this board or chipset, putting your primary drive non-sequentionally causes major instability.

Jason

 

[maxthedork]

If you installed a new driver, try rolling back to the previous driver?