BSOD during idle, error code 1E

[dakoslug]

Okay I'm getting sound distortions again. I'm getting really confused on where this is coming from. Could ESET really be causing this...?

 

[Arc]

First do it then see.

 

[dakoslug]

New BSOD. I checked it over a bit it seems like malwarebytes is an issue?

Could this be ESET + Malwarebytes issue..?

 

[Arc]

you noticed it?

PROCESS_NAME:  mbamservice.exe

The process name field is just the name of the program that was running at the time of the BSOD. Majority of the times it displays "system". Then system is not the issue.

Malwarebytes does not contribute to a BSOD other than two situations:

• Trial install with trial period expired
• Cracked/counterfeit install of MBAM.

If yours fall in either of these (I dont know), uninstall it, and get the free version only. That will be enough.

The BSOD was caused by network blockage for some reason.

BugCheck 7F, {8, 80050033, 406f8, fffff800032e6679}

[COLOR=Red]Probably caused by : NETIO.SYS[/COLOR] ( NETIO!CompareSecurityContexts+6a )

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

NETIO.sys does not fail at its own .... something is causing it to fail. And ESET personal firewall is still present there which is already found to cause such blockage earlier.

    Image path: \SystemRoot\system32\DRIVERS\epfw.sys

Saying it for the last time that we need to see the situation with ESET not present in the system.

If you still deny to listen it, I will have to stop, because it is also explicit that I cannot lead you to anywhere.

 

[dakoslug]

Something seems wrong, i cannot uninstall ESET...

Error opening installation log file

And yeah I looked at the minidump and I seen that process. my bad I guess I read it wrong

 

[Arc]

See what they are saying about it: How do I uninstall or reinstall ESET Smart Security/ESET NOD32 Antivirus? - ESET Knowledgebase

 

[dakoslug]

Okay managed to uninstall ESET. Is there anything I can do to see if it worked or do I have to just wait for another BSOD?

 

[Arc]

Just wait and see how it goes.

 

[dakoslug]

Okay so it's been 1 week or so without issues. I was able to idle, and there weren't any sound issues...

But yesterday night after a windows update I actually restarted my computer. (Probably the first time since I last posted) and then I left it to idle. I woke up this morning to a BSOD. I'm not exactly sure if the Windows Update caused it or whether restarting my computer agitated the issues yet again...

Here is the minidump. I would appreciate your help again. Thanks

 

[Arc]

WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
[COLOR=Red]3586 errors : !ataport [/COLOR](fffff88000de2000-fffff88000de2fff)

ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
[COLOR=Red]
DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR]

In this state, we will need the full data following the Blue Screen of Death (BSOD) Posting Instructions . We have to take a look at some more places.

 

[dakoslug]

Alright.

I idled my computer last night and there was no BSOD.

 

[Arc]

Uninstall WinCDEmu.

Test the 40 GB seagate with Seatools.
Test the 640 GB WD with Data lifeguard.

Also, re-seat the sata and power.

1. 

When seating, apply the cables on the other unused SATA ports on the motherboard. If possible, use fresh new SATA cables.

Let us know the results.

 

[dakoslug]

Is there any particular reason why Win32Emu? I did install that recently because I got rid of PowerISO.

Also I'm testing the HDD now

EDIT: Ran quick tests on both, all passed. I'll try re-seating the SATA cables later tonight

 

[Arc]

Is there any particular reason why Win32Emu? I did install that recently because I got rid of PowerISO.

All those programs are the same, they installs a SCSI adapter that to mount the drive during power on. Windows loads the software during the hardware environment, and a software tries to build the hardware environment at the same time; and here lies the problem.

If it is not the motherboard or BIOS, then it is the SCSI from Win32Emu that is throwing those storage port errors.

EDIT: Another explanation is possible for those storage port errors. There is a special type of malicious things called rootkit, and ataports are often infected by them. It is seen many a times that ataport errors are caused by rootkits only. So it would be better if you check for this possibility, too. Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

 

[dakoslug]

Ugh that is incredibly frustrating. Thanks for sticking with me and helping me out!

I scanned my computer with the Kaspersky tool you suggested. No threats found. I haven't gotten any BSOD since that windows update that seemed to cause it. I'll post back again if I receive one again. Maybe it'd be best to wait for Windows 10 or something to re-format...

 

[Arc]

Windows 10 will be a good place to go, for sure. You can do it right now, if you want: Download Windows 10 Technical Preview - Windows 10 Forums