Driver Verifier BSOD's

dimitris21 · 05 May 2012

Hello,

I have been having random crashes during all sorts of operations....watching a flash video,opening up a program,running a game or even at idle.
Weird thing is that the pc never crashed whilst running torture tests with prime95 and furmark.Prime 95 completed 12 hours in blend run, and as long as possible in large and small fft's before i had to stop it due to very high temps(system is usually overclocked-and the QX6700 isn't exactly cooling friendly at 130TDP).
The crashes however occur in both default clocked and overclocked...
System file checker(sfc scannow) completes with no problem
I attach the jcgriff2 and perfmon files for any help or ideas-The attachments were taken with the system in default clocks just to be sure.

Win7 x64 Ultimate
Seasonic X-series 760W
ABIT AW9d-MAX
Intel QX6700
8GB Ram OCZ Reaper
EVGA 460gtx
Asus Xonar D2X
RocketRaid 2640x4
7x Hard disks

Thank you,
Dimitris

dimitris21 · 05 May 2012

I attach an updated dmp file of a SSD error
as well as the link to a really large *.dmp file created with today's bsods(size was 559mb-zipped to 130).
http://uploading.com/files/e1d853d9/MEMORY.zip/

dimitris21 · 06 May 2012

I had to disable the page file because i was doing some tests and the pc crashed again so the bsod didnt save a minidump but i attach the event reports.could be helpful :)

usasma · 06 May 2012

I have to go to work, but wanted to post this so you can get started:

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum

Point a house fan into the case and see if that makes the crashes occur less often. It may be a component overheating that doesn't have a sensor on it.

Please stop overclocking until the system is stable again. Feel free to resume overclocking once it's stable - but until then we need to test the system in it's standard configuration (not overclocked).

If you had to stop Prime95 due to high temperatures, then you must work on your CPU cooling solution (and maybe the RAM cooling also). Prime95 should be able to run without having excessively high temperatures.

usasma · 06 May 2012

Overclocks interfere with troubleshooting. Please remove the overclock to see if the system continues to BSOD. If not, feel free to resume the overclock AFTER the troubleshooting is finished (your system has a 25% overclock (approximately a 640 mHz)).

It looks like you have some sort of Sony Ericsson device that's using USB to emulate a network connection. I don't trust these devices and have to wonder if they're causing your problem. Don't do anything with it right now, but remember it for troubleshooting later on.

You have a whole pile of problem devices:

Realtek PCIe GBE Family Controller #5 PCI\VEN_10EC&DEV_8168&SUBSYS_240B147B&REV_01\4&2A9E0036&0&00E2 This device is disabled.
G19 Gaming Keyboard (Display interface) USB\VID_046D&PID_C229&MI_00\7&28F48D07&0&0000 This device is disabled.
TAP-Win32 Adapter V9 (Tunngle) ROOT\NET\0000 This device is disabled.
ESLvnic Virtual Network 64 Bit ROOT\NET\0001 This device is disabled.
High Definition Audio Controller PCI\VEN_10DE&DEV_0BEB&SUBSYS_13713842&REV_A1\4&DF6EA01&0&0108 This device is disabled.
VMware Virtual Ethernet Adapter for VMnet1 ROOT\VMWARE\0000 This device is disabled.
VMware Virtual Ethernet Adapter for VMnet8 ROOT\VMWARE\0001 This device is disabled.

Disabled devices still load drivers - so it's advisable to uninstall the software for these devices and then physically remove the devices from your system (or disable in the BIOS).

I've seen issues with Abit uGuru in the past, please uninstall it. Feel free to reinstall it once the system is stable again.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

Some free alternatives (I don't use them, so I can't comment on them)
KernSafe iSCSI initiator, Virtual CD/DVD-RW Emulator, Virtual Encryption Disk and Virtual CD/DVD-ROM Emulator All-in-One free software.
MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor

EVGA Precision (and the same goes for RivaTuner and MSI Afterburner) causes BSOD's on Win7 systems. Please uninstall it immediately.

Your Silicone Image storage drivers date from 2007. Please update them immediately. More info here: Driver Reference Table - SI3132.sys

uGuru dates from 2006, please uninstall it. More info here: Driver Reference Table - uGuru.sys

Elby Clone DVD dates from 2006, please uninstall it. More info here: Driver Reference Table - ElbyDelay.sys

Acronis True Image dates from 2009 and is likely not compatible with Win7. Please uninstall it. If you wish to continue using it, please upgrade to a version that's compatible with Win7.

ESL Wire AntiCheat is causing issues (from the Driver Verifier memory dump), please uninstall it. More info here: http://img849.imageshack.us/img849/7440/88703120.jpg and here: ESL: ESL Wire Anti-Cheat - Anti-Cheat - ESL Wire - Europe - ESL - The eSports League

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
How I do it: http://www.carrona.org/howidoit.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


LHidFilt.Sys    Fri Sep 02 02:23:09 2011 (4E60764D)
LMouFilt.Sys    Fri Sep 02 02:23:15 2011 (4E607653)
sptd.sys        Tue Jan 03 19:01:58 2012 (4F0396F6)
SI3132.sys      Wed Oct 03 14:39:29 2007 (4703E1E1)
rr26xx.sys      Tue May 12 22:17:52 2009 (4A0A2DD0)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
iaStorV.sys     Thu Jun 10 20:46:19 2010 (4C11875B)
SiWinAcc.sys    Thu Jun 14 20:02:02 2007 (4671D6FA)
avc3.sys        Tue Mar 20 07:04:13 2012 (4F68642D)
bdfsfltr.sys    Wed Jul 27 11:23:21 2011 (4E302D69)
bdfwfpf.sys     Mon Nov 14 12:16:17 2011 (4EC14CE1)
VMkbd.sys       Thu Oct 22 06:51:05 2009 (4AE03919)
timntr.sys      Tue Sep 29 09:36:57 2009 (4AC20D79)
tdrpm258.sys    Tue Oct 20 03:39:53 2009 (4ADD6949)
snapman.sys     Mon Oct 19 06:29:56 2009 (4ADC3FA4)
SiRemFil.sys    Wed Jun 20 15:42:10 2007 (46798312)
ISODrv64.sys    Tue Feb 10 04:22:18 2009 (4991474A)
ElbyCDIO.sys    Fri Jan 01 12:20:27 2010 (4B3E2EDB)
uGuru.sys       Wed Sep 20 04:06:44 2006 (4510F694)
avchv.sys       Fri Nov 25 04:04:45 2011 (4ECF5A2D)
WmXlCore.sys    Tue Apr 27 16:09:26 2010 (4BD74476)
bdvedisk.sys    Tue Jan 19 10:45:31 2010 (4B55D39B)
appdrv01.sys    Wed Aug 25 08:03:46 2010 (4C7506A2)
Rt64win7.sys    Wed Nov 23 10:00:40 2011 (4ECD0A98)
WmBEnum.sys     Tue Apr 27 16:10:19 2010 (4BD744AB)
cmudaxp.sys     Mon Dec 19 22:23:23 2011 (4EEFFFAB)
ElbyDelay.sys   Wed Dec 13 14:14:48 2006 (45805128)
LGBusEnum.sys   Mon Nov 23 20:36:48 2009 (4B0B38B0)
trufos.sys      Wed Oct 19 05:10:43 2011 (4E9E9413)
avckf.sys       Fri Feb 10 05:39:13 2012 (4F34F3D1)
vmnetbridge.sys Mon Aug 10 08:05:58 2009 (4A800D26)
VMNET.SYS       Mon Aug 10 08:04:50 2009 (4A800CE2)
RtNdPt60.sys    Sun Jul 19 22:27:32 2009 (4A63D614)
hcmon.sys       Thu Oct 22 06:00:49 2009 (4AE02D51)
vmci.sys        Thu Oct 22 05:26:48 2009 (4AE02558)
atksgt.sys      Sun May 17 09:36:34 2009 (4A1012E2)
ESLWireACD.sys  Wed Oct 26 07:14:34 2011 (4EA7EB9A)
vmx86.sys       Thu Oct 22 07:36:57 2009 (4AE043D9)
vmnetuserif.sys Thu Oct 22 06:17:07 2009 (4AE03123)
vstor2-ws60.sys Mon Oct 12 17:06:26 2009 (4AD39A52)
WinFLdrv.sys    Wed Nov 18 08:05:58 2009 (4B03F136)
DKRtWrt.sys     Mon Feb 14 05:03:42 2011 (4D58FDFE)
a3ftws9b.SYS    Tue Dec 27 17:30:45 2011 (4EFA4715)
nvlddmkm.sys    Wed Feb 29 13:04:52 2012 (4F4E68C4)
ay6831k3.SYS    Tue Dec 27 17:30:45 2011 (4EFA4715)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050512-20968-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sat May  5 12:00:32.314 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:55.845
*** WARNING: Unable to verify timestamp for SiWinAcc.sys
*** ERROR: Module load completed but symbols could not be loaded for SiWinAcc.sys
*** WARNING: Unable to verify timestamp for tdrpm258.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpm258.sys
Probably caused by : SiWinAcc.sys ( SiWinAcc+102e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_SiWinAcc+102e
Bugcheck code 00000050
Arguments fffffab0`0817f184 00000000`00000000 fffff880`016a7f85 00000000`00000005
BiosVersion = 6.00 PG
BiosReleaseDate = 01/15/2008
CPUID:        "Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 3300
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050512-29625-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sat May  5 06:18:02.115 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:46.677
*** WARNING: Unable to verify timestamp for ESLWireACD.sys
*** ERROR: Module load completed but symbols could not be loaded for ESLWireACD.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ESLWireACD.sys ( ESLWireACD+a688b )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_VRF_ESLWireACD+a688b
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`04c99396 00000000`00000000 00000000`00000000
BiosVersion = 6.00 PG
BiosReleaseDate = 01/15/2008
CPUID:        "Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 3333
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

dimitris21 · 07 May 2012

Thanks alot for your input.
I have uninstalled all software you mentioned and updated the SI3132 driver(at the moment it only powers a dvd-rw - all other sata of the si3132 controller are unused cause i'm using the intel controller for 3 disks and a raid card for the other 4 disks).Pc is back in default clock settings and default voltages(except for the ram because 8gb put quite a stress on the board).
I'll enable the pagefile again and run verifier to see the results and i'll post back with or without a .dmp file. :)

BTW - this SSD error was the first error ive had with SSD's since 2009!!(SSD's are a OCZ Vertex2 which hosts the Windows installation and an OCZ APEX to which i have placed the documents folder - both are running the latest firmware).
chkdsk fixed the errors and i ran a second round of chkdsk on all disks as well as a 3-phase scan with sfc /scannow just to make sure.

usasma · 07 May 2012

FWIW - most released 3rd party products are tested thoroughly before release.
And they usually perform well in that regard.

BUT, with time, the system adds other things into the "mix". Things like other drivers that interact with the drivers of the device (and they weren't tested with the device) - along with things like Windows Updates. If there's a hidden "glitch" in the firmware or drivers of this device, it may not have problems for years. But once an update encounters this "glitch", it may not respond well (or may not respond at all).

That's the reasoning behind a lot of our BSOD troubleshooting steps. I still recall all of the problems with SP2 for XP - simply because drivers weren't designed according to Microsoft/Windows standards, and the update broke them.

dimitris21 · 07 May 2012

Ok, i've had several bsod's in the last hour mainly concerning bad_pool_caller for a sys file: winfldrv.sys - which apparently is not a system file...trying to see whether it's malware,however bitdefender and malwarebytes have not picked it up
Then i hit an irql not less or equal bsod.
I've attached them here so you could have a look.
I'm currently reseating ram,gfx card, etc(i clean installed gfx drivers by using driver sweeper ) just in case.

usasma · 07 May 2012

All but one of the memory dumps blames winfldrv.sys. It most likely belongs to Folder Lock 6 from newsoftwares.net (and it's installed on your system)
Driver Reference Table - WinFLdrv.sys
Uninstall it and see if that helps.

There's a slight overclock on your system (80 mHz). Please restore the system to default (non-overclocked) settings while we're troubleshooting.

uGuru is still on your system. I requested that you remove it in my previous post. If you have, please post back and we'll discuss how to safely remove it.

Your Silicone Image drivers are still from 2007. If you replaced them, let's just wait and see what happens. These drivers don't have a history of causing problems - so I'd hate to go through the difficulties of removing it and disabling your CD/DVD drive just for testing purposes.

Please have a look at the drivers listed below. Troubleshooting will involve updating all possible drivers that date from 2009 and earlier - so you may want to get a head start on it. Look them up at my Driver Reference Table here: Driver Reference Table (FYI - the links below the driver listing will take you directly to the drivers that you want).

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
How I do it: http://www.carrona.org/howidoit.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


iaStorV.sys     Thu Jun 10 20:46:19 2010 (4C11875B)
SI3132.sys      Wed Oct 03 14:39:29 2007 (4703E1E1)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
avc3.sys        Tue Mar 20 07:04:13 2012 (4F68642D)
bdfwfpf.sys     Mon Nov 14 12:16:17 2011 (4EC14CE1)
bdfsfltr.sys    Wed Jul 27 11:23:21 2011 (4E302D69)
SiWinAcc.sys    Thu Jun 14 20:02:02 2007 (4671D6FA)
snapman.sys     Mon Oct 19 06:29:56 2009 (4ADC3FA4)
SiRemFil.sys    Wed Jun 20 15:42:10 2007 (46798312)
avchv.sys       Fri Nov 25 04:04:45 2011 (4ECF5A2D)
WmXlCore.sys    Tue Apr 27 16:09:26 2010 (4BD74476)
ISODrv64.sys    Tue Feb 10 04:22:18 2009 (4991474A)
WmBEnum.sys     Tue Apr 27 16:10:19 2010 (4BD744AB)
LGBusEnum.sys   Mon Nov 23 20:36:48 2009 (4B0B38B0)
Rt64win7.sys    Wed Nov 23 10:00:40 2011 (4ECD0A98)
cmudaxp.sys     Mon Dec 19 22:23:23 2011 (4EEFFFAB)
bdvedisk.sys    Tue Jan 19 10:45:31 2010 (4B55D39B)
LHidFilt.Sys    Fri Sep 02 02:23:09 2011 (4E60764D)
LMouFilt.Sys    Fri Sep 02 02:23:15 2011 (4E607653)
VMkbd.sys       Thu Oct 22 06:51:05 2009 (4AE03919)
trufos.sys      Wed Oct 19 05:10:43 2011 (4E9E9413)
appdrv01.sys    Wed Aug 25 08:03:46 2010 (4C7506A2)
avckf.sys       Fri Feb 10 05:39:13 2012 (4F34F3D1)
vmnetbridge.sys Mon Aug 10 08:05:58 2009 (4A800D26)
VMNET.SYS       Mon Aug 10 08:04:50 2009 (4A800CE2)
RtNdPt60.sys    Sun Jul 19 22:27:32 2009 (4A63D614)
hcmon.sys       Thu Oct 22 06:00:49 2009 (4AE02D51)
vmci.sys        Thu Oct 22 05:26:48 2009 (4AE02558)
vmx86.sys       Thu Oct 22 07:36:57 2009 (4AE043D9)
atksgt.sys      Sun May 17 09:36:34 2009 (4A1012E2)
vmnetuserif.sys Thu Oct 22 06:17:07 2009 (4AE03123)
vstor2-ws60.sys Mon Oct 12 17:06:26 2009 (4AD39A52)
WinFLdrv.sys    Wed Nov 18 08:05:58 2009 (4B03F136)
DKRtWrt.sys     Mon Feb 14 05:03:42 2011 (4D58FDFE)
nvlddmkm.sys    Tue Apr 03 09:01:59 2012 (4F7AF4C7)
uGuru.sys       Wed Sep 20 04:06:44 2006 (4510F694)
nvlddmkm.sys    Wed Feb 29 13:04:52 2012 (4F4E68C4)
rr26xx.sys      Tue May 12 22:17:52 2009 (4A0A2DD0)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050712-20234-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Mon May  7 13:14:42.993 2012 (UTC - 4:00)
System Uptime: 0 days 0:27:58.633
Probably caused by : ntkrnlmp.exe ( nt!KiQuantumEnd+ea )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  vsserv.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiQuantumEnd+ea
Bugcheck code 0000000A
Arguments fffffa83`09b4a108 00000000`00000002 00000000`00000001 fffff800`04ca01f6
BiosVersion = 6.00 PG
BiosReleaseDate = 01/15/2008
CPUID:        "Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2720
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050712-15609-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Mon May  7 12:38:13.963 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:39.620
*** WARNING: Unable to verify timestamp for WinFLdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for WinFLdrv.sys
Probably caused by : WinFLdrv.sys ( WinFLdrv+1cf9 )
BUGCHECK_STR:  0xc2_9d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc2_9d_WinFLdrv+1cf9
Bugcheck code 000000C2
Arguments 00000000`0000009d 00000000`000007d0 00000000`00000001 fffff880`07c29cf9
BiosVersion = 6.00 PG
BiosReleaseDate = 01/15/2008
CPUID:        "Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2720
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050712-14703-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Mon May  7 10:34:48.809 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:53.465
*** WARNING: Unable to verify timestamp for WinFLdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for WinFLdrv.sys
Probably caused by : WinFLdrv.sys ( WinFLdrv+1cf9 )
BUGCHECK_STR:  0xc2_9d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc2_9d_WinFLdrv+1cf9
Bugcheck code 000000C2
Arguments 00000000`0000009d 00000000`000007d0 00000000`00000001 fffff880`07df1cf9
BiosVersion = 6.00 PG
BiosReleaseDate = 01/15/2008
CPUID:        "Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2720
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050712-24500-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Mon May  7 10:28:26.945 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:39.554
*** WARNING: Unable to verify timestamp for WinFLdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for WinFLdrv.sys
Probably caused by : WinFLdrv.sys ( WinFLdrv+1cf9 )
BUGCHECK_STR:  0xc2_9d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc2_9d_WinFLdrv+1cf9
Bugcheck code 000000C2
Arguments 00000000`0000009d 00000000`000007d0 00000000`00000001 fffff880`07c0dcf9
BiosVersion = 6.00 PG
BiosReleaseDate = 01/15/2008
CPUID:        "Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2720
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

dimitris21 · 07 May 2012

The uguru has been uninstalled - as software - however,the guru system device is showing in device manager/system devices as uguru micrprocessor even though no software is installed for it at the moment,which is probably because it is actually the monitoring/sensor system of the abit motherboard.
I get the error in windows events that the driver for it doesn;t load as per below:
- System - Provider [ Name] Microsoft-Windows-Kernel-PnP [ Guid] {9C205A39-1250-487D-ABD7-E831C6290539}
EventID 219 Version 0 Level 3 Task 212 Opcode 0 Keywords 0x8000000000000000 - TimeCreated [ SystemTime] 2012-05-07T19:41:03.736328100Z
EventRecordID 259173 Correlation - Execution [ ProcessID] 4 [ ThreadID] 44
Channel System Computer Dimitris - Security [ UserID] S-1-5-18

- EventData DriverNameLength 25 DriverName ACPI\ABT2005\3&2411e6fe&1 Status 3221226092 FailureNameLength 13 FailureName \Driver\UGURU Version 0

I fixed the slight overclock - this board tends to raise the default clock by 1mhz after its boot if i have it set to auto cpu/spd - so the fsb went from the default of 266 to 267. I set it manually to 266 now so it will remain there for the process.

Regarding the Si3132 - unfortunately because the controller is dated,this driver is the only - and latest - driver available from the siliconimage website.It does however state that it is the one compatible with Win7.( http://www.siliconimage.com/support/...=32&cat=3&os=0 )

Are the drivers Siremfill.sys and SiWinacc.sys also related to the silicon image controller?
I removed folderlock from registry as it was the only place which was found into.
The winfldrv.sys is however still located at the syswow64 folder - should i remove it together with the the five - seperate from folder lock -instances in the registry?

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_WINFLDRV
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_WINFLDRV\0000
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_WINFLDRV\0000\Control

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\WinFLdrv
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\WinFLdrv\Enum
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\WinFLdrv\Instances
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\WinFLdrv\Instances\WinFLdrvFltr

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Enum\Root\LEGACY_WINFLDRV
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Enum\Root\LEGACY_WINFLDRV\0000

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\services\WinFLdrv
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\services\WinFLdrv\Instances

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_WINFLDRV

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WinFLdrv