BSOD sometimes on logging into windows BCCode 50/ntoskrnl.exe/IOMap64

[ASUSoverkill]

I have recently rebuilt my computer and I have never run into BSOD problems in the past but I'm guessing this one has something to do with a driver I installed somewhere. Not every log in but once in a while I will get BSOD after logging into windows with BCCode: 50. The computer restarts itself and then I am able to log into windows with no further BSOD problems. This does not happen every cold boot. It has happened three times so far in this order: After hooking up my monitor, after restarting for a realtek audio driver install, and today upon logging in. I uninstalled the realtek driver today because I find it useless but I doubt that was the issue because it happened before the driver. I tried looking into the dump files but I'm not very knowledgeable there so I have attached all three of them in this zip file. The windgb program i was using to read them mentioned "unable to load image \SystemRoot\system32\ntoskrnl.exe" and "probably caused by: IOMap64.sys".

I appreciate any help in sorting out these pesky screens.

 

[essenbe]

ASUSoverkill, welcome to Seven Forums. I will try to help you with this. I need the BSOD Posting instructions http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

Would you also please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

All of your dump files were the same.

IOMap64
start             end                 module name
fffff880`07591000 fffff880`0759a000   IOMap64  T (no symbols)           
    Loaded symbol image file: IOMap64.sys
    Image path: \??\[COLOR=red]C:\Windows\system32\drivers\IOMap64.sys[/COLOR]
    Image name: IOMap64.sys
    Timestamp:        Tue Jul 02 03:27:47 2013 (51D28F03)
    CheckSum:         00012564
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

IOMap64 is a driver made by Asus and usually is included in all of their utilities such as AI Suite. many people have it installed and can use it without any problems. Others the AI Suite gives them all kinds of problems. You appear to be in the latter category. Please uninstall all of the AI Suite Utilities and then use this, AI Suite II uninstall cleaner. It is very hard to get rid of. I had it installed at one time, but it ended up being more trouble than it is worth. After doing that see how it goes for you and let us know.

 

[ASUSoverkill]

Sorry for the delay, I forgot that I had posted on this forum a while back. I am still having trouble with the same blue screen messages IOmap64 but also more frequently it flags asmthub3.sys. I have uninstalled all ASUS AI suite or related GPU monitoring utility software and ran the cleaner that you linked. I still blue screened twice today after doing so. I have attached the dumpfiles as requested.

EDIT:
The blue screens just happen randomly now. Sometimes I will run my pc without issues and sometimes it will crash in the middle of a skype call or a loading screen or logging into windows or while just idling with some voice programs open.

 

[essenbe]

asmthub3.sys. is your ASMedia USB 3.0 Hub driver. You can also try this AI Suite II uninstall cleaner

 

[essenbe]

Your last 3 dumps are the same

[Use !analyze -v to get detailed debugging information.
BugCheck 24B10002, {fffffa800eef2790, fffff880024db250, fffffa8010ee5ca0, fffffa800eef2a58}
*** WARNING: Unable to verify timestamp for FiioE17.sys
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=red]FiioE17.sys[/COLOR]
[COLOR=red]Probably caused by : asmthub3.sys ( asmthub3+9177 )[/COLOR]
Followup:     MachineOwner
/CODE]
 
FiiO USB DAC-E10 Audio Driver (WDM)
 
You are also getting errors from atkexComSvc.exe which is a part of AI Suite.

 

[ASUSoverkill]

I've already used that cleaner. I have updated my ASmedia hub drivers to the latest versions both the 3.0 controller drivers and the hub driver. The bluescreen still happened after the driver update. I'm not sure what to do with the link you sent me for drivers above.

EDIT:
I didn't know about the FiiO driver. I will look for another driver for it. Not sure how to clean the ASUS files anymore.

 

[essenbe]

No matter how you do it, the AI Suite is almost impossible to get rid of. Some have only rid themselves of them with a clean install.

Are you using a wireledd dongle? if so, try removing it and see if you still get BSODs.

 

[ASUSoverkill]

A wireledd dongle?

 

[ASUSoverkill]

I read in a Youtube post that you can move the Fiio E17 to a USB2.0 port and it should solve the USB3.0 Blue screen problems. I will see. I am about to run the cleaner again in safe mode for the IOmap64 problem

EDIT:
The cleaner wouldn't run the second time. I found an IOMap64.sys file under a folder in C:/programfiles/ASUS/ and deleted all of the ASUS folder (made sure i didn't need anything in there and have already uninstalled all my ASUS utilities.) Hopefully these few things fixes the blue screens.

 

[essenbe]

Wireless.

 

[ASUSoverkill]

I have no wireless devices connected to my computer.

 

[essenbe]

OK, just checking.