Crashing, ntoskrnl.exe, ASUS PC Probe II?!

Toggle sidebar Toggle sidebar
Rhia

Rhia

Reputable
Jul 31, 2014
11
0
4,510
Update: I uninstalled/deleted all ASUS utilities/services. I'll update and pick an answer if/when I verify this is fixed (by not crashing again, haha)!

Thank you in advance for any help or advice!

[strike]ASUS Com Service and ASUS HM Com Service both still have disabled entries in Services.[/strike]
I used "sc delete ascomsvc" and "sc delete ashmcomsvc" to get rid of the Services listings.


I think all of this is being caused by ASUS PC Probe II, which had an installer, but has no uninstaller. [strike]It has multiple things in my System Drivers folders (AsUpIO.sys and AsIO.sys in both SysWow64 and SysWow64\drivers\) and it seems to be running two services called ASUS Com Service and ASUS HM Com Service that start automatically.[/strike]

Edit: I stopped/disabled the ASUS Com Service and ASUS HM Com Service, deleted the Program Files folders ASUS\AMDA (and in the Program Files x86 folder AAHM, AXSP, and VGA COM), searched for AsIO.sys and AsUpIO.sys in the SysWow64 folder (one had a .dll file) and deleted them all.


Passed 8 passes (88/88) of Memtest86 for 5 hours with 0 errors. Any advice is appreciated!
[strike]I'm currently updating the Intel graphics driver, installing the beta instead, and waiting to see if it fixes it.[/strike]
[strike]I'll update this if it crashes again or if it seems fixed. I'm about to run Memtest86.[/strike]

This happens every couple days like clockwork, the screen goes black and then blue screens.


In case Blue Screen View isn't good/reliable, here are the [strike]two[/strike] [strike]three[/strike] [strike]four[/strike] five .dmp files:
August 13th:
https://www.asuswebstorage.com/navigate/s/69AF6BC7A8654E009B6871C3B4E70C8B4
August 10th
https://www.asuswebstorage.com/navigate/s/69A57D506DA044119D7BC6D506A38E314
August 8th:
https://www.asuswebstorage.com/navigate/s/2BB51B6F632544B180C8A3106787F5CB4
August 5th:
https://www.asuswebstorage.com/navigate/s/13BED70479094B9A9BC2CB7B425F71274
August 2nd:
https://www.asuswebstorage.com/navigate/s/6FBE414B7C9043CE9C9514DF2DDBF4564


After the first crash (8/2) I installed the latest Intel HD drivers from the site just in case it was somehow that, and didn't have another blue screen for 2 days, then again for 2 more days.

I have Windows 7 Home Premium, ASUS Z97-A with a Pentium G3258 with 4 GB RAM (for now) and no graphics card (for now).


This is the latest info from Blue Screen View:

Fifth crash (after installing beta graphics driver instead)

8/13/2014 2:08:29 AM
Bug check string: IRQL_NOT_LESS_OR_EQUAL
Bug check code: 0x0000000a
Parameter 1: 00000000`00000000
Parameter 2: 00000000`00000002
Parameter 3: 00000000`00000000
Parameter 4: fffff800`02e81e52
Caused by driver: ntoskrnl.exe
Caused by address: ntoskrnl.exe+75bc0
Crash address: ntoskrnl.exe+75bc0


Fourth crash (after uninstalling the drivers I could find in johnbl's post):

8/10/2014 10:34:15 PM
Bug check string: IRQL_NOT_LESS_OR_EQUAL
Bug check code: 0x0000000a
Parameter 1: 00000000`00000000
Parameter 2: 00000000`00000002
Parameter 3: 00000000`00000000
Parameter 4: fffff800`02ed3e52
Caused by driver: igdkmd64.sys
Caused by address: igdkmd64.sys+200fd3
Crash address: ntoskrnl.exe+75bc0

Third crash:

8/8/2014 7:33:25 PM
Bug check string: IRQL_NOT_LESS_OR_EQUAL
Bug check code: 0x0000000a
Parameter 1: 00000000`00000000
Parameter 2: 00000000`00000002
Parameter 3: 00000000`00000000
Parameter 4: fffff800`02e7de52
Caused by driver: ntoskrnl.exe
Caused by address: ntoskrnl.exe+75bc0
Crash address: ntoskrnl.exe+75bc0

This was the second crash (after installing graphics driver):

8/5/2014 10:36:52 PM
Bug check string: IRQL_NOT_LESS_OR_EQUAL
Bug check code: 0x0000000a
Parameter 1: 00000000`00000000
Parameter 2: 00000000`00000002
Parameter 3: 00000000`00000000
Parameter 4: fffff800`02ecde52
Caused by driver: ntoskrnl.exe
Caused by address: ntoskrnl.exe+75bc0
Crash address: ntoskrnl.exe+75bc0

And this is from the first one (before installing latest Intel graphics driver):

8/2/2014 11:44:49 PM
Bug check string: IRQL_NOT_LESS_OR_EQUAL
Bug check code: 0x0000000a
Parameter 1: 00000000`00000000
Parameter 2: 00000000`00000002
Parameter 3: 00000000`00000000
Parameter 4: fffff800`02c8e662
Caused by driver: igdkmd64.sys
Caused by address: igdkmd64.sys+1fdcc3
Crash address: ntoskrnl.exe+80640
 
Solution
J
-you might want to remove suspect drivers.
basically your last bugcheck was in directx

some suspect drivers:
ALSysIO64.sys Tue Mar 05 13:50:34 2013
\SystemRoot\system32\drivers\amdxata.sys Fri Mar 19 09:18:18 2010
\??\C:\Program Files (x86)\ASUSTek Computer Inc\Disk Unlocker\ASFLTDrv64.sys Thu Sep 16 01:30:49 2010
\SystemRoot\SysWow64\drivers\AsIO.sys Wed Aug 22 02:54:47 2012
\SystemRoot\SysWow64\drivers\AsUpIO.sys Mon Aug 02 19:47:59 2010
\SystemRoot\SysWow64\drivers\ASUSFILTER.sys Tue Sep 20 08:46:33 2011
rasl2tp.sys Sat Nov 20 02:52:34 2010
raspppoe.sys Mon Jul 13 17:10:17 2009
raspptp.sys Sat Nov 20 02:52:31 2010
rassstp.sys Mon Jul 13 17:10:25 2009


BIOS Version 1204
BIOS Starting Address...
Sort by date Sort by votes
Rhia

Rhia

Reputable
Jul 31, 2014
11
0
4,510


Thanks for the reply but like I said, I already searched and saw that, and installed the Intel graphics driver and it changed my BSOD from igdkmd64.sys to instead being caused by ntoskrnl.exe :(

Any idea how to fix ntoskrnl.exe?
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
-you might want to remove suspect drivers.
basically your last bugcheck was in directx

some suspect drivers:
ALSysIO64.sys Tue Mar 05 13:50:34 2013
\SystemRoot\system32\drivers\amdxata.sys Fri Mar 19 09:18:18 2010
\??\C:\Program Files (x86)\ASUSTek Computer Inc\Disk Unlocker\ASFLTDrv64.sys Thu Sep 16 01:30:49 2010
\SystemRoot\SysWow64\drivers\AsIO.sys Wed Aug 22 02:54:47 2012
\SystemRoot\SysWow64\drivers\AsUpIO.sys Mon Aug 02 19:47:59 2010
\SystemRoot\SysWow64\drivers\ASUSFILTER.sys Tue Sep 20 08:46:33 2011
rasl2tp.sys Sat Nov 20 02:52:34 2010
raspppoe.sys Mon Jul 13 17:10:17 2009
raspptp.sys Sat Nov 20 02:52:31 2010
rassstp.sys Mon Jul 13 17:10:25 2009


BIOS Version 1204
BIOS Starting Address Segment f000
BIOS Release Date 06/20/2014

Manufacturer ASUSTeK COMPUTER INC.
Product Z97-A
Processor Version Intel(R) Pentium(R) CPU G3258 @ 3.20GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 3200MHz
memory:
Speed 1600MHz
Manufacturer 1315
Part Number BLS4G3D1609DS1S00


 
Upvote 1 Downvote
Solution
Rhia

Rhia

Reputable
Jul 31, 2014
11
0
4,510


Thank you for the reply! I've been tracking down the various drivers and uninstalling the associated programs, most so far have been ASUS software that I installed from the site, namely AI Suite 3.

I also uninstalled CoreTemp because in my searches it said the driver was used by that. My temp was staying around 24-31C so I don't really need it I guess?

I'm still unsure what some of them are, but I haven't crashed again yet, though it happened every few days before so maybe I just haven't run into it yet.

I'm about to reinstall DirectX, and then figure out how to run SFC from a USB drive (I don't have a SATA optical drive) to see if it fixes anything.
 
Upvote 0 Downvote
Rhia

Rhia

Reputable
Jul 31, 2014
11
0
4,510
Fourth blue screen just happened. Updated post with the latest .dmp in case anyone can help

I'm about to update the Intel graphics driver with the beta one instead to see if that helps.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
-I think you might want to run memtest86 on its own boot to try to rule out hardware issues and confirm your memory works as expected.
- you also have a newer CPU, you might want to go directly to intel an install the current intel chipset drivers for windows.
 
Upvote 0 Downvote
Rhia

Rhia

Reputable
Jul 31, 2014
11
0
4,510


As far as I can tell, the only chipset driver I can install would be "downgrading" (as stated on the installer) to this older version from February https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20775 which is before my CPU was released.

I'm making a memtest86 USB drive right now and I'll run that.

I had another crash and I'll update my original post with the latest .dmp just in case memtest86 finds nothing and this continues.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
- looks like there were two more BIOS updates for your motherboard since the one you have installed.
("system stability fixes") you might want to get the latest version from 8/5/2014

http://support.asus.com/Download.aspx?SLanguage=en&m=Z97-A&p=1&s=45
also shows a chipset update you might want to try. (if it is not the one you have)
now there is one thing about your debug image. It looks like you are still running two very old ASUS probe software drivers
\SystemRoot\SysWow64\drivers\AsIO.sys Wed Aug 22 02:54:47 2012
\SystemRoot\SysWow64\drivers\AsUpIO.sys Mon Aug 02 19:47:59 2010

if you removed it you might want to check your task scheduler and see if it put itself back in.
you might want to install.

or it could be the ASUS Probe II Sense Driver package does have a very old driver in it.


 
Upvote 1 Downvote
Rhia

Rhia

Reputable
Jul 31, 2014
11
0
4,510


I deleted the drivers (and a dll file with the same name as one). I couldn't at first because they were "in use, went into Services and found "ASUS Com Service" and "ASUS HM Com Service" both started and automatic.

Disabled both services, deleted the ASUS folder(s) in Program Files and Program Files (x86).

[strike]"ASUS Com Service" and "ASUS HM Com Service" are both still listed in Services, but are disabled.[/strike]

I used "sc delete ascomsvc" and "sc delete ashmcomsvc" to get rid of the Services listings.

I believe the Program Files (x86) ASUS folders AAHM and AXSP folders are where those are located but I don't know if I should just delete the folders or not.

Is this all I need to do, or is there a way to look for other remnants of ASUS Probe II/AI Suite 3 and others?
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
start cmd.exe as a admin
run
driverquery.exe /v > outfile.txt

take a look at the outfile.txt and you should get a list of drivers running/installed on your machine.

Note: I used to clear out the ASUS drivers but they would come back after a week and it was because they had
put a task in the task scheduler that checked the state of the drivers and would reinstall them if they were removed.
You had to delete the task to prevent it.
 
Upvote 1 Downvote
Rhia

Rhia

Reputable
Jul 31, 2014
11
0
4,510


Thank you for the reply, I feel like this is actually being fixed! Sorry for the millions of edits on my posts, I'm trying to keep the entire process listed in case someone else runs into this (and we fix it). :)

I looked in Task Scheduler, found and got rid of "i-Setup160111" by ASUS that I had missed before.

These suspected problem drivers are still listed in the outfile.txt:

rasl2tp.sys - WAN Miniport (L2TP) C:\Windows\system32\DRIVERS\
raspppoe.sys - Remote Access PPPOE C:\Windows\system32\DRIVERS\
rassstp.sys - WAN Miniport (SSTP) C:\Windows\system32\DRIVERS\
amdxata.sys - amdxata C:\Windows\system32\drivers\

There's also RasAgileVpn.sys and RasAcd.sys, both also WAN Miniport. Are these problematic?

I think amdxata is "AMD storage controller driver", and its start mode is "Boot".

I don't know if I can remove these things without causing other problems? I haven't crashed since my last update, but it was every couple days before so it could still be upcoming.

[strike]I don't see WAN Miniport in Device Manager,[/strike] (it was in Hidden Devices, had to unhide it).
[strike]I'm about to try these instructions to reinstall it:[/strike]
http://geekswithblogs.net/BrentCaskey/archive/2011/06/09/re-installing-wan-miniport-devices.aspx

I couldn't reinstall WAN Miniport (any of them listed) with hdwwiz.exe because it says "An error occurred during the installation of this device. The system cannot find the file specified."

I downloaded "Turbo LAN" and "Intel(R) Gigabit Ethernet Driver" from the ASUS site for my motherboard and I'm about to uninstall all listings of WAN Miniport in Device Manager, restart, then install those.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
I don't know of any problems with the remaining drivers, I think I just flagged them because of the driver dates. Normally if they are Microsoft drivers and you update they will be fine. If a Microsoft driver bugchecks millions of machines crash and report the bug to Microsoft automatically. Microsoft makes a fix and pushes the fix out via windows update. It is not the case with OEM drivers, Microsoft can get the bugcheck report but they had off the bug to the OEM and the OEM makes a fix. Problem is the OEM expects you to look at their website for the fix (they don't give the fix to Microsoft)

 
Upvote 1 Downvote
Rhia

Rhia

Reputable
Jul 31, 2014
11
0
4,510


Okay, thanks, I'm having Windows update each WAN Miniport listing in Device Manager now. I've got one down so far, the rest will probably do the same. I wonder why Windows Update doesn't automatically do that for those?

I think the issue might be fixed now! Removing ASUS PC Probe II (and other ASUS things, along with deleting the Task Scheduler entries) seems to have done it.

I'm waiting a while so I don't jump the gun on it, but thank you so much for the help (and to Combatmed1 for the attempt too)! I'll pick your answer where you pointed out ASUS Probe as soon as I'm sure.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom