Windows 7 Looking for Assistance with Blue Screen

trkr81 · Jul 12, 2013

Link Removed

I've included as much information as possible. There is also a README file in the .zip folder that may be of some help to you.

I'm very grateful for the time you folks take in helping people. Thank you.

If you need anything further, I'll do my best to get it to you asap.

usasma · Jul 13, 2013

Only 113 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

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.

Your Intel RAID storage driver (iaStorV.sys) dates from before mid-2013 (actually it's from 2010) and should be updated. Try this driver (I got this link on 10 Jul 2013):
Link Removed
Use the SetupRST.exe file - the other 2 are the "preinstall" drivers for use when first installing an OS that doesn't have these drivers. If it doesn't install, post back and I'll research it further.

The devices have problems in Device Manager:

ViXS PureTV-U 48B8 (NTSC/ATSC Combo) PCI\VEN_1745&DEV_2100&SUBSYS_48B81043&REV_00\6&2A53C5E2&0&000800E7 This device is disabled.

PCI Simple Communications Controller PCI\VEN_8086&DEV_1E3A&SUBSYS_84CA1043&REV_04\3&11583659&0&B0 The drivers for this device are not installed.

BCM20702A0 USB\VID_0B05&PID_17B5\0008CAE5C63F The drivers for this device are not installed.

VMLite Host-Only Ethernet Adapter ROOT\NET\0000 This device is disabled.

The first one is a TV controller and it's disabled. Is this deliberate? If so, why?
The second one is most likely the Intel Management Engine Interface and needs to be installed
The third one is most likely your Broadcom USB Bluetooth device and it needs to have drivers installed
The last one is your VMLite ethernet adapter which is disabled? Is this deliberate? If so, why?

While all the memory dumps are STOP 0x3B's and all blame your ATI video drivers, I have to wonder about hardware issues due to your explanation in the readme.txt file

Please un-install the current ATI video drivers, then download and install the latest version from Link Removed If that doesn't stop the BSOD's, then try the video stress tests from here: Link Removed

Also, you may want to consider posting in a video/hardware forum to get advice from video card experts.

Analysis:
The following is for informational purposes only.

Code:

[FONT=lucida console]**************************Thu Jul 11 23:38:01.083 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071113-12448-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:01:15.864[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+14bd95 )[/B]
BugCheck [B]3B, {c0000005, fffff880059bed95, fffff880099b6210, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880059bed95, Address of the instruction which caused the bugcheck
Arg3: fffff880099b6210, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_atikmdag+14bd95[/B]
CPUID:        "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3417[/B]
  BIOS Version                  2003
  BIOS Release Date             05/09/2013
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jul 11 23:36:25.973 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071113-12183-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 1:33:02.643[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+14bd95 )[/B]
BugCheck [B]3B, {c0000005, fffff880059afd95, fffff88009db8210, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880059afd95, Address of the instruction which caused the bugcheck
Arg3: fffff88009db8210, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_atikmdag+14bd95[/B]
CPUID:        "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3417[/B]
  BIOS Version                  2003
  BIOS Release Date             05/09/2013
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jul 11 22:02:40.380 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071113-12370-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]1 days 5:26:12.161[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+14bd95 )[/B]
BugCheck [B]3B, {c0000005, fffff88005951d95, fffff8800a011210, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88005951d95, Address of the instruction which caused the bugcheck
Arg3: fffff8800a011210, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_atikmdag+14bd95[/B]
CPUID:        "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3417[/B]
  BIOS Version                  2003
  BIOS Release Date             05/09/2013
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul  8 20:59:14.414 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070813-12308-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:17:26.194[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+14bd95 )[/B]
BugCheck [B]3B, {c0000005, fffff880057cdd95, fffff8800b85f210, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880057cdd95, Address of the instruction which caused the bugcheck
Arg3: fffff8800b85f210, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  CCC.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_atikmdag+14bd95[/B]
CPUID:        "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3417[/B]
  BIOS Version                  2003
  BIOS Release Date             05/09/2013
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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.

Code:

[FONT=lucida console]**************************Thu Jul 11 23:38:01.083 2013 (UTC - 4:00)**************************
intelppm.sys       Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
vmlitedrv.sys      Tue Aug  3 23:27:59 2010 (4C58DE3F)
VBoxNetFlt.sys     Wed Aug 11 17:28:32 2010 (4C631600)
VBoxDrv.sys        Wed Aug 11 17:28:44 2010 (4C63160C)
vmlitestor.sys     Wed Aug 11 21:37:24 2010 (4C635054)
vmliteusbmon.sys   Wed Aug 18 15:29:34 2010 (4C6C349E)
bcmvwl64.sys       Mon Nov 22 08:58:19 2010 (4CEA76FB)
NuidFltr.sys       Fri Apr  8 18:58:16 2011 (4D9F9308)
mvxxmm.sys         Mon Sep 19 07:31:37 2011 (4E772819)
mvs91xx.sys        Mon Sep 19 07:31:51 2011 (4E772827)
mv91cons.sys       Mon Sep 19 07:36:08 2011 (4E772928)
asmtxhci.sys       Wed Nov  2 23:00:22 2011 (4EB203C6)
asmthub3.sys       Wed Nov  2 23:00:32 2011 (4EB203D0)
IntcDAud.sys       Tue Dec  6 06:23:07 2011 (4EDDFB1B)
asahci64.sys       Thu Jan  5 00:08:19 2012 (4F053043)
bcmwl664.sys       Mon Feb  6 22:01:16 2012 (4F3093FC)
BCM42RLY.sys       Tue Feb 21 02:41:04 2012 (4F434A90)
igdkmd64.sys       Mon Mar 26 22:09:46 2012 (4F71216A)
Rt64win7.sys       Wed Apr 11 12:29:16 2012 (4F85B15C)
iusb3hub.sys       Mon May 21 03:21:36 2012 (4FB9ED00)
iusb3xhc.sys       Mon May 21 03:21:40 2012 (4FB9ED04)
iusb3hcs.sys       Mon May 21 03:23:42 2012 (4FB9ED7E)
busenum.sys        Fri Aug  3 05:32:04 2012 (501B9A94)
RTKVHD64.sys       Tue Aug  7 06:49:39 2012 (5020F2C3)
AsIO.sys           Wed Aug 22 05:54:47 2012 (5034AC67)
dc3d.sys           Tue Sep 18 06:18:24 2012 (50584A70)
point64.sys        Sun Nov 25 21:24:47 2012 (50B2D2EF)
AtihdW76.sys       Thu Feb 14 17:11:09 2013 (511D60FD)
e1c62x64.sys       Thu Feb 21 00:14:02 2013 (5125AD1A)
VirtuWDDM.sys      Tue Mar  5 11:06:31 2013 (51361807)
atikmpag.sys       Thu Mar 28 21:09:45 2013 (5154E9D9)
atikmdag.sys       Thu Mar 28 22:27:04 2013 (5154FBF8)
MpFilter.sys       Fri Jun  7 19:01:11 2013 (51B26637)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul  8 20:59:14.414 2013 (UTC - 4:00)**************************
MpFilter.sys       Wed Oct 31 18:43:06 2012 (5091A97A)
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
vmlitestor.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
vmliteusbmon.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
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
busenum.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

trkr81 · Jul 14, 2013

Hi John,

According to your advice, this is what I have done so far...

Stress Test:
MemTest86 = No errors
Furmark = No shutdown occurred. 7909 Frames, 8 FPS, 81 degrees C (15 minute burn-in / benchmark).

Updates:
All Windows updates have been installed (including optional updates).
The SSD firmware is "up to date" according to the Samsung Magician software.
The latest motherboard storage controller driver (Intel RST) has been installed.
The TV Tuner (ViXS PureTV-U 48B8) has been removed from the hardware. We never use it.
Intel Management Engine has been installed.
ASUS Intel Management Engine firmware has been updated.
Latest Intel 4000 graphics have been installed. (We used the Intel driver update utlity).
Bluetooth drivers have been installed.
VMLite NIC has been enabled. (I disabled that previously to troubleshoot something else).
Before posting this thread, I uninstalled / re-installed the drivers for the video card.

After following the steps above, I was still able to reproduce the BSOD. However, I was also able to prevent it.

When all three monitors are connected (2) using the GPU, and (1) using the iGPU... the BSOD occurs randomly when launhcing or using Camtasia. However, when I disconnect the on-board iGPU cable, and use only the video card connected monitors, I am unable to reproduce the BSOD.

It's almost as if the software get's confused which GPU is in charge. Camtasia has the option "Use GPU accelleration if available". I'm not certain this is the culprit. But it's looking like I'll need a different video card capable of handling all of my monitors without using any of the on-board iGPU ports (if I plan to use this software).

By, the way, thank you for such a detailed report. I do appreciate you taking the time to do so. I certainly welcome any thoughts you might have.

usasma · Jul 14, 2013

VMLite NIC has been enabled. (I disabled that previously to troubleshoot something else).

What was the issue that you were troubleshooting? Was it resolved?

My ideas are limited to:
- faulty Camtasia software. Either a corruption in the current installation, or a problem with the software in this scenario. Un-installing/reinstalling a fresh copy of the software will help to rule out corruption.
- cabling issues. Try different cables
- video card issues. Try stress tests (Link Removed - see the 2 video card test sections) and try another card

As I stated before, I'm not real adept with video card issues. My usual solution is to just throw a new card in and see if there's still a problem. You could always purchase a new card from a place that accepts returns and try it. If it doesn't fix the issues you can always return the card for your money back.

Good luck!

Search

Navigation section

Windows 7 Looking for Assistance with Blue Screen

trkr81

New Member

usasma

usasma

Fantastic Member

trkr81

New Member

usasma

Fantastic Member

Similar threads