Windows 7: BSOD Stop 109 CLFS.SYS Random Times

gabman6 · 11 Nov 2011

Hello everyone,

Okay I've tried my best to solve this one on my own, but it seems like there's just a ton of other factors I either aren't taking into consideration or that I don't even know of. It's bugging the heck out of me! Please help.

Initial Specs:

- Windows 7 Professional x64
- full retail version (student upgrade)
- Just newly built (about a month old)
- Age of the OS is new, I guess? This was the first and only installation of Windows 7

Thanks all.

zigzag3143 · 11 Nov 2011

Quote: Originally Posted by gabman6

Hello everyone,

Okay I've tried my best to solve this one on my own, but it seems like there's just a ton of other factors I either aren't taking into consideration or that I don't even know of. It's bugging the heck out of me! Please help.

Initial Specs:

- Windows 7 Professional x64
- full retail version (student upgrade)
- Just newly built (about a month old)
- Age of the OS is new, I guess? This was the first and only installation of Windows 7

Thanks all.

Memory corruption (probably related to a 2005 driver SNTUSB64.SYS) I would run these two tests

Please run these two tests to verify your memory and find which driver is causing the problem.

1-Memtest.

Quote:

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+

2-Driver verifier

Quote:

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Driver Verifier - Enable and Disable

gabman6 · 14 Nov 2011

Hello,

So i managed to get DriverVerifier working and it BSOD everytime BattleField 3 would enter the game after loading the level in Battlelog.

I also got this latest BSOD when i ran BSOD 3.03.

It has to do with HIDCLASS.sys.

What does this mean now?

As for MemTest, I did 29 passes for each test, so im pretty sure that department is okay.

zigzag3143 · 14 Nov 2011

Quote: Originally Posted by gabman6

Hello,

So i managed to get DriverVerifier working and it BSOD everytime BattleField 3 would enter the game after loading the level in Battlelog.

I also got this latest BSOD when i ran BSOD 3.03.

It has to do with HIDCLASS.sys.

What does this mean now?

As for MemTest, I did 29 passes for each test, so im pretty sure that department is okay.

Your crashes prior to verifier were Related to clfs.sys Common Log File System Driver from Microsoft Corporation

After hidclass.sys. It may very well be verifier kicking of the HID. Human Interface Deviices are usually external devices like gamie steering wheels, non standard mice, keyboards, or some other device.

In the HID case it may be an external device (USB, or in your case BT and lots of them) that is causing the HID.

I would start by running a system file check

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

It may need to be run up to three times before sucessful

Read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.

gabman6 · 16 Nov 2011

So I managed to get a notification after doing the scan. Something about a CBS.log

I've attached the .log file.

Otherwise, there was no violations to report

Shortly there after, got another BSOD 124 about hal.dll

Why aren't these errors consistent!?

Thank you

gabman6 · 18 Nov 2011

Has anyone found any solution yet? I would greatly appreciate a response. Thank you.

zigzag3143 · 18 Nov 2011

Quote: Originally Posted by gabman6

Has anyone found any solution yet? I would greatly appreciate a response. Thank you.

The 4 driver verified crashes all still Point to HIDCLASS.sys

You need to resolve what device is causing the problem, if necessary by a process of elimination.

If it is under warranty take it back, if it isnt, perhaps take it to a pro.

If you are comfortable start disabling things in start up, remove external devices.

Remove everything but the mouse, keyboard, monitor.

Lets take another tact

Please put your system specs in user cp so we know what hardware we are dealing with

Please give us a list of all the things connected to the computer (usb, BT, finger print reader, joystick, XBOX, PS3, etc.

Use an application like Everest, Aida64, SIW2 to get fully detailed reports about your hardware.

gabman6 · 21 Nov 2011

So I've managed to test different scenarios but I'm still getting the errors.

I have no other things plugged in besides the mouse keyboard monitor. I've tried having just the keyboard in, resetting, having only the mouse.

I've tried uninstalling all the USB controllers / Human Interface Devices drivers in the Device Manager and have them reinstall after i restart, but that didn't work either.

Different mouse/keyboards still cause the bsod when i try to run BF3 or another game. Surprisingly StarCraft 2 runs though.

It's still all pointing to HIDCLASS.SYS.

Also I'd like to know why the error code is now C9 when Driver Verifier is on rather than a code 109 when Verifier is off?

I've attached my hardware report from Everest as well.

Windows 7: BSOD Stop 109 CLFS.SYS Random Times

BSOD Stop 109 CLFS.SYS Random Times problems?