Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Seemingly Random dxgkrnl.sys BSODs

22 Sep 2010   #1
amf66

Windows 7 64-bit
 
 
Seemingly Random dxgkrnl.sys BSODs

Hello. After a few months of no problems thanks to some great people on this forum I'm having problems again. In the past few days I've had at least 4 blue screens. Remembering what someone recommended I uninstalled my video card drivers, used Driver Sweeper to get rid of any remnants, and reinstalled the latest 10.9 drivers. Unfortunately, I'm still having blue screens. One thing that I have noticed is that all of the blue screens reference dxgkrnl.sys. I'm running Windows 7 64-bit.

Thanks for any help!


My System SpecsSystem Spec
.
23 Sep 2010   #2
usasma
Microsoft MVP

 
 

Please install the device drivers for your USB20 camera. The perfmon report shows:
Quote:
The device driver for USB20 Camera has not been installed
The memory dump files seem to indicate that this is a hardware problem. The dump files date back to Nov 09. Have you done anything to fix the blue screens prior to the last 4 that occurred? If so, what did you do?

The BSOD from 18 August 2010 blames snman462.sys This is most likely a component of Acronis True Image. Please uninstall that program, then check in C:\Windows\System32\drivers to ensure that snman462.sys is gone. If not, rename it from .sys to .BAK, then reboot to ensure it doesn't respawn itself.

Also, please remove or update 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 currently available drivers to replace the one's that you uninstall OR remove:
Quote:
How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those 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.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: Driver Reference ).
Please pay particular attention to any dated 2008 or earlier:
Code:

timntr.sys   Fri Sep 12 10:49:48 2008 - Acronis True Image Backup Archive Explorer - http://www.carrona.org/dvrref.html#timntr.sys
RtNdPt60.sys Mon Dec 10 21:49:52 2007 - Netgear GA511 Driver file (Realtek chipset) - http://www.carrona.org/dvrref.html#RtNdPt60.sys
AsIO.sys     Mon Dec 17 04:11:49 2007 - Asus PCProbe Utility - http://www.carrona.org/dvrref.html#AsIO.sys
Afc.sys      Wed Jul 12 01:48:20 2006 - Arcsoft(R) ASPI Shell (CD/DVD program) - http://www.carrona.org/dvrref.html#Afc.sys
tifsfilt.sys Fri Sep 12 10:50:44 2008  - Acronis True Image FS Filter - http://www.carrona.org/dvrref.html#tifsfilt.sys
RTCore64.sys Wed May 25 02:39:12 2005 - RivaTuner/EVGA Precision (issues w/Win7) - http://www.carrona.org/dvrref.html#RTCore64.sys
SNCAMD.SYS   Mon Nov 13 04:27:05 2006 - USB 2.0 PC Camera (SN9C201) driver - http://www.carrona.org/dvrref.html#SNCAMD.SYS
mv2.sys      Wed Feb 06 16:02:40 2008 - UltraVnc miniport driver2 - http://www.carrona.org/dvrref.html#mv2.sys
If that doesn't stop the BSOD's, then Sep 2010 BSOD's may indicate another problem - so please run Driver Verifier according to these instructions:
Quote:
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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

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:
Code:
Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 22 22:43:54.704 2010 (UTC - 4:00)
System Uptime: 0 days 1:58:34.040
Probably caused by : memory_corruption
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`044e61fa fffff880`09597278 fffff880`09596ae0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 21:28:12.461 2010 (UTC - 4:00)
System Uptime: 1 days 1:54:36.608
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  UT2004.exe
Bugcheck code 00000050
Arguments fffff100`088ea2d0 00000000`00000001 fffff880`04475176 00000000`00000007
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 12 20:43:21.580 2010 (UTC - 4:00)
System Uptime: 1 days 2:40:12.906
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
Bugcheck code 1000009F
Arguments 00000000`00000004 00000000`00000258 fffffa80`03a03b60 fffff800`04bae510
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 18 15:41:01.685 2010 (UTC - 4:00)
System Uptime: 0 days 0:11:34.981
*** WARNING: Unable to verify timestamp for snman462.sys
*** ERROR: Module load completed but symbols could not be loaded for snman462.sys
Probably caused by : snman462.sys ( snman462+260fb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  msiexec.exe
Bugcheck code 0000000A
Arguments 00000000`00000138 00000000`00000002 00000000`00000000 fffff800`0326adec
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Aug 17 14:41:31.201 2010 (UTC - 4:00)
System Uptime: 0 days 1:33:10.902
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff880`044d417c fffff880`0b37b040 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  9 20:18:18.871 2010 (UTC - 4:00)
System Uptime: 1 days 0:31:47.572
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`045ad176 fffff880`0b33beb8 fffff880`0b33b720
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 15 19:08:52.851 2010 (UTC - 4:00)
System Uptime: 1 days 1:47:27.400
Probably caused by : NETIO.SYS ( NETIO!WfppIncrementIndexAndPurgeEntries+166 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0183c491 fffff880`035b68a8 fffff880`035b6110
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 13 17:39:38.701 2010 (UTC - 4:00)
System Uptime: 2 days 2:40:23.743
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
Bugcheck code 1000009F
Arguments 00000000`00000004 00000000`00000258 fffffa80`03a18b60 fffff800`00b9c510
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 21 18:18:48.982 2010 (UTC - 4:00)
System Uptime: 3 days 0:52:12.853
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmIsAllocationTerminated+14 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Crysis.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`04401e30 fffff880`08b82070 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 17 22:29:23.864 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:18.206
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0511e038 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Apr 29 15:34:50.799 2010 (UTC - 4:00)
System Uptime: 0 days 22:24:39.110
Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+40 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  CCleaner.exe
Bugcheck code 0000000A
Arguments 00000000`00000058 00000000`00000002 00000000`00000000 fffff800`031359b0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 17 16:16:24.021 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:00.254
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CINEBENCH R10 
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`059e3028 00000000`b669c000 00000000`00000135
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 16 22:16:30.770 2010 (UTC - 4:00)
System Uptime: 0 days 2:03:04.440
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`04b88028 00000000`b66b4000 00000000`00000135
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 16 20:03:06.895 2010 (UTC - 4:00)
System Uptime: 1 days 2:11:28.580
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SETUP.EXE
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`055e5028 00000000`b669c000 00000000`00000135
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan 14 23:08:45.373 2010 (UTC - 4:00)
System Uptime: 1 days 5:36:51.059
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  TrueImageHomeS
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec 29 19:15:14.829 2009 (UTC - 4:00)
System Uptime: 0 days 3:43:15.125
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Steam.exe
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`05a20028 00000000`b66d4000 00000000`00000135
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Nov  4 22:51:05.218 2009 (UTC - 4:00)
System Uptime: 3 days 7:21:26.558
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+e7220 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
Bugcheck code 00000116
Arguments fffffa80`0af974e0 fffff880`04b66220 00000000`00000000 00000000`00000002
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
23 Sep 2010   #3
amf66

Windows 7 64-bit
 
 

Thanks for the quick reply! I fixed the previous blue screens by replacing the RAM since it was faulty and failed Memtest86. I've installed the drivers for the webcam, updated the Realtek driver, and gotten rid of the old drivers that are used by programs I don't have installed anymore (Acronis, UltraVNC, Rivatuner). However, I can't find what uses Afc.sys and how to update this driver. Can someone help me with this? Also, The last few crashes in the BSOD summary say that they were probably caused by memory corruption. Could this be a sign that my RAM has gone bad already? I just replaced it last month.

Thanks for the help!

Edit: Also, the driver for Asus PC Probe, AsIO.sys, isn't in the drivers folder and when I searched for it I didn't get any results. Could a cheap or faulty PSU be the cause of my blue screens? I've always regretted going with an off-brand PSU since I built this computer last year and wondered if it could be causing my problems.
My System SpecsSystem Spec
.

24 Sep 2010   #4
usasma
Microsoft MVP

 
 

To find drivers that don't have much information (like this copy of AFC.sys) the simplest method is to rename the driver from .sys to .BAK Then use all CD/DVD programs and find out which one is broken - that's likely to be the one that the driver belongs to. Rename the .BAK to .sys to see if it works again.

Anything is possible - and I always suggest going with overkill on a new PSU. Also use a well-known and respected brand, some of the off-the-wall brands aren't known for their ability to provide what they advertise.
Purchase a PSU from a store with a good return policy - then you can return it if it doesn't solve your issues.

In most cases RAM doesn't go bad over time. It takes power surges or other adverse conditions (such as heat) to make it go bad. That's why the reputable manufacturer's offer a lifetime warranty.

Because I ran all of the dump files, it's possible that the AsIO.sys file was in an earlier dump - and that you removed the program already. Just keep an eye out for it in future dumps.
My System SpecsSystem Spec
24 Sep 2010   #5
amf66

Windows 7 64-bit
 
 

Thanks, I'll see if I have any more crashes and consider buying a new PSU. I'll run Memtest tonight.

Edit: So it is possible for a bad PSU to kill RAM?
My System SpecsSystem Spec
24 Sep 2010   #6
usasma
Microsoft MVP

 
 

I'd say it was, but I haven't seen a PSU that kills RAM (that'd be easy to identify as all new RAM would be fried as soon as the system was turned on).

More likely is a power surge (through the power supply) that fries the RAM.
Or, overheating/overclocking may do it.
Have you run MemTest again? Does it show that the RAM is bad?
My System SpecsSystem Spec
24 Sep 2010   #7
amf66

Windows 7 64-bit
 
 

I have not run Memtest again yet. I DID, however, just have a BSOD when I plugged in my iPod to charge it. I'll post a crash dump as soon as I can.

The voltage on my 12V rail is 12.8V, is that cause for concern?

Edit: Uploaded the latest crash dumps.
My System SpecsSystem Spec
24 Sep 2010   #8
usasma
Microsoft MVP

 
 

I have no clue about voltages on PSU's - I'd use the results of MemTest to draw a conclusion about the voltages (if the RAM is OK, then I wouldn't worry about the voltage).

This memory dump points at your Acronis software. Please uninstall it until we're finished troubleshooting. It is outdated so I'd also suggest purchasing a newer copy.

Here's the dump files and then the listing of the drivers. Please fix them as requested in my previous post:
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 24 17:32:39.141 2010 (UTC - 4:00)
System Uptime: 1 days 18:47:12.268
*** WARNING: Unable to verify timestamp for timntr.sys
*** ERROR: Module load completed but symbols could not be loaded for timntr.sys
Probably caused by : timntr.sys ( timntr+2c46a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
Bugcheck code 1000007E
Arguments ffffffff`c000001d fffffa80`048bf8e6 fffff880`035a1418 fffff880`035a0c80
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
Code:


mv61xx.sys   Thu Mar 19 23:48:21 2009 (49C31205)
amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
iaStorV.sys  Wed Apr 08 12:57:17 2009 (49DCD76D)
MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
timntr.sys   Fri Sep 12 10:49:48 2008 (48CA818C)
AtiPcie.sys  Mon Aug 24 04:25:26 2009 (4A924E76)
tdrpm228.sys Wed Apr 15 11:08:50 2009 (49E5F882)
snapman.sys  Wed Mar 25 04:49:15 2009 (49C9F00B)
vmm.sys      Thu Jan 21 05:38:48 2010 (4B582EB8)
n VBoxUSBMon.sys Fri Jun 25 09:32:28 2010 (4C24AFEC)
VBoxDrv.sys  Fri Jun 25 09:32:28 2010 (4C24AFEC)
RtNdPt60.sys Mon Dec 10 21:49:52 2007 (475DFAD0)
ElbyCDIO.sys Tue Feb 17 12:11:23 2009 (499AEFBB)
AsIO.sys     Mon Dec 17 04:11:49 2007 (47663D55)
atikmpag.sys Wed Aug 25 21:20:56 2010 (4C75C178)
t VBoxNetFlt.sys Fri Jun 25 09:32:28 2010 (4C24AFEC)
WmXlCore.sys Fri Sep 11 15:40:07 2009 (4AAAA797)
p VBoxNetAdp.sys Fri Jun 25 09:32:28 2010 (4C24AFEC)
hamachi.sys  Thu Feb 19 05:36:41 2009 (499D3639)
VClone.sys   Fri May 22 19:08:37 2009 (4A173075)
WmBEnum.sys  Fri Sep 11 15:40:09 2009 (4AAAA799)
Afc.sys      Wed Jul 12 01:48:20 2006 (44B48D24)
DM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
ASACPI.sys   Wed May 13 21:25:17 2009 (4A0B72FD)
tifsfilt.sys Fri Sep 12 10:50:44 2008 (48CA81C4)
atikmdag.sys Wed Aug 25 21:47:22 2010 (4C75C7AA)
btusbflt.sys Thu Apr 08 21:11:36 2010 (4BBE7EC8)
BTHUSB.sys   Mon Jul 13 20:06:52 2009 (4A5BCC1C)
bthport.sys  Mon Jul 13 20:06:56 2009 (4A5BCC20)
AtihdW76.sys Thu Jul 15 08:46:49 2010 (4C3F0339)
viahduaa.sys Sat May 15 06:22:39 2010 (4BEE75EF)
bthpan.sys   Mon Jul 13 20:07:00 2009 (4A5BCC24)
bthmodem.sys Mon Jul 13 20:06:52 2009 (4A5BCC1C)
sftvollh.sys Wed Sep 23 14:45:45 2009 (4ABA6CD9)
netr7364.sys Thu Mar 12 23:13:08 2009 (49B9CF44)
point64k.sys Fri Oct 16 16:08:03 2009 (4AD8D2A3)
rfcomm.sys   Mon Jul 13 20:06:56 2009 (4A5BCC20)
BthEnum.sys  Mon Jul 13 20:06:52 2009 (4A5BCC1C)
sftfslh.sys  Wed Sep 23 14:45:57 2009 (4ABA6CE5)
64 cpuz132_x64.sys Thu Mar 26 19:17:23 2009 (49CC0D03)
WmVirHid.sys Fri Sep 11 15:40:05 2009 (4AAAA795)
SECDRV.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
MpNWMon.sys  Sat Mar 20 01:58:00 2010 (4BA463E8)
 sftplaylh.sys Wed Sep 23 14:46:16 2009 (4ABA6CF8)
h Sftredirlh.sys Wed Sep 23 14:46:24 2009 (4ABA6D00)
2 AODDriver2.sys Wed May 05 00:03:12 2010 (4BE0EE00)
Rt64win7.sys Thu Aug 20 12:05:06 2009 (4A8D7432)
SNCAMD.SYS   Thu Jan 25 05:48:38 2007 (45B88B06)
snp2sxp.sys  Tue Feb 12 22:35:44 2008 (47B26590)
STREAM.SYS   Mon Jul 13 20:06:18 2009 (4A5BCBFA)
My System SpecsSystem Spec
24 Sep 2010   #9
amf66

Windows 7 64-bit
 
 

I uninstalled Acronis about a month ago when I was having blue screens, but it seems that some of the drivers were left behind. I renamed them to "*.bak" and I have updated or gotten rid of all the over drivers you listed in your previous post (some of them were missing). However, SNCAMD.sys is necessary for my webcam to work, and I have updated it to the latest drivers. It's still old, but hopefully that won't cause any more bluescreens. Are there any other drivers you think I should update?

Thank you for all the help!
My System SpecsSystem Spec
25 Sep 2010   #10
usasma
Microsoft MVP

 
 

I'd suggest waiting to see if the BSOD's stop.
My System SpecsSystem Spec
Reply

 Seemingly Random dxgkrnl.sys BSODs




Thread Tools




Similar help and support threads
Thread Forum
Seemingly random BSODs
Getting BSODs at random, but it seems as though most of the time it's because I alt tab into or out of a full screen program. This might of course be confirmation bias. Got this when I logged back on, maybe it can help: BCCode: 3b BCP1: 00000000C0000005 BCP2: FFFFF96000164283 ...
BSOD Help and Support
Seemingly random BSODs
Hi, I've been experiencing BSODs for a couple of months, but they seem to be getting more frequent recently. It's mostly when I'm running several programs (but not games), but other than that I haven't noticed anything particular. Sorry not to be more specific - I'd be really grateful for any...
BSOD Help and Support
Random BSODs: ntoskrnl, dxgkrnl, dxgmms1, nvlddmkm, BCCode 116
Hi Guys. I'd appreciate some help here. I've been getting BSODs for quite a while now and would like some help in finding a solution. Attached is my SF zip. Looking at the dmp files, it seems it's either ntoskrnl or (dxgkrnl, dxgmms1, nvlddmkm). I have no idea what this means.
BSOD Help and Support
Seemingly random BSODs
For a while I've been having some seemingly random BSODs with my new Win7 Hope Premium install. I did have a severe problem with them a while ago but a reformat seemed to help. Unfortunately BSODs seem to have been returned albeit not as bad as with my previous installation (I guess it is a driver...
BSOD Help and Support
Seemingly random BSODs?
Okay, so I *thought* my computer was fine, but yesterday it started p*ssing me off again. What a surprise... If you knew how many BSODs this friggin system has gone through, you would be surprised. Anyway, I've gotten 2 BSODs since I thought it was fixed. No minidump files have been produced and...
BSOD Help and Support
Seemingly Random BSODs
I have just built this computer and now i'm getting random BSODs. These are all fresh components except of a recycled video card. I've installed all motherboard drivers except for jmicron jmb36x driver which causes problems with my CD-Drive. Anyways these BSODs happen about 3 times a week,...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 04:24.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App