Random BSOD in Windows 7 64 bit

Don't stop secdrv.sys, please re-enable it.
It's a component of the Windows operating system and is necessary (but is rarely updated).
I normally remove it from listings that I post - I must've goofed on this one! Sorry!

I'm unsure if it caused this BSOD - but it may have. So please wait and see if you get another one after re-enabling secdrv.sys.

Summary of the BSOD:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jan 13 20:27:44.391 2010 (GMT-5)
System Uptime: 0 days 4:23:36.983
BugCheck 50, {fffffffffffffff5, 0, fffff8000316256d, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe

Essentially the same thing as the previous memory dump. Please run Driver Verifier using these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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/Win7 Startup Repair feature).

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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Here's a summary of the BSOD:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan 14 18:41:03.191 2010 (GMT-5)
System Uptime: 0 days 2:24:39.158
BugCheck 1000007E, {ffffffffc0000005, fffff800031ac1fc, fffff880031c4988, fffff880031c41e0}
Probably caused by : ntkrnlmp.exe ( nt!CmpRemoveKeyHash+4c )
PROCESS_NAME:  System
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

The Driver Verifier dump blames oa002ufd.sys - a component of your Creative Camera OA002 Upper Filter Driver. Please note that these drivers are also listed in the list of older drivers below.

Please do the following:
- download the latest version of the Camera drivers from the Creative website (Creative Worldwide Support)
- uninstall the current drivers on your system
- install the freshly downloaded drivers
- monitor for further BSOD's

Also, Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:

How To Find Updated Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- some driver links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers:

Code:

000.fcl      Fri Sep 26 09:11:22 2008 -  CyberLink FCL Driver or My Book Device Driver by Cyberlink Corp (CyberLink ? PowerDVD sales - Media Suite 8 Multimedia Software).
npusbio_x64.sys Wed Apr 11 07:44:53 2007 - NaturalPoint\Optitrack driver
OA002Afx.sys Fri Jun 08 04:00:36 2007 - Creative Camera driver
OA002Ufd.sys Tue Jun 03 05:30:37 2008 - Creative Camera driver
OA002Vid.sys Fri Aug 01 05:34:52 2008 - Creative Camera driver
PxHlpa64.sys Wed Oct 17 14:25:02 2007 - Driver for a CD/DVD burning program
RtNdPt60.sys Mon Dec 10 21:49:52 2007 -Netgear GA511 Driver file

Summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 15 21:12:38.900 2010 (GMT-5)
System Uptime: 0 days 0:01:16.523
BugCheck C4, {f6, 260, fffffa800923cb30, fffff880039106cb}
*** WARNING: Unable to verify timestamp for OA002Ufd.sys
*** ERROR: Module load completed but symbols could not be loaded for OA002Ufd.sys
Probably caused by : OA002Ufd.sys ( OA002Ufd+266cb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WebcamDell2.ex
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 15 21:15:31.498 2010 (GMT-5)
System Uptime: 0 days 0:00:12.495
BugCheck D3, {fffff880012ab057, 2, 0, fffff80002ebbf62}
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System