[SOLVED] BSOD three time a day HELP!

Hi -

The zip file contained 4 dump files, yet the Event Viewer logs show at least 13 BSODs going back to 28 April 2012. There are files missing from the jcgriff2 BSOD app output folder Windows7_Vista_jcgriff2 as well.

One entry found in the Event Viewer, yet had no corresponding dump file, clearly names ESET as the probable cause -
Code: 
[SIZE=2][FONT=Lucida Console]Fault bucket X64_0x1E_c0000005_R_[COLOR=#FF0000]EpfwLWF[/COLOR]+3ba0, type 0[/FONT][/SIZE]
http://sysnative.com/drivers/driver.php?id=EpfwLWF.sys

I am also experiencing difficulty with some of the output files (seem blank, even though size >0); not sure why. Did you by any chance terminate the jcgriff2 app prematurely?

I'm seeing Unknown_module in the dumps, which is indicative of RAM failure or other underlying hardware failure affecting RAM.

We should never see Unknown_Module as can be seen below (found in the dump files):
Read More:

First, let's concentrate on driver issues.

Code: 
[font=lucida console]eamonm.sys       Tue Aug 02 05:33:29 2011 (4E37C469) - ESET
ehdrv.sys        Tue Jun 28 03:34:38 2011 (4E09840E) - ESET
epfw.sys         Tue Jun 28 03:30:10 2011 (4E098302) - ESET
epfwwfp.sys      Tue Jun 28 03:30:08 2011 (4E098300) - ESET

lmimirr.sys      Tue Apr 10 18:32:45 2007 (461C108D) - LogMeIn
LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 (487B7E50) - LogMeIn

netr28x.sys      Mon Oct 12 09:42:24 [COLOR=#FF0000]2009[/COLOR] (4AD33240) - wifi
[/font]
http://sysnative.com/drivers/driver.php?id=EpfwLWF.sys
http://sysnative.com/drivers/driver.php?id=eamonm.sys
http://sysnative.com/drivers/driver.php?id=ehdrv.sys
http://sysnative.com/drivers/driver.php?id=epfw.sys
http://sysnative.com/drivers/driver.php?id=epfwwfp.sys
http://sysnative.com/drivers/driver.php?id=LMIRfsDriver.sys
http://sysnative.com/drivers/driver.php?id=lmimirr.sys
http://sysnative.com/drivers/driver.php?id=netr28x.sys


You have what appears to be an outdated ESET ESS/NOD32 installation.

Use the removal tool to remove ESET - http://kb.eset.com/esetkb/index?page=content&id=SOLN146

Reboot upon completion.

If you have a current ESET key code, install the latest version of ESET - http://www.eset.com/us/download/home/

If not, Install Microsoft Security Essentials (MSE)​


Update your LogMeIn installation. Upgrade to the most recent version - https://secure.logmein.com/welcome/products/

Locate a driver update for your wifi device - try this link or check your system manufacturer's support site.
http://sysnative.com/drivers/driver.php?id=netr28x.sys

RAM is a likely culprit here.

Run memtest86+ one stick at a time; alternate slots --> http://www.memtest.org/#downiso

Use ImgBurn to burn memtest86+ ISO to CD --> http://www.imgburn.com/index.php?act=download​


Windbg Logs
--> https://www.sysnative.com/BSOD2012/...lvevolts_Windows7x64_07-14-2012_jcgriff2_.txt
--> https://www.sysnative.com/BSOD2012/...olts_Windows7x64_07-14-2012_jcgriff2_.txt.zip

Regards. . .

jcgriff2


`


BSOD SUMMARY

Code: 
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\071212-16208-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jul 12 19:43:04.571 2012 (GMT-4)
System Uptime: 0 days 0:24:44.820
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 3B, {c0000005, fffff80003070319, fffff8800c47ef00, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertQueueApc+69 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiInsertQueueApc+69
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`03070319 fffff880`0c47ef00 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\071212-17534-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jul 12 19:45:06.319 2012 (GMT-4)
System Uptime: 0 days 0:00:34.926
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : tcpip.sys ( tcpip!TcpPeriodicTimeoutHandler+1f9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_tcpip!TcpPeriodicTimeoutHandler+1f9
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = P01-B1
BiosReleaseDate = 04/02/2010
SystemManufacturer = Acer
SystemProductName = Aspire X3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\071212-17986-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jul 12 18:47:27.431 2012 (GMT-4)
System Uptime: 0 days 8:07:31.054
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 3D, {fffff88002ffad60, 0, 0, fffff8800f29be04}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_nt!PoIdle+52a
Bugcheck code 0000003D
Arguments fffff880`02ffad60 00000000`00000000 00000000`00000000 fffff880`0f29be04
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\071312-17238-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jul 12 22:40:52.583 2012 (GMT-4)
System Uptime: 0 days 0:05:07.206
BugCheck 1000007E, {ffffffffc0000005, fffff800031d614c, fffff880033166c8, fffff88003315f20}
Probably caused by : memory_corruption ( nt!MiLogPageAccess+1fc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!MiLogPageAccess+1fc
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`031d614c fffff880`033166c8 fffff880`03315f20
BiosVersion = P01-B1
BiosReleaseDate = 04/02/2010
SystemManufacturer = Acer
SystemProductName = Aspire X3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


	    
             
       [color=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
             
           [url=https://mvp.support.microsoft.com/profile/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   

           [url=https://www.sysnative.com][color=#000033][u][url]www.sysnative.com[/url][/u][/color][/url]
             
           [url=http://jcgriff2.com][color=#000055][u][url]www.jcgriff2.com[/url][/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  
[/font]
 
Last edited:
Please run the jcgriff2 application again - most of the reports are empty and a few are missing. Let it run for at least 15 minutes (unless it finishes before then). Sometimes it's difficult to tell if it's still working.
 
Thanks guys...I'm running memtest 86 at the moment and I will check all the suggestios when its done..memtest did find errors ..I have no clue what they are,yet..thanks
 
That RAM stick is bad - needs to be replaced.

EDIT: That test was performed with a single RAM stick..?

If so and you have another stick, remove the bad one and see if the system is stable with the remaining stick(s).
 
Last edited:
I stayed out last night and got home just now and the mem test was still running? i just rebooted..I have three sticks of ram so i will test each one and trash the bad one. I re ran the BSOD program and attached it to this post.

Thanks again guys!
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top