Random BSOD- Need help

[vilcabti]

Random BSOD - Please, need help

Hi.

I'm uploading files obtained by SF Diag Tool. My system specs are:

Sistema operativo Microsoft Windows 7 Ultimate 6.1.7600 (Win7 RTM) 64 bits
Tipo de CPU HexaCore AMD Phenom II X6 1055T, 3500 MHz (14 x 250)
Nombre del motherboard MSI 890GXM-G65 (MS-7642) (1 PCI, 1 PCI-E x1, 2 PCI-E x16, 4 DDR3 DIMM, Audio, Video, Gigabit LAN)
Chipset del motherboard AMD 890GX, AMD K10
Memoria del sistema 4096 MB (DDR3-1333 DDR3 SDRAM)
DIMM1: G Skill F3-12800CL9-2GBRL 2 GB DDR3-1333 DDR3 SDRAM (8-8-8-22 @ 609 MHz) (7-7-7-20 @ 533 MHz) (6-6-6-17 @ 457 MHz)
DIMM2: G Skill F3-12800CL9-2GBRL 2 GB DDR3-1333 DDR3 SDRAM (8-8-8-22 @ 609 MHz) (7-7-7-20 @ 533 MHz) (6-6-6-17 @ 457 MHz)
Tipo de BIOS AMI (04/30/10)


I'm facing random BSOD. I've ran memtest+ 4.1 just one pass, and no errors found (single, in dual channel, in different slots). I know I probably must pass several times. However before I begin tu run a longer test, I wish to know if there is some driver problem.

Please help me to find a solution.

Regards.


New file uploaded: Windows7_BSOD_jcgriff2

 

[Jonathan_King]

Welcome!

Is this a recurring problem? If not, I advise to forget about it. My own machine BSODs once in a blue moon, likely from power issues.

The dump does not mention a specfic cause, but I do notice CCleaner was running at the time of the crash. Make sure it is NOT set to delete memory dumps, because we need them.

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

McAfee is also a good possibility. Please remove it with this tool: http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe

Replace it with the free Microsoft Security Essentials: http://www.microsoft.com/security_essentials

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Aug  7 10:41:03.242 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:45.382
BugCheck 50, {fffff8a0033bf4ac, 0, fffff800029b556d, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
BUGCHECK_STR:  0x50
PROCESS_NAME:  CCleaner.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[vilcabti]

Thanks Jonatahan.

Problem is recurring. I got 3 BSOD in the last hours. Files uploaded.

I had Magic Disc. I uninstalled it. Also uninstall sptd.sys with tool provided.

I never had problems with Mcafee before. This is a new PC, so don't discard this posibility, but if issue persists. I'll try uninstalling Mcafee.

Please tell me something about new dump files uploaded.

 

[Jonathan_King]

McAfee is blamed by one dump, highlighted. Be sure to remove that as suggested in my previous post.

I still see STPD.sys on your system. Please run this tool again: http://www.duplexsecure.com/download/SPTDinst-v172-x64.exe

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Aug  7 18:00:14.870 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:27.165
BugCheck D1, {fffffffa80077d22, 2, 0, fffff88006933be7}
*** WARNING: Unable to verify timestamp for mfefirek.sys
*** ERROR: Module load completed but symbols could not be loaded for mfefirek.sys
[COLOR=Red][B]Probably caused by : mfefirek.sys ( mfefirek+1dbe7 )[/B][/COLOR]
BUGCHECK_STR:  0xD1
PROCESS_NAME:  prime95.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Aug  7 17:55:21.704 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:50.000
BugCheck A, {10000004f, 2, 0, fffff800034da3df}
Probably caused by : memory_corruption ( nt!MiCheckControlArea+17f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[vilcabti]

Dump files uploaded were generated before I uninstall sptd.sys.

Now, I've uninstalled Mcafee and will install security essentials.

Hope this solve my problem.

I'll post any news. Thanks.

 

[Jonathan_King]

Sounds good, I honestly believe McAfee was the problem.

Keep us posted!

 

[vilcabti]

Hi again.

I'm uploading new file obtained with SF Diag Tool. Please review minidump for 08.17.10. Mcafee is uninstalled since last time I posted.

Please help me to identify another possible reason for BSOD.


Regards.

 

[ttran]

You have some out of date drivers, please update them:

fffff880`04f3d000 fffff880`04f44000   lmimirr  lmimirr.sys  Wed Apr 11 05:32:45 2007 (461C108D)
fffff960`00b80000 fffff960`00b88000   lmimirr2 lmimirr2.dll Wed Apr 11 05:32:46 2007 (461C108E)
fffff960`00920000 fffff960`0092c000   lmimirr_fffff96000920000 lmimirr.dll  Wed Apr 11 05:32:45 2007 (461C108D)

I believe they belong to product RemotelyAnywhere Mirror Miniport Driver or LogMeIn

Please run system file check please:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

I hope you will be able to run memtestx86 again at least 6 passes because it looks like all of the DMP file we've been looking at have memory violation related.

Also, I would like you to enable Driver Verifier:
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

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).

BUGCHECK SUMMARY:

BugCheck 1A, {5003, fffff70001080000, 1e79, 1d1800003cf0}

Probably caused by : win32k.sys ( win32k!vSolidFillRect1+157 )

Followup: MachineOwner
---------
PROCESS_NAME:  WINWORD.EXE

Regard,

Tuan