Blue Screen plz help minidump in topic

julian2017

Prominent
Apr 26, 2017
9
0
510
*****Windows server 2008 R2 Standard*****

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.272.7
Locale ID: 1033

Additional information about the problem:
BCCode: c2
BCP1: 0000000000000007
BCP2: 0000000000001097
BCP3: 0000000000000000
BCP4: FFFFFA8010766010
OS Version: 6_1_7600
Service Pack: 0_0
Product: 272_3

Files that help describe the problem:
C:\Windows\Minidump\042617-11996-01.dmp
C:\Users\admin\AppData\Local\Temp\2\WER-3060068-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x0000000000000007, 0x0000000000001097, 0x0000000000000000, 0xfffffa8010766010). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 042617-11996-01.

MINIDUMP LINK :
https://mega.nz/#!ndlSRChR!MeW3VSwBeqdLfRxggNk1nbaLli6_OrFsmNuNtOu-1Yc



 


Hello, thank you very much bailojustin for the help
GameServer.exe really is a program that I use to manage a game server, do you have any idea why it is causing it?
 


Issues with winsock connections, try reseting winsock
 


I formatted the machine, previously, it only has 1 day and this problem occurred again.
I will pass the information to the Gameserver.exe developer
Thank you for your help
 



Hello again,i have this dump too
Is it different, or is it the same thing?
Is it possible to see better what happens through it?

Memory.DMP (dump):
https://mega.nz/#!GRMQgTgC!Kbw_jBwi95mt_Y9B1dbKCFY53yFgetIRPzLZT2iBMvQ
 



Hello, I can not read your answer, I think it gave some problem
 


042617-11996-01.dmp
4/26/2017 5:48:40 PM
BAD_POOL_CALLER
0x000000c2 00000000`00000007 00000000`00001097 00000000`00000000 fffffa80`10766010

CULPRIT DRIVER tcpip.sys tcpip.sys+4842f


\x64 ntoskrnl.exe+6f880 \

8 15 7600 271,880 4/26/2017 11:06:11 PM

Please Update or repair your TCPIP drivers, they may be corrupt.
For help and more information doing so, please start by visiting Microsofts TCP reset and more.

The site has steps you should follow in order to fix your issue.
if the problem persists, let me know.

Also reinstall your LAN drivers, also check your device manager and please post the results if there are any non functioning or halted drivers.
 
you should start your own thread and put the actual memory dump on a server like microsoft onedrive, share the files for public access and post a link.

basically if you are getting a bugcheck in a network stack, it will be a bug in a 3rd party network driver. In the original post it would have been a bug where the driver freed up the same memory address twice. but they were also running windows 7 RTM and needed to update to service pack one.
 
for the bugcheck in the transport I would first look to update your network drivers:
\SystemRoot\system32\DRIVERS\e1q62x64.sys Mon Apr 2 14:29:29 2012

and
Intel(R) 82579V Gigabit Network Connection driver
\SystemRoot\system32\DRIVERS\e1c62x64.sys Thu Mar 15 20:57:28 2012
http://downloadcenter.intel.com/

assuming your windows version has had its updates applied.
 
Honestly, if you reistaled and formatted and the problem persists, I have seen it multiple times, but it's very easy for your network port to suffer from a surge causing it to act as described. ESPECIALLY after a reinstall of OS.

Get a network card and try.
 



have the following problem at the moment:

A critical system process, C: \ Windows \ system32 \ lsass.exe, failed with status code 255. The machine must now be restarted.

Fault bucket, type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: lsass.exe
P2: 6.1.7600.16385
P3: 4a5bc155
P4: StackHash_2264
P5: 0.0.0.0
P6: 00000000
P7: 000000006d7814d5
P8: c0000005
P9: 0000000000000008
P10:

Attached files:
C: \ Windows \ Temp \ WER9FC7.tmp.appcompat.txt
C: \ Windows \ Temp \ WER9FF6.tmp.WERInternalMetadata.xml
C: \ Windows \ Temp \ WER9FF7.tmp.hdmp
C: \ Windows \ Temp \ WERA49A.tmp.mdmp

These files may be available here:
C: \ ProgramData \ Microsoft \ Windows \ WER \ ReportQueue \ AppCrash_lsass.exe_50a2a82d60eaa41211b4392c16505b4ff5f630c4_cab_0f5ca4d5

Analysis symbol:
Rechecking for solution: 0
Report Id: 3f657c19-304b-11e7-ba71-002590528cf6
Report Status: 0

///////////////
Faulting application name: lsass.exe, version: 6.1.7601.23391, time stamp: 0x56e99881
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000006d7814ff
Faulting process id: 0x1fc
Faulting application start time: 0x01d2c48dfaa4d1fb
Faulting application path: C: \ Windows \ system32 \ lsass.exe
Faulting module path: unknown
Report Id: deda9038-3097-11e7-bf5f-002590528cf6

A critical system process, C: \ Windows \ system32 \ lsass.exe, failed with status code 255. The machine must now be restarted.



---------------

Fix:1 Installed (but dont work)

https://support.microsoft.com/en-us/help/2913087/lsass.exe-process-crashes-and-error-code-255-is-logged-because-of-a-cnf-ntds-settings-object-in-active-directory-on-windows

Fix2: Installed (but dont work)

https://support.microsoft.com/en-in/help/2732595/lsass.exe-crashes-and-error-code-255-is-generated-in-windows-server-2008-r2-or-in-windows-7

--------------------------------

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_lsass.exe_50a2a82d60eaa41211b4392c16505b4ff5f630c4_cab_0f5ca4d5

Download Link : https://mega.nz/#!vAUSCAoJ!1jduSfxXSkQK3U-1Y2hAfLSll0bakjF86fb9LXF2Sds


Windows event Log:

https://mega.nz/#!TMV0iQxC!ZnPh12rTdqxBs8yT87tqN-_LBLY_xyHzmz8j6m6Ec1E

I have windows server 2008 r2 SP1 with all updates of windows update