Video Screencast Help

BSOD on SErver2008 R2 when transferring large data

Created: 03 May 2011 | 8 comments

I have 2 systems connected via Cross-over cable, both are Server 2008 R2 with SP1 and the Hyper-V role enabled. When I attempt to transfer 20+GB of data through this Gigabit connection the recieving computer will often blue screen and reboot. Both are running Endpoint Protection 11.0.6005.562.

I contacted the hardware vendor thinking it was related to an expansion network card but they pointed me back to Symantec as the cause.

the stop code i get is: 0x0000007f (0x0000000000000008, 0x0000000080050033, 0x00000000000006f8, 0xfffff80001a8429e). and the Crash dump points back to tcpip.sys.

any suggestions?

Discussion Filed Under:

Comments 8 CommentsJump to latest comment

P_K_'s picture

What is the version of tcpip.sys?

General causes of "STOP 0x0000007F" errors

MCT MCSE-2012 Symantec Technical Specialist (SCTS)

Bsalyer's picture

TCPIP.sys file version 6.1.7601.17514 I'll investigate the links you provided.


P_K_'s picture

Stop error message on a computer that is running Windows Vista or Windows Server 2008: "STOP: 0x0000007F"

Stop error message in Windows Server 2008 R2 SP1 or in Windows 7 SP1: "STOP: 0x0000007F"

MCT MCSE-2012 Symantec Technical Specialist (SCTS)

Bsalyer's picture

Acquired the hotfix, I attempted to apply it to my test machine which was experiancing the problem but it says it is not applicable.

I attempted to run it for the production machine which was experiancing the problem and it was willing to apply the fix.  If i can schedule down time i'll test iton the production machine

Thomas K's picture

Does the issue occur when SEP is disabled? If so, what features are you running on the client?

Bsalyer's picture

The issue occurs with SEP disabled (it was disabled to increase throughput of known good files)

the installation includes:

Antivirus and Antispyware

Network Threat Protection

and Application and Device Control.

it does not include:

Antivirus Email Protection

TruScan Protection.

Also: I believe our Support Contract with Symantec is current.

Thomas K's picture

If the issue is happening with SEP disabled, then it is likely that SEP is not the cause of the BSOD.

Have you ran scans to make sure the system is not carrying a virus?

Bsalyer's picture

Yes, I've run scans on all impacted systems - all scans come back clean.

if things go as planned I'll be able to test the hotfix tonight, but that depends on scheduling issues.