Windows 7 BSOD every 1-4 weeks on Win7 / Asus UL80JT-A1

[AsusUser]

BSD every 1-4 weeks... sometimes more often.

I would appreciate any insight.

I have uploaded the requested files (minus both evt logs - which although they are below the file size limit - have been giving me problems with the uploads).

Please advise if you need to evt logs. I can try to either make them smaller to upload or use any other method you suggest.

Running Symantec A/V.

Thank you.

Mitch



OS Name: Microsoft Windows 7 Home Premium
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Original Install Date: 9/24/2010, 3:04:47 PM
System Boot Time: 7/13/2013, 6:05:15 AM
System Manufacturer: ASUSTeK Computer Inc.
System Model: UL80Jt
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 37 Stepping 5 GenuineIntel ~1199 Mhz
BIOS Version: American Megatrends Inc. UL80Jt.211, 5/31/2010

 

[usasma]

For now just hang onto the event logs. Since they're so big, please do this:

Please do the following:
- open Event Viewer (eventvwr.msc)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

The MSINFO32 file is corrupt and can't be opened. I suspect that this is because of the size of the WER reports (which is probably large because your event logs are large). We need this report, so please rerun the collection app and let it run for at least 15 minutes (or until the app itself tells you that it's finished). Then zip it up and upload it again.

Please visit the Asus website for your system and update all of the drivers.

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! :

ATK64AMD.sys Tue May 12 21:04:54 2009 (4A0A1CB6)
ATK Hotkey ATK0101 ACPI UTILITY Driver
Link Removed

ASMMAP64.sys Thu Jul 2 05:13:26 2009 (4A4C7A36)
LENOVO ATK Hotkey ATK0101 ACPI UTILITY
Link Removed

kbfiltr.sys Mon Jul 20 05:21:42 2009 (4A643726)
Dritek Keyboard Filter Driver
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Sat Jul 13 04:02:18.023 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071313-55130-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 19:23:25.552[/B]
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by :[B]Ntfs.sys ( Ntfs+1f15 )[/B]
BugCheck [B]24, {c08a5, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000000c08a5
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x24_Ntfs+1f15[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jun 18 16:04:41.750 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061813-86767-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 23:07:02.303[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 )[/B]
BugCheck [B]1A, {41201, fffff68000004008, a939c630cf209c8f, fffffa800e836070}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff68000004008
Arg3: a939c630cf209c8f
Arg4: fffffa800e836070
BUGCHECK_STR:  0x1a_41201
PROCESS_NAME:  dllhost.exe
FAILURE_BUCKET_ID: [B]X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13702[/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]**************************Sat Jul 13 04:02:18.023 2013 (UTC - 4:00)**************************
[B]ATK64AMD.sys                Tue May 12 21:04:54 2009 (4A0A1CB6)[/B]
[B]ASMMAP64.sys                Thu Jul  2 05:13:26 2009 (4A4C7A36)[/B]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[B]kbfiltr.sys                 Mon Jul 20 05:21:42 2009 (4A643726)[/B]
HECIx64.sys                 Thu Sep 17 15:54:16 2009 (4AB293E8)
ETD.sys                     Thu Oct 15 05:23:18 2009 (4AD6EA06)
iaStor.sys                  Thu Dec 17 13:41:59 2009 (4B2A7B77)
RTKVHD64.sys                Tue Jan 12 05:14:27 2010 (4B4C4B83)
IntcDAud.sys                Wed Feb  3 08:38:31 2010 (4B697C57)
Impcd.sys                   Fri Feb 26 18:32:11 2010 (4B8859FB)
L1C62x64.sys                Thu Mar  4 02:32:36 2010 (4B8F6214)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nvBridge.kmd                Sat Mar 27 11:46:26 2010 (4BAE2852)
nvlddmkm.sys                Sat Mar 27 12:29:29 2010 (4BAE3269)
enfilter.sys                Fri May  7 17:46:22 2010 (4BE48A2E)
npf.sys                     Fri Jun 25 12:50:58 2010 (4C24DE72)
psi_mf.sys                  Wed Sep  1 03:53:14 2010 (4C7E066A)
igdkmd64.sys                Sun Apr 10 14:50:59 2011 (4DA1FC13)
SRTSPX64.SYS                Tue Nov 15 17:30:55 2011 (4EC2E81F)
vmci.sys                    Mon Apr 30 21:14:27 2012 (4F9F38F3)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
VMNET.SYS                   Sun Jul  8 03:58:34 2012 (4FF93DAA)
vmnetadapter.sys            Sun Jul  8 03:58:35 2012 (4FF93DAB)
vmnetbridge.sys             Sun Jul  8 03:59:19 2012 (4FF93DD7)
Teefer.sys                  Tue Jul 17 08:58:52 2012 (5005618C)
SYMNETS.SYS                 Fri Jul 20 22:07:07 2012 (500A0ECB)
SYMDS64.SYS                 Mon Jul 23 18:58:38 2012 (500DD71E)
Ironx64.SYS                 Mon Jul 23 20:34:50 2012 (500DEDAA)
EraserUtilRebootDrv.sys     Tue Jul 31 19:36:50 2012 (50186C12)
eeCtrl64.sys                Tue Jul 31 19:36:51 2012 (50186C13)
ccSetx64.sys                Thu Aug 16 17:18:11 2012 (502D6393)
vsock.sys                   Tue Aug 21 17:10:15 2012 (5033F937)
SYMEVENT64x86.SYS           Wed Aug 22 01:33:18 2012 (50346F1E)
IDSvia64.sys                Tue Aug 28 22:48:40 2012 (503D8308)
SYMEFA64.SYS                Wed Oct  3 15:00:06 2012 (506C8B36)
hcmon.sys                   Thu Oct 11 20:15:27 2012 (5077611F)
cbdisk2.sys                 Wed Oct 17 05:27:42 2012 (507E7A0E)
cbfs3.sys                   Mon Oct 22 10:38:33 2012 (50855A69)
SRTSP64.SYS                 Thu Nov  1 16:16:15 2012 (5092D88F)
SysPlant.sys                Sat Nov  3 09:53:53 2012 (509521F1)
aksdf.sys                   Wed Nov 28 10:04:04 2012 (50B627E4)
ctxusbm.sys                 Fri Nov 30 11:09:56 2012 (50B8DA54)
aksfridge.sys               Tue Feb 19 07:09:17 2013 (51236B6D)
vmnetuserif.sys             Tue Feb 26 03:56:15 2013 (512C78AF)
VMkbd.sys                   Tue Feb 26 04:28:37 2013 (512C8045)
vmx86.sys                   Tue Feb 26 05:18:21 2013 (512C8BED)
hardlock.sys                Fri Mar  8 08:08:21 2013 (5139E2C5)
EX64.SYS                    Fri Apr 26 02:08:58 2013 (517A19FA)
ENG64.SYS                   Fri Apr 26 02:10:48 2013 (517A1A68)
BHDrvx64.sys                Mon May 20 16:47:31 2013 (519A8BE3)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jun 18 16:04:41.750 2013 (UTC - 4:00)**************************
enportv.sys                 Thu Nov 17 13:38:43 2011 (4EC554B3)
vmnetuserif.sys             Thu Nov  1 04:00:20 2012 (50922C14)
VMkbd.sys                   Thu Nov  1 04:31:30 2012 (50923362)
vmx86.sys                   Thu Nov  1 05:23:47 2012 (50923FA3)
akshasp.sys                 Sat Dec  8 01:01:50 2012 (50C2D7CE)
akshhl.sys                  Sat Dec  8 01:04:01 2012 (50C2D851)
AKSCLASS.SYS                Tue Dec 11 07:24:07 2012 (50C725E7)
aksusb.sys                  Tue Mar  5 08:46:53 2013 (5135F74D)
S3XXx64.sys                 Mon Mar 25 04:56:10 2013 (5150112A)
GsiMrx.sys                  Mon Apr 29 20:24:32 2013 (517F0F40)
[/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
enfilter.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
Teefer.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
cbdisk2.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
enportv.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
GsiMrx.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.

 

[AsusUser]

usasma / John,

Thanks for all the efforts so far.

From the ASUS website, I obtained the latest versions of the three drivers you specifically identified as needing updated. I installed the new versions. However, when I re-ran the collection tool, the dates on those three drivers are the same as earlier. (I have included that file in the zip file.) Any ideas? I think the dates should have changed.

I installed every available update from the Asus website.

MSINFO32 and the evtx file (using the steps you described) are both attached.

Much appreciated.

Mitch

 

[usasma]

The driver updates aren't critical (at this point) - and they're not at fault as often as other things. So, for now, let's just stick with what you've got and see what happens. Just FYI, often the manufacturer will put older drivers into a new package because it's cheaper than developing all new drivers. The package should have been thoroughly tested, so they presume that the older drivers are still good.

The Admin event viewer logfile cites a number of problems with the BIOS. First, please reset your BIOS to default values. Then, there are 3 newer versions of the BIOS at the Asus website for your model (so, please update your BIOS): Link Removed Be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard. Use the flash utility from within Windows in order to minimize the possibility of problems.

FYI - the MSINFO32 report was corrupted again - but this time I was able to open it in Notepad.
The drawback to this method is that I wasn't able to scan the WER reports (as I usually do) - but the Admin event viewer log should have taken care of most of that.

 

[AsusUser]

usasma / John,

I reflashed the BIOS with the updated version per your instructions. No problems re-booting after that.

I tried to re-capture MSINFO32 a couple times. Each time, same result - everything populates except for WER. So... no help there.

No new DUMP reports since July 14th.

Should I check anything else or is this a good resolution - unless I have a crash at a later date? Anything else you want to see?

Thanks much.

Mitch

 

[AsusUser]

usasma / John,

Minutes later, I did get the MSINFO32 file to show WER results (initially showed corrupted and then eventually opened) - and there are a few entries on July 19th. File attached. Anything useful?

Thank you.

Mitch

 

[usasma]

I wasn't able to open the MSINFO32 report. It opens in Notepad tho', and it has the WER error report info there.
I wouldn't be too concerned about this as it probably doesn't affect these problems.

I'd keep an eye on the system to see if the BIOS flash has fixed your problems. You can also run these free hardware diagnostics in order to see if there are any hardware problems on the system: Link Removed

 

[AsusUser]

usasma / John,

Will do.

Zero problems one week later knock on wood.

Thanks much for your hard work.

Mitch

 

[usasma]

Glad to hear it. Thanks for letting us know!