Wireless
Participate in insightful discussions regarding issues related to Intel® Wireless Adapters and technologies
7592 Discussions

BugCheck 7e with BE200

FM9
Beginner
277 Views

Dear Forum.
I'am trying to automate a Test with NetSH and a BE200 Card.
Sadly the whole Win11 System crashes.

StopCode: 0x0000007e
Arguments:
Arg1: ffffffffc0000420, The exception code that was not handled
Arg2: fffff803423f72fe, The address that the exception occurred at
Arg3: ffffda842cdda4c8, Exception Record Address
Arg4: ffffda842cdd9ce0, Context Record Address
EXCEPTION_RECORD: ffffda842cdda4c8 -- (.exr 0xffffda842cdda4c8)
ExceptionAddress: fffff803423f72fe (NetAdapterCx!BufferPool::~BufferPool+0x0000000000000012)
ExceptionCode: c0000420 (Assertion failure)
ExceptionFlags: 00000000
NumberParameters: 0
Assertion minio\netcx\bm\bufferpool.cpp(9): IsFull()

Does anyone have a solution for that problem or is there any kind of Information about the error?
Help is greatly appreciated.

Thx in advance.
FM

0 Kudos
2 Replies
nart
Novice
134 Views
0 Kudos
TylerZach900
New Contributor I
152 Views

hey there FM

Stop Code 0x0000007e is a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error, which is a very common bug check that indicates the system encountered an unhandled exception generated by a system thread.

exception code 0xc0000420 denotes an assertion failure. This could be due to a bug in the driver or firmware of the BE200 card, or an incompatibility with Windows 11. The specific assertion failure in minio\netcx\bm\bufferpool.cpp suggests there might be an issue with the buffer pool within the network driver that's not being properly handled.

 

Here are some steps you can take to troubleshoot and potentially resolve the issue:

  1. Update your wireless driver especially those related to the BE200 card, are up to date.
  2. Make sure your Windows 11 system is fully updated, as Microsoft frequently releases updates that can fix known bugs and compatibility issues.
  3. Run a memory check on your system. Faulty RAM can sometimes cause these types of errors. You can use Windows Memory Diagnostic or a third-party tool like MemTest86.
  4. Use the System File Checker tool to repair missing or corrupted system files. Run sfc /scannow in the Command Prompt (admin).
  5. Use the Deployment Imaging Service and Management Tool (DISM) with the command DISM /Online /Cleanup-Image /RestoreHealth.

 

I hope this helps, and you're able to resolve the system crash issue soon.

 

Tyler

Reply