[SOLVED] BSOD anytime

Docfxit · Sep 4, 2020

· OS - Windows 7 Ultimate
· x86 (32-bit)
· What was the originally installed OS on the system? Windows 7 Ultimate

· Is the OS full retail version (YOU purchased it from retailer)
· Age of system (hardware) 12/12/2014
· Age of OS installation - 12/12/2014

· CPU AMD A8-7600 Radeon R7, 10 Compute Cores 4C+6G 3.10GHz
· Video Card AMD Radeon R9 255
· MotherBoard - LENOVO 90AY000BUS
· Power Supply - LENOVO

· System Manufacturer LENOVO
· Exact model number 90AY000BUS

· Desktop

Patrick · Sep 5, 2020

Code:

Bugcheck code 1000007E
Arguments c0000005 88b8d17b 807b767c 807b7260

There was an unhandled exception in a system thread, which in this case was an access violation (0xc5). When we see access violations in these bugchecks as the exception, it's typically a driver issue causing the corruption.

Code:

eax=00000000 ebx=ab75fc98 ecx=00000000 edx=00000000 esi=807b7854 edi=807b7794
eip=88b8d17b esp=807b7744 ebp=807b7750 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
NETIO!CalloutStreamDataInit+0xe:
88b8d17b 8b5004          mov     edx,dword ptr [eax+4] ds:0023:00000004=????????

The access violation occurred in a network I/O subsystem function (CalloutStreamDataInit). The instruction at the time of the exception was to do some simple data moving with the mov instruction from eax+4 to edx. The reason an access violation occurred is due to the eax register being null (eax=00000000).

What we should do next is take a look at the stack at the time of the crash to see what's going on in relation to network:

Code:

00 807b7750 88b8d648 NETIO!CalloutStreamDataInit+0xe
01 807b7798 88b8d9fa NETIO!StreamInvokeCalloutAndNormalizeAction+0x2f
02 807b77c8 88b8db15 NETIO!StreamCalloutProcessData+0x31
03 807b7808 88b8df7b NETIO!StreamCalloutProcessingLoop+0x55
04 807b7874 88b7bf72 NETIO!StreamProcessCallout+0x128
05 807b78d8 88b66b3e NETIO!ProcessCallout+0x120
06 807b794c 88b6521f NETIO!ArbitrateAndEnforce+0xae
07 807b7a5c 88b8cbaa NETIO!KfdClassify+0x1c7
08 807b7ae8 88b8e5e9 NETIO!StreamInternalClassify+0x84
09 807b7b44 88b89cdb NETIO!StreamInject+0x17e
0a 807b7b88 88d94c71 NETIO!FwppStreamInject+0xde
0b 807b7bc0 8e38af4d fwpkclnt!FwpsStreamInjectAsync0+0x93
WARNING: Stack unwind information not available. Following frames may be wrong.
0c 807b7c14 8e387d9e vsdatant+0xdf4d
0d 807b7c2c 8e387e94 vsdatant+0xad9e
0e 807b7c4c 8361fb36 vsdatant+0xae94
0f 807b7c90 834bf8f5 nt!PspSystemThreadStartup+0x11b
10 00000000 00000000 nt!KiThreadStartup+0x19

There's a system thread startup and then we call vsdatant.sys before going into a bunch of network subsystem stream stuff, which is a ZoneAlarm driver.

I did a quick look at some other modules installed and can see that you also have Bitdefender on the system. What's probably going on here well-before the crash is that ZoneAlarm isn't playing nicely with Bitdefender. Typically you can run both firewall and av software without issue, but apparently here it's not working too well.

My suggestion is to uninstall ZA on the machine and see what happens.

Docfxit · Sep 6, 2020

Thank you immensely for figuring that out. I didn't realize ZA was on the machine because it wasn't running. I have uninstalled ZA. I have re-booted the machine. I'm now waiting to see what happens.

Patrick · Sep 9, 2020

No problem, good luck.

Docfxit · Sep 9, 2020

I haven't had a problem with it since. You are a genius.

Thank you very much,

Docfxit

Search

Search

[SOLVED] BSOD anytime

Docfxit

Contributor

Attachments

Patrick

Sysnative Staff

Docfxit

Contributor

Patrick

Sysnative Staff

Docfxit

Contributor