Multiple BSOD error messages

[Wor3d]

Hello!
I have all specs filled, so feel free to check dome info there
My computer is like 1 and half year old, never had problem with him, just little one - PC accepted only 4Gigs of ram instead of 8. I couldn't play games like BF4, or have game and browser opened at same time, but I really dont care anymore, changed rams to another model and nothin, dunno...

Current problem is still same, but yet different for like a week. I get random BSODs or rarely PC restarts, with different reasons, mostly while playing any game. I didn't change nay components for long time, and didnt installed new drivers. (It couldn't be cuz theyre old, some games I played then and now without them updating, so nothin with drivers I guess...) I used program called BSOD viewer to try to fix problems with google, but no big succes... I'll write here some BSOD error codes...

HTML chart with crash log (sorry, software in lovak language, I think you'll figure it out :/) U will have to download it and view :/

I'll be glad to any help guys

Google Drive link

TL;DR:
Suddently repeated BSOD's with multiple error messages when playing games:
IRQL_NOT_LESS_OR_EQUAL
UNEXPECTED_KERNEL_MODE_TRAP
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
KMODE_EXCEPTION_NOT_HANDLED

 

[koolkat77]

Allot of important info is missing from your zip, please follow http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html to grab all and upload a new report here.

 

[Wor3d]

My bad...

Before anything, I want to than you for your reply Here is ZIP file

 

[Arc]

fffff880`08a7e798  fffff880`010dc2c6Unable to load image spwo.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for spwo.sys
*** ERROR: Module load completed but symbols could not be loaded for spwo.sys[/COLOR]
 spwo+0x432c6

I dont know what is spwo.sys. So searched for it in www. Some people thinks it as a virus.

Scan the system for possible virus infection with the following programs only.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the results.

 

[Wor3d]

Hi.

I ran the Kaspersky Root kit test, with no errors/founds.
I also ran the Windows defender offline, and ESET 8 complete in-depth scan of all drives, memory and system.

Meanwhile, I had couple of BSODs, as well as random restarts. Quick error logs said (marked red in program BlueScreen Viewer, dumped from 3 logs) mouhid.sys, npfs.sys, ntoskrnl.sys (eset antivirus, which i installed 2 days ago, not before bsods...), USBSTOR.sys, beep.sys, eamonm.sys, fltmgr.sys, resulting in SYSTEM_SERVICE_EXCEPTION, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and KMODE_EXCEPTION_MODE_NOT_HANDLED(I dont know if this informations are valuable, I know very little about stuff like BSODs....)

VERY interesting fact: I realised, that these BSODs and random restarts only happen when I will start computer, and 10-15 minutes after that. Later, after circa one restart and BSOD all seems to be fine... Not every day is start problematic...

Complete log from DM log collector, which is recommended for minidumps here is in attachment

 

[Arc]

Two dumps are blaming two different things.

Eset Personal Firewall driver

BugCheck 3B, {c0000005, fffff800028a1738, fffff8800e635cd0, 0}
[COLOR=Red]
*** WARNING: Unable to verify timestamp for epfw.sys
*** ERROR: Module load completed but symbols could not be loaded for epfw.sys[/COLOR]
Probably caused by : memory_corruption

Followup: memory_corruption
---------

Atheros Extensible Wireless LAN device driver by TamoSoft

BugCheck 7E, {ffffffffc0000005, fffff800028d9a04, fffff88007a62268, fffff88007a61ac0}

[COLOR=Red]*** WARNING: Unable to verify timestamp for ts_arnusbx.sys
*** ERROR: Module load completed but symbols could not be loaded for ts_arnusbx.sys[/COLOR]
Probably caused by : ts_arnusbx.sys ( ts_arnusbx+99af )

Followup: MachineOwner
---------

Are you sure that the scans did not found anything? Misinformation may be fatal for your system.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Also, it is a must in this situation to see your msinfo3.nfo file, which is corrupt in the zips. So upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

Continue with troubleshooting, dont post back only when you experience BSODs.

 

[Wor3d]

Things I did:

• I run MemTest86+ through 11 consecutive passes (around 11 hours?) with no errors
• I saved MSINFO32 file (too big file, so i had to .zip it to pass attachment requirements)
• I got 2 BSODs, around 2 hours from turning PC on.... (program dumped like 5 BSODs, new to you are just last 2 of them)
• I checked all .sys files that u listed there, and some more through VirusTotal, nothing bad found

I am sure ESET is not the cause, because I installed it after approximately 5 BSODs...
I am sure, that any of tests that you adviced (Anti-rootkit...), found no infected files.

 

[Arc]

The msingo32 files are corrupt again, in both of your attachments.

At this point I will have to suggest you to uninstall ESET. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Also, update the network driver from Realtek ... take the first one of the list (the "Win7 and Server 2008 R2 Auto Installation Program" one).

Also update the wireless network driver. I dont know the source of it.

Let us know how it goes.
_______________________________________

fffff800`03e65918  fffff880`0540641fUnable to load image Rt64win7.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys[/COLOR]
 Rt64win7+0x641f

fffff800`03e65768  fffff880`05202602Unable to load image EpfwLWF.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for EpfwLWF.sys
*** ERROR: Module load completed but symbols could not be loaded for EpfwLWF.sys[/COLOR]
 EpfwLWF+0x2602

 

[Wor3d]

So, my progress:

• Uninstalled ESET completely
• Installed free MBAM
• Got 1 BSOD, minute after starting PC (minidump included)
• Uninstalled VMware virtual network drivers (After last BSOD...)

That Wireless driver you adviced me to update, is newest. Also, I dont have WLAN Adapter connected at all.... (for like 2 months)
I dont know, what "corrupted msinfo32" means, so I'll upload it with last minidump.

 

[Arc]

Corrupt MSINFO means as you uploaded ....

View attachment 352911
​

If there is any more BSOD, post those.

 

[Wor3d]

Well, I don't know why, I can open .nfo file without problems... (According to google, u maybe dont have program to do it? Notepad++ and Programmer's notepad are working for me, even windows notepad...CtrlV.cz(scrshot))

One more BSOD happened just like sent you that one. (Attached)

 

[Arc]

Both the new dumps are not showing anything precisely. So it would be better to give Driver Verifier another go.

 

[Wor3d]

I didn't do Driver Verifier test yet. I see guide how to do it, but should I manually select drivers to controll, or drivers which you wrote me to check?

 

[Arc]

I didn't do Driver Verifier test yet. I see guide how to do it, but should I manually select drivers to controll, or drivers which you wrote me to check?

OK, to enable Driver Verifier to monitor the drivers, read it:

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Wor3d]

Okay, but guide is telling me, that i should enable all drivers, that are not made by microsoft. So, i know how to enable DV, but don't know which drivers I should enable. Enabling all drivers caused windows to not boot.

Meanwhile, I had couple BSODs, but one of them dont have minidump, because BSOD got stuck...

 

[Arc]

All about driver verifier is stated in the supplied link. Click it and know which you dont.

The BSODs caused by the audio driver.

BugCheck 50, {ffffffffd033c408, 0, fffff800032e2a88, 2}

*** WARNING: Unable to verify timestamp for MAudioFastTrack.sys
*** ERROR: Module load completed but symbols could not be loaded for MAudioFastTrack.sys

Could not read faulting driver name
[COLOR=Red]Probably caused by : MAudioFastTrack.sys[/COLOR] ( MAudioFastTrack+2608 )

Followup: MachineOwner
---------

Which is too old.

    Image name: MAudioFastTrack.sys
[COLOR=Red]    Timestamp:        Wed Dec 08 08:47:00 2010[/COLOR] (4CFEF8AC)

You need to update it. M-Audio - Acclaimed audio interfaces, studio monitors, and keyboard controllers

 

[Wor3d]

Okay. Few BSODs happened, but alot of them without Driver Verifier turned on, because I had to work without lags... Last 3-4 BSOD should be catched with Driver Verifier (Except very last one, i had to turn verifier off, beccause it throwed BSOD every 5 mins. At some point, i had to turn verifier off throught safe mode), turned on and configured like in tutorial which you gave me. All unnecesarry devices are permanently disconected (external Audio cards [btw those drivers are most actual, and win7 compatible], ext HDD, WiFi adapter...) After one of BSODs, windows decided to do some kind of "chkdsk" or what (before boot, so I dont know what was that exactly) on my secondary HDD (1000GB SATA3 7200RPM; windows SSD is 60GB SATA3)... And, I also removed one stick of ram, because Windows couldn't process all of 8 gigs (dunno why, it's 64 bits, but I had this problem like 1.5 years ago and all was fine... so, just to be sure)

I hope this will be enough information to you

 

[Arc]

Do you use Trend Micro?

fffff880`0b31a558  fffff880`00e55566Unable to load image spsc.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for spsc.sys
*** ERROR: Module load completed but symbols could not be loaded for spsc.sys[/COLOR]
 spsc+0x40566

If so, then how long? I cannot check because as always I cannot check your msinfo32.nfo file. So let us know. This info will be vital.

Also, Update the vmware tools. It is also causing BSODs here.

BugCheck A, {fffff980015a0fc0, 2, 1, fffff800033a8838}

*** WARNING: Unable to verify timestamp for hcmon.sys
*** ERROR: Module load completed but symbols could not be loaded for hcmon.sys
[COLOR=Red]Probably caused by : hcmon.sys ( hcmon+64fd )[/COLOR]

Followup: MachineOwner
---------

Display is also causing issues, but at first these two things are to be rectified. So continue with troubleshooting.

 

[Arc]

Also, can you explain how can you have a HP OEM licensing on a retail Gigabyte motherboard?

BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = 990XA-UD3

ID produktu:                         00426-OEM-8992662-00006

It is not possible without hackers activation exploitation which uses heavy modified codes and is sufficient reason for all those issues. A counterfeit computer is not any worthy for troubleshooting at all.

Get a legit windows license, have a legit windows install, and expect a trouble free computer.

 

[Wor3d]

I do not use Trend Micro, at least not now. VMWare is completely uninstalled from PC, so i dont know what should start the driver... Which is still in pc??? And, I cannot explain you why I have that OEM. Any idea why it is like that, it should not. ANd last thing - PC ran just fine for 1.5 years, nothin like this could broke win7, or ?

EDIT: WTF is trend micro? I didn't install any of those on my computer (was googling trend micro site), and my PC is 100% virus free. I checked in every possible way (Kaspersky, Anti rootkit, Eset, Malwarebytes, Virus Total.....)