Community
cancel
Showing results for 
Search instead for 
Did you mean: 
SPriv1
Beginner
2,336 Views

Re:I219-V latest Intel Network Gigabit Drivers causes crash on wmiprvse.exe...

Good day.

I hope you can make this thread "unresolved" again. This is still happening...

I updated my Intel i219-v drivers this week from PROWin_v22.1 (driver version 12.15.23.9) to Intel-LAN-22.4.16.0-RS2-20170718.zip which I found on Asus Website (driver version 12.15.25.6). Immediately WMIPRVSE started crashing. I have User-Mode dumps enabled, and after this release I see about 5 dumps a day - I can FTP somewhere if you accept dumps. CoreAgnt.dll is version 22.4.14.0. The Windows Error Reporting Service records this:

Faulting Application Path: C:\Windows\System32\wbem\WmiPrvSE.exe

Problem Event Name: BEX64

Application Name: wmiprvse.exe

Application Version: 6.3.9600.16406

Application Timestamp: 5244fd73

Fault Module Name: CoreAgnt.dll_unloaded

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 58fe61c5

Exception Offset: 000007fee4197e88

Exception Code: c0000005

Exception Data: 0000000000000008

When I discovered this I went back to Intel and discovered a new release, so I installed PROWin_v22.6. The CoreAgnt.dll version increased to 22.6.6.0 but it was still crashing.

I downgraded back to PROWin_v22.1 and the problem is gone.

The release notes between 22.1 and 22.6 only speak of enabling ultra low power mode, so according to them I am not missing much. But some bugs were probably corrected, so I would LIKE to be able to use the latest drivers. Features like Large Send Offload are especially problematic and might've seen a few improvements between releases.

When I look in WinDbg I see this:

BUGCHECK_STR: APPLICATION_FAULT_BAD_INSTRUCTION_PTR_SOFTWARE_NX_FAULT_INVALID

PRIMARY_PROBLEM_CLASS: BAD_INSTRUCTION_PTR_INVALID

I see NX there; maybe this is related to the fact that I have NoExecute (DEP) enabled for all processes, rather than the Opt-In which is the default? I'm not really in the mood to reInstall the latest drivers, disable DEP and let the machine sit for a day just to see if DEP is the issue - CoreAgnt.dll should not be causing DEP issues...

Thank you.

Best Regards,

Tags (1)
0 Kudos
34 Replies
idata
Community Manager
446 Views

Hi B00ze,

 

 

Thank you for posting at Wired Communities. Just to double check since the crash occurred after updating to Asus driver and understand you reverted back to version 22.1. Have you tried just upgrade directly from version 22.1 to version 22.6 (Intel's).

 

 

Thanks,

 

sharon

 

SPriv1
Beginner
446 Views

Hi Sharon.

You missed a little bit of my message:

When I discovered this I went back to Intel and discovered a new release, so I installed PROWin_v22.6. The CoreAgnt.dll version increased to 22.6.6.0 but it was still crashing.

So I went from release 22.1 -> Asus (Crash) -> release 22.6 (crash) -> 22.1 (fixed).

Best Regards,

idata
Community Manager
446 Views

Hi Booze,

 

 

Thank you for pointing that out, What is the operating system and your Asus model?

 

 

Regards,

 

sharon

 

SPriv1
Beginner
446 Views

Hi Sharon.

Windows 7 x64. Asus Maximus Hero VIII with Skylake; latest BIOS (new, with HyperThread-Bug-Fix microcode). Could be caused by the fact that I have NoExecute as Opt-Out (enabled for all processes except those I specify) rather than the Win7 default of Opt-In (disabled for most processes except those that I specify). I say this only because of WinDbg's description of the fault. When I have time again I /could/ try to add WmiPrvSE to the Opt-Out list and see if that fixes the problem - clearly the problem would still be there but it might not crash the process. I'm busy debugging something else tho right now. This is not something EVERYONE experiences, otherwise there would be more reports, but we're at least two ;-)

Regards,

idata
Community Manager
446 Views

Hi Booze,

 

 

Thank you for the information. I will check on this.

 

 

Regards,

 

sharon

 

idata
Community Manager
446 Views

Hi Booze,

 

 

The difference on the driver is the enabling of Ultra Low Power configuration.

 

I would suggest you to contact Asus* support still to check if there might be

 

incompatibility with something on the Asus motherboard. They are in better position to isolate the issue as this is an onboad NIC.

 

 

Thanks,

 

Sharon

 

SPriv1
Beginner
446 Views

Hi Shanon.

I really think the two best placed to investigate this are Intel and Microsoft. You can both analyze the dump file(s) that the crash creates. Intel knows the crashing DLL and Microsoft knows the crashing process. There is virtually no chance that Asus can assist; they will probably point me back here. There is one other user with that problem (from which this discussion has been branched off) and he has a completely different motherboard, and a different network adapter. To me this says that something in common to both is causing the issue, something in CoreAgnt.dll. Since both motherboards are Asus, there is a small chance that the problem is caused by some BIOS code shared by both motherboards, but I need Intel to tell me what that is if I am to go to Asus and complain. I also don't mind going to Microsoft, but I would like to also go there with something from Intel. Something detailed, otherwise the likely outcome will be Microsoft blaming Intel and we will go nowhere. I know from experience that wmiprvse is very "fragile" - I know of a PDF-Printer driver that also makes this process crash. But I can find other PDF-Printers, whereas it is impossible to find another driver for my NIC.

Will you not have a look at the process dump? Your programmers can tell much more from it than I can...

Thank you.

Best Regards,

idata
Community Manager
446 Views

Hi Booze,

 

 

Thank you for the clarification. Let me further check.

 

 

Thanks,

 

Sharon

 

idata
Community Manager
446 Views

Hi Booze,

 

 

Thank you for the information. Please be informed Asus must be the first point of contact for support as they are the manufacturer. Intel supplies the chip but Asus decides how to implement it. That motherboard may not have support for the ultra low power mode. If this is happening on several Asus motherboards, then Asus needs to know about then and they have their own engineering support channel to contact Intel for help. Hope this clarifies.

 

 

Thanks,

 

Sharon

 

SPriv1
Beginner
446 Views

Good evening Sharon.

I have opened a case with Asus, but they use a Web Form for emails with a max number of characters, so I had to point them to this thread here for a description of the issue. Hopefully they are allowed to follow URLs in support emails. Unfortunately they do not provide case numbers. Will report back.

Best Regards,

idata
Community Manager
446 Views

Hi Booze,

 

 

Thank you for the update and hope to hear good news from you.

 

 

Regards,

 

Sharon

 

idata
Community Manager
446 Views

Hi Booze,

 

 

Any update from Asus*? Please feel free to update me.

 

 

Thanks,

 

Sharon

 

SPriv1
Beginner
446 Views

Good day.

The Asus rep was all happy to tell me that he'd found the solution: Please download the latest Intel drivers.

So I had a look and there was a new release (v22.7.1.0). Installed it, CoreAgnt.dll version was now 22.7.17.0. Ten minutes later, WMIPRVSE had already crashed:

Faulting application name: wmiprvse.exe, version: 6.3.9600.16406, time stamp: 0x5244fd73

Faulting module name: CoreAgnt.dll_unloaded, version: 0.0.0.0, time stamp: 0x599b44a1

Exception code: 0xc0000005

Fault offset: 0x000007fef6207f48

Faulting process id: 0x1f84

Faulting application start time: 0x01d3453016e6e5f7

Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe

Faulting module path: CoreAgnt.dll

Report Id: 734520d7-b125-11e7-947e-3497f634f9ff

Regards,

idata
Community Manager
446 Views

Hi Booze,

 

 

I am sorry to hear what happened. Can you check with Asus* if they have any customized driver and inform them about this issue so that they can check with their engineer internally.

 

 

Thanks,

 

Sharon

 

SPriv1
Beginner
446 Views

Hi Sharon.

They're not much help so far; they offered to RMA my motherboard. There's nothing wrong with it as far as I know. Before we think RMA we need to analyze the crash dump and see why that WMIPRVSE process is crashing. Maybe Microsoft could help; you know the entry point to Microsoft for this kinda question? Like where do I go?

Thanks.

Best Regards,

idata
Community Manager
446 Views

Hi Booze,

 

 

Thank you for the update. I am sorry I do not know where is the exact entry point for this kind of inquiry. I try search on the Microsoft site and found here is the support contact entry, you may inquire them and ask them to direct you to the support team.

 

 

https://support.microsoft.com/en-us/contactus/

 

 

https://support.microsoft.com/en-us

 

 

While searching on the contact site, I search using "Wmiprvse.exe" on the Microsoft site and found there are other inquiries about Wmiprvse.exe crashing in Windows, thus you may double check with Microsoft and hope they could be of help.

 

 

Thanks,

 

Sharon
SPriv1
Beginner
446 Views

Good day.

Alright, I was unable to make the Microsoft Support site work. There is this "virtual assistant" and when I click "I want to Chat" it just sits there for hours, sending data back and forth but never opening a chat window. So I am trying the Microsoft Community, https://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/wmiprvse-crash-with-newer-intel... https://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/wmiprvse-crash-with-newer-intel...

Regards,

idata
Community Manager
446 Views

Hi Booze,

 

 

Thank you for the update and hope to hear good news from you.

 

 

Regards,

 

Sharon

 

idata
Community Manager
446 Views

HI Booze,

 

 

Please feel free to update me or if there is other inquiry. Thank you.

 

 

Regards,

 

Sharon

 

SPriv1
Beginner
217 Views

Hi Sharon.

Asus support is not moving anywhere, but my ticket is not closed. On Microsoft's side, I proceeded in making the Intel driver crash on a freshly installed Windows 7, so the problem is not something I did to my Windows (breaking the driver) - I can reproduce on a newly installed Win7 image. Here's what I did:

1- Backup/Image current system partition

2- Restore system partition to a Fresh install of Windows 7, no drivers, nothing but Win7.

3- Enable DEP

4- Enable User-Mode dumps

5- Install latest Intel Network Drivers

6- Open a remote desktop to generate traffic

7- Wait 10 minutes -> WMIPRVSE has crashed.

I know you tried to escalate this before, but we had not tried a Fresh Windows install.

Can you see if you can escalate again? I would be interested in knowing if this can be reproduced on an Intel board.

PS: My Windows 7 x64 install has the "Convenience Update" (sp2) slip-streamed, so if you try to reproduce you may need to install the convenience update.

Thank you.

Best Regards,

Reply