Jump to content

Windows Server Crashing


Ziogref
Go to solution Solved by Beardyname,

Recommended Posts

  • Solution
Beardyname

I ran it for about 1min then it crashed (BSOD screenshot linked below) it the cpu stayed under 90c

 

https://docs.google.com/file/d/0B7f8lJwBgFSveWR4bk96NmtHdUk/edit?usp=docslist_api

 

(sorry if it's not Hyperlinked, i used my phone to post this)

 

yep it's either hardware/driver issue. :(

 

I would re-apply the cooler on your cpu and double check so it's fastened properly, fresh thermal paste and all that. If it's still crashing, i would either run ram diagnostics or pull the dimm's 1 by 1 and see if it's either of them making it go haywire.

 

If you think it's a driver issue, then re-check all the drivers and what not. Should all be available on your motherboard manufacturers homepage. (or computer retail thing if it's a pre-buit one).

 

Hopefully you can figure out it :)

  • Like 1
Link to comment
Share on other sites

yep it's either hardware/driver issue. :(

 

I would re-apply the cooler on your cpu and double check so it's fastened properly, fresh thermal paste and all that. If it's still crashing, i would either run ram diagnostics or pull the dimm's 1 by 1 and see if it's either of them making it go haywire.

 

If you think it's a driver issue, then re-check all the drivers and what not. Should all be available on your motherboard manufacturers homepage. (or computer retail thing if it's a pre-buit one).

 

Hopefully you can figure out it :)

 

Yeah i will re-apply the thermal paste and run memtest on all 4 dimms, its weird because it started doing it about a month or 2 ago, before that no problems, thats why i assumed the problem with mediabrowser. I Have already installed the drivers from gigabyte, i will see if intel has a more up to date chipset drivers. Thanks for all your help

Link to comment
Share on other sites

mouseware
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80001b6cb9e, fffff880075c0ab0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+173 )

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff80001b6cb9e, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880075c0ab0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ObpWaitForMultipleObjects+173
fffff800`01b6cb9e 0fb64718        movzx   eax,byte ptr [rdi+18h]

CONTEXT:  fffff880075c0ab0 -- (.cxr 0xfffff880075c0ab0)
rax=00000000ffe0fffc rbx=fffff8a00b436540 rcx=fffdfa8009de8130
rdx=0000000000000001 rsi=0000000000000001 rdi=fffdfa8009de8130
rip=fffff80001b6cb9e rsp=fffff880075c1490 rbp=fffff880075c1ca0
 r8=0000000000000000  r9=fffff8a00b403000 r10=fffffa800a4da060
r11=fffffffffffffd80 r12=fffff880075c19a0 r13=fffff8a002e21b30
r14=0000000000000000 r15=0000000000000002
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!ObpWaitForMultipleObjects+0x173:
fffff800`01b6cb9e 0fb64718        movzx   eax,byte ptr [rdi+18h] ds:002b:fffdfa80`09de8148=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0x3B

PROCESS_NAME:  ffmpeg.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80001b6cb9e

STACK_TEXT:  
fffff880`075c1490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x173


FOLLOWUP_IP: 
nt!ObpWaitForMultipleObjects+173
fffff800`01b6cb9e 0fb64718        movzx   eax,byte ptr [rdi+18h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObpWaitForMultipleObjects+173

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  548a6e28

STACK_COMMAND:  .cxr 0xfffff880075c0ab0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpWaitForMultipleObjects+173

BUCKET_ID:  X64_0x3B_nt!ObpWaitForMultipleObjects+173

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

ffmpeg.exe is crashing the system... 

Link to comment
Share on other sites

JeremyFr79

Yeah i will re-apply the thermal paste and run memtest on all 4 dimms, its weird because it started doing it about a month or 2 ago, before that no problems, thats why i assumed the problem with mediabrowser. I Have already installed the drivers from gigabyte, i will see if intel has a more up to date chipset drivers. Thanks for all your help

Never use manufacturer drivers always use drivers directly from nVidia/AMD etc.  Also I have found that 3rd party memtest software like memtestx86 find issues that windows memtest doesn't.  I've seen memory that passes windows memory test throw 1000's of errors when running memtestx86

Edited by JeremyFr79
Link to comment
Share on other sites

Beardyname
*******************************************************************************
*snip*

ffmpeg.exe is crashing the system... 

 

 

If it was only ffmpeg that is crashing the system, it would not blue-screen on a cpu/ram benchmarking test :)

Link to comment
Share on other sites

mouseware

If it was only ffmpeg that is crashing the system, it would not blue-screen on a cpu/ram benchmarking test :)

 

The screen shot indicates 7e stop, the minidump was 3b... i'd have to see the dump from the 7e crash to debug...

Edited by mouseware
Link to comment
Share on other sites

ok. so I have been doing some thinking. The mobo and CPU came out of my old gaming RIG as that was experiencing BSOD's aswell when under load (opening games, or running prime 95) so i replaced the mobo and CPU. then a year later i used those parts to build my home server (red flag here) as the server wasnt going to do anything intensive, and since i dont look at the server physically (its hidden in a corner) i forgot about this problem. From memory (this all happened like 3 years ago) it was the motherboard at fault and i was unable to find a replacement. so as the resolution im replacing the MoBO and CPU and throwing the old ones out. I doubt i will be able to sell the cpu, and it will hurt throwing out that core i7 860. Thanks for all the help, now i just need to find the best answer to close the thread. I appreciate all your support, i didnt expect that many people would post, thank you all for your kind support.

Link to comment
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
×
×
  • Create New...