Windows 7 BSOD Win7 Pro64 upgrade- Chrome Crash

[GeorgeR]

While surfing in Chrome I will get a BSOD (Flashes then reboot) Chrome will load fine and I can surf various lengths of time and various number of sites before I get the shut down / reboot. Any advice or help is welcomed. Thanks

 

[usasma]

No memory dumps and no MSINFO32.nfo uploaded. Please provide this information so we can provide a complete analysis: Link Removed If you have already run the app, please re-run it and let it run for at least 15 minutes (or until the app itself says that it's done). Then zip up the reports and upload them with your next post.

Just FYI - we have had problems with Killer network cards in the past. Be sure that you have the latest, Win8 compatible drivers for the card. I also suggest testing with another network card. They're fairly cheap (about $15 US at most major retailers) and it's good to have a spare on hand.

 

[GeorgeR]

Sorry about that let me try again.

also all 4 mem slots are the same as the slot 1 grab.

 

[usasma]

You have 4 hard drives. What is the make/model/wattage and age of your Power Supply?

SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:

1) That the SSD firmware is the latest available for the SSD
2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to.

Intel Ethernet card is disabled. I presume that this was done to use the Killer card. Please let us know if that was the case.

If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

No sign of any BSOD crashes in the WER section of MSINFO32 - and no uploaded memory dumps.
Please do this:

Upload Dump Files:
NOTE: If using a disk cleaning utility, please stop using it while we are troubleshooting your issues.
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service. Then post the link to it in your topic so that we can download it.

Also, search your entire hard drive for files ending in .dmp, .mdmp, and .hdmp. Zip up any that you find and upload them with your next post.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Link RemovedMore info on dump file options here: http://support.microsoft.com/kb/254649

While waiting for the next BSOD, start with these free hardware diagnostics: Link Removed

 

[GeorgeR]

Ultra X4 1050 watt 3 years old (MPN: U12-40502) only overclocking so to speak is Intel XMP for my RAM. also no minidump and searched and only came up with these files that are attached.

Will check all drivers but am sure they are the latest. C: drive is only 1 year old. Don't really need the other 2 WD drives if needed to remove.

yes Intel NIC was disabled for Bigfoot.

 

[usasma]

While helpful, the .dmp files that you found are older (the most recent is from 21 May)
All are STOP 0x117's - which normally don't even show the BSOD (just a little notice that your video driver has recovered from a crash).

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).

Please un-install 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): [DEL] Link Removed [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

Please try these steps for troubleshooting the STOP 0x117 errors: Video TDR Timeout - 0x116 + 0x117 - Sysnative Forums

Killer card drivers date from 2011. I suggest:
1) Trying updated drivers if available
2) Trying another NIC card (they're only $15 US at most major retailers - and it's a good idea to have a spare on hand just in case you need it).

McAfee appears in each memory dump. While this may not be significant, you can test it this way:

Anti-Virus Removal:
Please do the following:
- download a free anti-virus for testing purposes: Link Removed If using Windows 8, enable Windows Defender and the Windows Firewall instead.
- un-install the McAfee from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of McAfee using this free tool: Link Removed (This link has changed a lot. If it doesn't work, search for McAfee Consumer Products Removal Tool)
- IMMEDIATELY install and update the free anti-virus (if using Win8, enable Windows Defender), then check to ensure that the Windows Firewall is turned on.
- perform a full system scan to ensure that no malware has snuck onto your system while the anti-virus was malfunctioning.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

LHidFilt.Sys Wed Apr 22 20:05:22 2009 (49EFB0C2)
Logitech SetPoint HID Filter Driver
Link Removed

LMouFilt.Sys Wed Apr 22 20:05:26 2009 (49EFB0C6)
Logitech SetPoint HID Filter Driver
Link Removed

If all of this doesn't stop the BSOD's, please run these free hardware diagnostics: Link Removed. Let us know the results and we can move on from there.




Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Tue May 21 10:15:09.504 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\WD-20130521-1015.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]4 days 18:14:04.913[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+14ba88 )[/B]
BugCheck [B]117, {fffffa80121fd1b0, fffff880057b7a88, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa80121fd1b0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880057b7a88, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
BUGCHECK_STR:  0x117
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x117_IMAGE_nvlddmkm.sys[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Feb 12 01:15:22.019 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\WD-20130212-0015.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]3 days 4:01:23.519[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+14ba88 )[/B]
BugCheck [B]117, {fffffa8011c854e0, fffff88003380a88, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa8011c854e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003380a88, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
BUGCHECK_STR:  0x117
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x117_IMAGE_nvlddmkm.sys[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 16 19:15:22.232 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\WD-20130116-1815.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]2 days 3:46:51.122[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+14ba88 )[/B]
BugCheck [B]117, {fffffa8013527390, fffff880031fba88, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa8013527390, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880031fba88, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
BUGCHECK_STR:  0x117
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x117_IMAGE_nvlddmkm.sys[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Oct 14 19:58:18.460 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\WD-20121014-1958.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]1 days 12:10:50.350[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+1af0dc )[/B]
BugCheck [B]117, {fffffa80118e1010, fffff880031e70dc, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa80118e1010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880031e70dc, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
BUGCHECK_STR:  0x117
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x117_IMAGE_nvlddmkm.sys[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Tue May 21 10:15:09.504 2013 (UTC - 4:00)**************************
[COLOR=RED][B]LHidFilt.Sys       Wed Apr 22 20:05:22 2009 (49EFB0C2)[/B][/COLOR]
[COLOR=RED][B]LMouFilt.Sys       Wed Apr 22 20:05:26 2009 (49EFB0C6)[/B][/COLOR]
intelppm.sys       Mon Jul 13 19:19:25 2009 (4A5BC0FD)
intelsmb.sys       Tue Jan 19 22:27:18 2010 (4B567816)
amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
vpcnfltr.sys       Sat Nov 20 06:35:20 2010 (4CE7B278)
vpcusb.sys         Sat Nov 20 06:35:31 2010 (4CE7B283)
vpchbus.sys        Sat Nov 20 06:35:38 2010 (4CE7B28A)
vpcvmm.sys         Sat Nov 20 06:35:48 2010 (4CE7B294)
Edge7x64.sys       Wed May 18 18:55:15 2011 (4DD44E53)
Xeno7x64.sys       Wed May 18 18:55:16 2011 (4DD44E54)
[COLOR=RED][B]dtsoftbus01.sys    Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
nvhda64v.sys       Tue Jan 17 07:45:46 2012 (4F156D7A)
MpFilter.sys       Fri Mar  9 06:05:26 2012 (4F59E3F6)
RTKVHD64.sys       Tue Mar 27 05:01:50 2012 (4F7181FE)
nvlddmkm.sys       Tue Oct  2 14:21:13 2012 (506B3099)
mfehidk.sys        Tue Jan 15 13:21:15 2013 (50F59E1B)
mfewfpk.sys        Tue Jan 15 13:21:30 2013 (50F59E2A)
mfeapfk.sys        Tue Jan 15 13:21:56 2013 (50F59E44)
mfeavfk.sys        Tue Jan 15 13:22:16 2013 (50F59E58)
mfefirek.sys       Tue Jan 15 13:24:04 2013 (50F59EC4)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Feb 12 01:15:22.019 2013 (UTC - 4:00)**************************
IOCBIOS.sys        Wed Feb  3 14:41:29 2010 (4B69D169)
pneteth.sys        Fri Nov 25 00:25:50 2011 (4ECF26DE)
e1k62x64.sys       Thu Feb  2 04:42:59 2012 (4F2A5AA3)
mfehidk.sys        Tue Dec 18 19:25:11 2012 (50D10967)
mfewfpk.sys        Tue Dec 18 19:25:26 2012 (50D10976)
mfeapfk.sys        Tue Dec 18 19:25:52 2012 (50D10990)
mfeavfk.sys        Tue Dec 18 19:26:11 2012 (50D109A3)
mfefirek.sys       Tue Dec 18 19:27:59 2012 (50D10A0F)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 16 19:15:22.232 2013 (UTC - 4:00)**************************
mfehidk.sys        Tue Nov  6 17:47:12 2012 (50999370)
mfewfpk.sys        Tue Nov  6 17:47:27 2012 (5099937F)
mfeapfk.sys        Tue Nov  6 17:47:56 2012 (5099939C)
mfeavfk.sys        Tue Nov  6 17:48:17 2012 (509993B1)
mfefirek.sys       Tue Nov  6 17:50:08 2012 (50999420)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Oct 14 19:58:18.460 2012 (UTC - 4:00)**************************
mfehidk.sys        Mon Feb 13 18:36:14 2012 (4F399E6E)
mfewfpk.sys        Mon Feb 13 18:36:29 2012 (4F399E7D)
mfenlfk.sys        Mon Feb 13 18:36:45 2012 (4F399E8D)
mfeapfk.sys        Mon Feb 13 18:37:01 2012 (4F399E9D)
mfeavfk.sys        Mon Feb 13 18:37:27 2012 (4F399EB7)
mfefirek.sys       Mon Feb 13 18:40:07 2012 (4F399F57)
nvlddmkm.sys       Wed Feb 29 13:04:52 2012 (4F4E68C4)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed