Jump to content

BSOD MWAC.SYS windows 10 pro

folamour
 Share

Recommended Posts

folamour

folamour

Posted
Posted

Hi folks i'm experiencing BSOD under windows 10 involving Malware byte, im up to date regarding the OS or Malwarebyte 3.7.1

i've upgraded my NIC drivers, don't know what the next step,

attached is my crashdump,

 

2 crash dumps have been found and analyzed. Only 1 is included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

mwac.sys (Malwarebytes Web Protection, Malwarebytes)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.

032419-13375-01.dmp

Link to post
Share on other sites
  • Staff
Malwarebytes

Malwarebytes

Posted
  • Staff
Posted

***This is an automated reply***

Hi,

Thanks for posting in the Malwarebytes 3 Help forum.

 

If you are having technical issues with our Windows product, please do the following: 

Spoiler

If you haven’t already done so, please run the Malwarebytes Support Tool and then attach the logs in your next reply:

NOTE: The tools and the information obtained is safe and not harmful to your privacy or your computer, please allow the programs to run if blocked by your system.

  1. Download Malwarebytes Support Tool
  2. Once the file is downloaded, open your Downloads folder/location of the downloaded file
  3. Double-click mb-support-X.X.X.XXXX.exe to run the program
    • You may be prompted by User Account Control (UAC) to allow changes to be made to your computer. Click Yes to consent.
  4. Place a checkmark next to Accept License Agreement and click Next
  5. You will be presented with a page stating, "Get Started!"
  6. Click the Advanced tab
    Repair menu_arrows.png
     
  7. Click the Gather Logs button
    Advanced_arrows.png
     
  8. A progress bar will appear and the program will proceed with getting logs from your computer
    Advanced Gather Logs_arrows.png
     
  9. Upon completion, click a file named mbst-grab-results.zip will be saved to your Desktop. Click OK
    Advanced Gather Logs completed_arrows.png
     
  10. Please attach the file in your next reply. Before submitting your reply, be sure to enable "Notify me of replies" like so:
     notify me.jpeg  

Click "Reveal Hidden Contents" below for details on how to attach a file:
 

Spoiler

To save attachments, please click the link as shown below. You can click and drag the files to this bar or you can click the choose files, then browse to where your files are located, select them and click the Open button.

mb_attach.jpg.220985d559e943927cbe3c078b
 

One of our experts will be able to assist you shortly.

 

If you are having licensing issues, please do the following: 

Spoiler

For any of these issues:

  • Renewals
  • Refunds (including double billing)
  • Cancellations
  • Update Billing Info
  • Multiple Transactions
  • Consumer Purchases
  • Transaction Receipt

Please contact our support team at https://support.malwarebytes.com/community/consumer/pages/contact-us to get help

If you need help looking up your license details, please head here: https://support.malwarebytes.com/docs/DOC-1264 

 

Thanks in advance for your patience.

-The Malwarebytes Forum Team

Link to post
Share on other sites
LiquidTension

LiquidTension

Posted
Posted

Hello @folamour,

Thanks for reporting the issue.

Do you have a full memory dump (%systemroot%\MEMORY.dmp) from the blue screen? If you do, please compress the file, upload it to WeTransfer.com and provide the generated download link in a post.

In addition, please carry out steps 4 and 5 in the topic linked below:
https://forums.malwarebytes.com/topic/190532-having-problems-using-malwarebytes-please-follow-these-steps/

Thank you!

Link to post
Share on other sites
LiquidTension

LiquidTension

Posted
Posted

Thanks for the file. It looks like one of the troubleshooting tools used by the Malwarebytes Support Tool failed to download.

Please could you carry out the following instructions as well and provide the two generated logs: https://support.malwarebytes.com/docs/DOC-1318

I have a few questions on the blue screens:

  • When did they first start occurring? How many have occurred?
  • How often does the machine blue screen?
  • Does any particular action trigger the blue screen or is it seemingly random?


Obtaining a full memory dump will make it much more likely we're able to determine what's triggering the blue screen.

Please could you ensure full/complete memory dump creation is configured.
https://www.tenforums.com/tutorials/5560-configure-windows-10-create-minidump-bsod.html

Refer to, "Have Windows Create a Complete Memory Dump on BSOD" in the link above.

When the computer next blue screens, MEMORY.dmp should be created in C:\Windows.

 

Link to post
Share on other sites
folamour

folamour

Posted
  • Author
Posted

Hi liquid, all i know it that i was up to date 3.7.1 but dont know the rest of the version, i've used my registration email to download and install the latest,

then i followed your troubleshooting software and then he downloaded another release (I dont know if that a different one or not)

usually get the BSOD two time a day, since this update no BSOD, but you know this kind of thing need patience, ; )

I have make enougth room left on my C drive to get the full 32go dump file,

Keep you updated because that can take 3 or 4 day to BSOD, sry

 

 

Link to post
Share on other sites
LiquidTension

LiquidTension

Posted
Posted

That's no problem. Thanks for the information.

The Minidump indicates that the mwac.sys driver file present at the time of the crash was version 3.1.0.266. This belongs to the previous components package version (1.0.538). It's possible that now you have the latest components package version (and therefore a more up-to-date mwac.sys), the blue screen will no longer occur.

Link to post
Share on other sites
folamour

folamour

Posted
  • Author
Posted

hi folks, sorry about he delay, he's BSOD one more time, but this time get enougth room on my drive to get the memory.dmp, but its huge......... 32go

i goes to windbg and !analyze -v the dump, and he said :

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R)  SIG: 84'00000000 (cache) 84'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  MBAMService.exe


So i have the entire dump, but want to know how to proceed ?

thanks a lot,

guillaume,

 

 

Link to post
Share on other sites
folamour

folamour

Posted
  • Author
Posted

Ok currently compressing the dump, here the total display of windbg analysis

 


Microsoft (R) Windows Debugger Version 10.0.17134.12 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available

WARNING: Whitespace at end of path element
Error: Empty Path.
WARNING: Whitespace at end of path element
Symbol search path is: https://msdl.microsoft.com/download/symbols/
Executable search path is:
WARNING: Whitespace at end of path element
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff802`aac0e000 PsLoadedModuleList = 0xfffff802`aafbc150
Debug session time: Thu Mar 28 12:37:53.397 2019 (UTC + 1:00)
System Uptime: 1 days 4:31:04.099
Loading Kernel Symbols
...............................................................
................Page 2001881ec too large to be in the dump file.
........Page 2005c93a6 too large to be in the dump file.
........................................
........................................Page 20039f46d too large to be in the dump file.
.Page 2001888e9 too large to be in the dump file.
.......................
......................................
Loading User Symbols
Page 2001bc3d3 too large to be in the dump file.
Page 2001bc3d3 too large to be in the dump file.
.....Page 2003cb77a too large to be in the dump file.
.....................................Page 2001a95cb too large to be in the dump file.
......Page 20018c062 too large to be in the dump file.
.Page 2001baf67 too large to be in the dump file.
.Page 2001cdf42 too large to be in the dump file.
.Page 2002d5e70 too large to be in the dump file.
.Page 2001a19de too large to be in the dump file.
..Page 2001a3730 too large to be in the dump file.
.Page 20019ecac too large to be in the dump file.
.Page 2001fad9c too large to be in the dump file.
..Page 2002e3355 too large to be in the dump file.
.Page 20043bc2e too large to be in the dump file.
.Page 20019dcd8 too large to be in the dump file.
.Page 20019a0eb too large to be in the dump file.
...
Page 2001cc054 too large to be in the dump file.
.Page 2005e79e7 too large to be in the dump file.
.Page 2001cca3a too large to be in the dump file.
Page 2001cca3a too large to be in the dump file.
.Page 2001cc764 too large to be in the dump file.
Page 2001cc764 too large to be in the dump file.
.Page 2001ce07d too large to be in the dump file.
.Page 2001dc33d too large to be in the dump file.
.Page 20040a176 too large to be in the dump file.
.Page 2003fcf98 too large to be in the dump file.
.Page 2005e66f5 too large to be in the dump file.
.Page 20039f7b3 too large to be in the dump file.
.Page 2002dedab too large to be in the dump file.
.Page 2001d37c8 too large to be in the dump file.
..Page 2001d766e too large to be in the dump file.
Page 2001d766e too large to be in the dump file.
.Page 2001d6a95 too large to be in the dump file.
..Page 2001d836a too large to be in the dump file.
.Page 2001d4eda too large to be in the dump file.
.Page 2005e811a too large to be in the dump file.
.Page 2001d9b50 too large to be in the dump file.
.Page 2006d4bfd too large to be in the dump file.
...Page 2001e5c25 too large to be in the dump file.
.Page 200266fad too large to be in the dump file.
.Page 2001eeea2 too large to be in the dump file.
.Page 2001eb4d3 too large to be in the dump file.
Page 2001eb4d3 too large to be in the dump file.
.Page 2001ee237 too large to be in the dump file.
.Page 2001ec7a4 too large to be in the dump file.
.Page 2001f4987 too large to be in the dump file.
.Page 2001f51b4 too large to be in the dump file.
.Page 200181fd2 too large to be in the dump file.
.Page 2001f1f6f too large to be in the dump file.
.Page 20024b3d3 too large to be in the dump file.
...Page 20084b69a too large to be in the dump file.
.........Page 2001a483a too large to be in the dump file.
.Page 200021048 too large to be in the dump file.
.....Page 20084d2c6 too large to be in the dump file.
..Page 20016bb0e too large to be in the dump file.
......
Loading unloaded module list
...............................................................................................
ERROR: FindPlugIns 8007007b
ERROR: Some plugins may not be available [8007007b]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff802bd30a787, ffff86052a02e060, 0}

*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for MwacLib.dll -
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Probably caused by : NETIO.SYS ( NETIO!ProcessCallout+1eb39 )

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

3: kd> !Analyze -v
ERROR: FindPlugIns 8007007b
ERROR: Some plugins may not be available [8007007b]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff802bd30a787, Address of the instruction which caused the bugcheck
Arg3: ffff86052a02e060, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.

KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 402

BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  Z170-WS

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  3204

BIOS_DATE:  03/02/2018

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  Z170-WS

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  0

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff802bd30a787

BUGCHECK_P3: ffff86052a02e060

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction   0x%p emploie l'adresse m moire 0x%p. L' tat de la m moire ne peut pas  tre %s.

FAULTING_IP:
tcpip!AlePostProcessClassify+47
fffff802`bd30a787 49394218        cmp     qword ptr [r10+18h],rax

CONTEXT:  ffff86052a02e060 -- (.cxr 0xffff86052a02e060)
rax=000000000001ab8d rbx=ffff888a87b73088 rcx=0000000000000000
rdx=ffff888a8cee3010 rsi=fffff802be482104 rdi=ffff888a8cee3010
rip=fffff802bd30a787 rsp=ffff86052a02ea50 rbp=ffff86052a02eba0
 r8=ffff888a87b73088  r9=ffff888a751be180 r10=0000000000000038
r11=ffff888a7e502740 r12=ffff86052a02ece4 r13=ffff86052a02ef40
r14=ffff888a87b73088 r15=ffff888a75817790
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
tcpip!AlePostProcessClassify+0x47:
fffff802`bd30a787 49394218        cmp     qword ptr [r10+18h],rax ds:002b:00000000`00000050=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R)  SIG: 84'00000000 (cache) 84'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  MBAMService.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  MICHELANGELO

ANALYSIS_SESSION_TIME:  03-28-2019 13:53:51.0987

ANALYSIS_VERSION: 10.0.17134.12 x86fre

LAST_CONTROL_TRANSFER:  from fffff802bc7f4799 to fffff802bd30a787

STACK_TEXT:  
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
Page 2006d4bfd too large to be in the dump file.
ffff8605`2a02ea50 fffff802`bc7f4799 : ffff888a`6c3cec20 ffff8605`2a02ed98 00000000`0000015a 00000000`00000000 : tcpip!AlePostProcessClassify+0x47
ffff8605`2a02eaa0 fffff802`bc7d5087 : 00000000`00000042 ffff888a`8cee3010 ffff888a`87b73088 ffff888a`7e502740 : NETIO!ProcessCallout+0x1eb39
ffff8605`2a02ec30 fffff802`bc7d2d88 : ffff888a`708c0ee0 ffff888a`8cee3010 00000000`00000001 ffff8605`2a02eff0 : NETIO!ArbitrateAndEnforce+0x4a7
ffff8605`2a02ee20 fffff802`bd30a483 : 00000000`00000000 ffff888a`6a361040 00000000`00000202 fffff802`aacab328 : NETIO!KfdClassify+0x2f8
ffff8605`2a02f240 fffff802`bc80a859 : 0002a4ab`0002702b 00000000`00000001 71a6391b`cc674733 fffff802`aac78d4a : tcpip!AleInspectConnectRequestComplete+0x133
ffff8605`2a02f430 fffff802`bd4a614f : ffff888a`793cfed0 fffff802`bfd34880 ffff8605`2a02f4e8 fffff802`aaca2500 : NETIO!FeCompleteClassify+0xa9
ffff8605`2a02f480 fffff802`bfd28d3d : ffff888a`793cfed0 00000000`00000002 fffff802`bfd34880 00000000`00000000 : fwpkclnt!FwpsCompleteClassify0+0xf
ffff8605`2a02f4b0 fffff802`bfd29fb3 : ffff888a`793cfed0 fffff802`00000002 00000000`000000f8 ffff8605`2a02f5e0 : mwac+0x8d3d
ffff8605`2a02f4e0 fffff802`bfd272c8 : ffff888a`793cff20 fffff802`bfd34c00 ffff888a`6a774270 ffff888a`73fe3870 : mwac+0x9fb3
ffff8605`2a02f510 fffff802`bfd254ef : ffff888a`793cff20 00000000`000000f8 ffff9c8e`7ec15800 00000000`000000f8 : mwac+0x72c8
ffff8605`2a02f540 fffff802`bfd249f8 : 00000000`00000000 ffff888a`7ec19218 00000000`00000002 00002004`18623880 : mwac+0x54ef
ffff8605`2a02f590 fffff802`bfd2403e : 00000000`00000000 00000000`00000002 fffff802`bfd351c0 ffff9c81`48821010 : mwac+0x49f8
ffff8605`2a02f650 fffff802`bfd25198 : fffff802`bfd34c00 ffff888a`6f424410 00000000`00005c3b ffff888a`863f0100 : mwac+0x403e
ffff8605`2a02f680 fffff802`bfd2f0d8 : 00000000`000000a0 00000000`00000000 fffff802`bfd347a0 00000000`00000000 : mwac+0x5198
ffff8605`2a02f6c0 fffff802`aaca6e69 : ffff888a`6f424410 fffff802`00000000 ffff888a`73fe3870 00000000`00000000 : mwac+0xf0d8
ffff8605`2a02f700 fffff802`ab10af9b : ffff888a`6f424410 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x59
ffff8605`2a02f740 fffff802`ab10a64a : ffff888a`00000000 ffff888a`73fe38c0 00000000`00000000 ffff8605`2a02fa80 : nt!IopSynchronousServiceTail+0x1ab
ffff8605`2a02f7f0 fffff802`ab10add6 : 00000000`00000000 00000000`000017a8 00000000`00000000 000001b0`756fb130 : nt!IopXxxControlFile+0x68a
ffff8605`2a02f920 fffff802`aadc8743 : ffff9c8e`7a0a88b0 fffff802`ab109edd 00000000`77566d4d ffff8605`2a02f900 : nt!NtDeviceIoControlFile+0x56
ffff8605`2a02f990 00007ffc`787caa84 : 00007ffc`755728da 000001b0`74f1ce50 00007ffc`4fbe81d7 000001b0`140f1e60 : nt!KiSystemServiceCopyEnd+0x13
0000000c`b6dff9a8 00007ffc`755728da : 000001b0`74f1ce50 00007ffc`4fbe81d7 000001b0`140f1e60 ffffffff`00000000 : ntdll!NtDeviceIoControlFile+0x14
0000000c`b6dff9b0 00007ffc`766a4ac0 : 00000000`85010074 00000000`00000000 00000000`0000003d 00000000`0000003f : KERNELBASE!DeviceIoControl+0x1da
0000000c`b6dffa20 00007ffc`4fbe1133 : 000001b0`756c5470 00000000`00000000 000001b0`7a53bb20 000001b0`7a86f1b0 : KERNEL32!DeviceIoControlImplementation+0x80
0000000c`b6dffa70 000001b0`756c5470 : 00000000`00000000 000001b0`7a53bb20 000001b0`7a86f1b0 000001b0`7a86f1b0 : MwacLib!MWAC_SetDriverOffsets+0xa053
0000000c`b6dffa78 00000000`00000000 : 000001b0`7a53bb20 000001b0`7a86f1b0 000001b0`7a86f1b0 0000000c`000000f2 : 0x000001b0`756c5470


THREAD_SHA1_HASH_MOD_FUNC:  938891bcc462f672b059cf36030f99619fc6f97b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  39b5817372b68ba3634e493b45fd17aa4e9ab262

THREAD_SHA1_HASH_MOD:  a0b153bfe33c5f91c5ecca33cd9fa5c931fbaf1a

FOLLOWUP_IP:
NETIO!ProcessCallout+1eb39
fffff802`bc7f4799 90              nop

FAULT_INSTR_CODE:  1d23e990

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  NETIO!ProcessCallout+1eb39

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  90332b2

STACK_COMMAND:  .cxr 0xffff86052a02e060 ; kb

BUCKET_ID_FUNC_OFFSET:  1eb39

FAILURE_BUCKET_ID:  0x3B_NETIO!ProcessCallout

BUCKET_ID:  0x3B_NETIO!ProcessCallout

PRIMARY_PROBLEM_CLASS:  0x3B_NETIO!ProcessCallout

TARGET_TIME:  2019-03-28T11:37:53.000Z

OSBUILD:  17134

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2019-03-06 09:32:15

BUILDDATESTAMP_STR:  180410-1804

BUILDLAB_STR:  rs4_release

BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME:  787

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_netio!processcallout

FAILURE_ID_HASH:  {87101bcf-bd6e-56aa-8afa-fbe31b106fa6}

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

 

 

Link to post
Share on other sites
LiquidTension

LiquidTension

Posted
Posted

Thanks for the update. Please let me know the size of the compressed dump file and I'll send you details on how you can provide it to us.

In case it helps, you could also split the program into multiple compressed files using a program such as 7-Zip.
See here: https://superuser.com/questions/94083/how-to-split-large-file-on-windows/94084

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

  I accept