Overclock.net › Forums › Intel › Intel - General › (SOLVED) PC shuts off without any warning
New Posts  All Forums:Forum Nav:

(SOLVED) PC shuts off without any warning  

post #1 of 13
Thread Starter 
Hi,

I'm experiencing random shut downs and restarts when I play Bioshock Infinite. However if I'm playing Far Cry 3, Crysis 3 and Arma 3 at the highest settings I don't get it. I get no warning, no bsod, just a shutdown and a few seconds later a restart.
I looked over the dmp file but that is a bit out of my league.

Specs:

CPU: i5 2500K @ 4.2 GHz (X.M.P. profile)
Custom water cooling (see sig)
MoBo: Asus Maximus IV Gene-Z, bios 0902
RAM: 16Gb Corsair Vengeance @ 1600MHz (CMZ8GX3M2A1600C9)
PSU: Corsair HX850W
SSD 1: Corsair Force 3 120GB (Windows 7 Ultimate 64-bit)
SSD 2: Corsair Force 3 120GB (games)
HDD: Western Digital 320Gb (stuff)
GPU: Asus Matrix HD 7970 (stock @ 1050 MHz)

Bioshock Infinite screenie, 2 seconds later the shutdown Warning: Spoiler! (Click to show)

dump.zip 24k .zip file

thinking.gif Ideas?
post #2 of 13
Your overclock might be a little bit unstable - you could dial down by 100-200mhz and see if that makes any difference.
post #3 of 13
The few times this has happened to me it's either.

1. A bad OC as mentioned above.
2. Overheating, but since you have a custom WC setup you probably have the temps on lock. I would look into it just to be sure. smile.gif
post #4 of 13
Looks like a memory bsod. A critical os process could not access memory, csrss.exe.

csrss.exe is the user mode client / server runtime subsystem. It handles user mode functions involving console programs, threading and dll assemblies.

Most likely Bioshock Infinate is much more intensive memory intensive than the other games. It could be trying to thread preloading of data into ram in order to stream level data to your video card in order to reduce load times.

Are you overclocking your memory? Have you manually checked the voltages and timing?

Have you done any stability testing. P95 with small FFT's to verify your processor overclock is good?

If everything is stock with your memory and you have verified your processor overclock then I would look at bumping up your voltage just a tad. I used to run some corsair dominator memory that needed a little extra voltage to be stable even at stock speed and timings.

Also, I know it's silly but I would assume your video card drivers are up to date and you have checked the forums related to the game to make sure other people aren't having the same issue. There could be application bugs that are causing the issue. =p

Also if you hit F8 or when your booting you can select "Disable automatic restart on system failure." which should allow you to view the error at the time of failure.
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\djenkins\Desktop\dump\011913-7612-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0304e000 PsLoadedModuleList = 0xfffff800`03292670
Debug session time: Sat Jan 19 01:47:04.272 2013 (UTC - 4:00)
System Uptime: 0 days 0:08:02.069
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800d44c060, fffffa800d44c340, fffff800033cc460}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800d44c060, Terminating object
Arg3: fffffa800d44c340, Process image file name
Arg4: fffff800033cc460, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa800d44c060

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

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

BUGCHECK_STR:  0xF4_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06aece38 fffff800`03454822 : 00000000`000000f4 00000000`00000003 fffffa80`0d44c060 fffffa80`0d44c340 : nt!KeBugCheckEx
fffff880`06aece40 fffff800`03400e0b : ffffffff`ffffffff fffffa80`0e174b50 fffffa80`0d44c060 fffffa80`0d44c060 : nt!PspCatchCriticalBreak+0x92
fffff880`06aece80 fffff800`0337ff04 : ffffffff`ffffffff 00000000`00000001 fffffa80`0d44c060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176e6
fffff880`06aeced0 fffff800`030cc253 : fffffa80`0d44c060 fffff800`c0000005 fffffa80`0e174b50 00000000`02210340 : nt!NtTerminateProcess+0xf4
fffff880`06aecf50 fffff800`030c8810 : fffff800`03117b7f fffff880`06aeda38 fffff880`06aed790 fffff880`06aedae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`06aed0e8 fffff800`03117b7f : fffff880`06aeda38 fffff880`06aed790 fffff880`06aedae0 00000000`02211e50 : nt!KiServiceLinkage
fffff880`06aed0f0 fffff800`030cc642 : fffff880`06aeda38 00000000`0001226c fffff880`06aedae0 00000000`02211928 : nt! ?? ::FNODOBFM::`string'+0x488a4
fffff880`06aed900 fffff800`030cb1ba : 00000000`00000001 00000000`02210a58 00000000`0224e501 00000000`0001226c : nt!KiExceptionDispatch+0xc2
fffff880`06aedae0 00000000`770d8e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`02210a60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770d8e3d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_c0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_c0000005_IMAGE_csrss.exe

Followup: MachineOwner

Edited by zer0patches - 3/31/13 at 9:17pm
post #5 of 13
Thread Starter 
thanx all, I'll look into it!

cheers.gif
post #6 of 13
Thread Starter 
Quote:
Originally Posted by Broseidon View Post

Your overclock might be a little bit unstable - you could dial down by 100-200mhz and see if that makes any difference.

What if I just increase the voltage a bit?
Quote:
Originally Posted by RemagCP View Post

The few times this has happened to me it's either.

1. A bad OC as mentioned above.
2. Overheating, but since you have a custom WC setup you probably have the temps on lock. I would look into it just to be sure. smile.gif

I've had this OC for over 2 years, nothing has changed except for the graphics card. I check the temps running P95, max temp at stress test was 56C (only one core). I could add 2 extra fans for push/pull.
Quote:
Originally Posted by zer0patches View Post

Looks like a memory bsod. A critical os process could not access memory, csrss.exe.

csrss.exe is the user mode client / server runtime subsystem. It handles user mode functions involving console programs, threading and dll assemblies.

Most likely Bioshock Infinate is much more intensive memory intensive than the other games. It could be trying to thread preloading of data into ram in order to stream level data to your video card in order to reduce load times.
Warning: Spoiler! (Click to show)
Are you overclocking your memory? Have you manually checked the voltages and timing?

Have you done any stability testing. P95 with small FFT's to verify your processor overclock is good?

If everything is stock with your memory and you have verified your processor overclock then I would look at bumping up your voltage just a tad. I used to run some corsair dominator memory that needed a little extra voltage to be stable even at stock speed and timings.

Also, I know it's silly but I would assume your video card drivers are up to date and you have checked the forums related to the game to make sure other people aren't having the same issue. There could be application bugs that are causing the issue. =p

Also if you hit F8 or when your booting you can select "Disable automatic restart on system failure." which should allow you to view the error at the time of failure.
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\djenkins\Desktop\dump\011913-7612-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0304e000 PsLoadedModuleList = 0xfffff800`03292670
Debug session time: Sat Jan 19 01:47:04.272 2013 (UTC - 4:00)
System Uptime: 0 days 0:08:02.069
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800d44c060, fffffa800d44c340, fffff800033cc460}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800d44c060, Terminating object
Arg3: fffffa800d44c340, Process image file name
Arg4: fffff800033cc460, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa800d44c060

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

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

BUGCHECK_STR:  0xF4_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06aece38 fffff800`03454822 : 00000000`000000f4 00000000`00000003 fffffa80`0d44c060 fffffa80`0d44c340 : nt!KeBugCheckEx
fffff880`06aece40 fffff800`03400e0b : ffffffff`ffffffff fffffa80`0e174b50 fffffa80`0d44c060 fffffa80`0d44c060 : nt!PspCatchCriticalBreak+0x92
fffff880`06aece80 fffff800`0337ff04 : ffffffff`ffffffff 00000000`00000001 fffffa80`0d44c060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176e6
fffff880`06aeced0 fffff800`030cc253 : fffffa80`0d44c060 fffff800`c0000005 fffffa80`0e174b50 00000000`02210340 : nt!NtTerminateProcess+0xf4
fffff880`06aecf50 fffff800`030c8810 : fffff800`03117b7f fffff880`06aeda38 fffff880`06aed790 fffff880`06aedae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`06aed0e8 fffff800`03117b7f : fffff880`06aeda38 fffff880`06aed790 fffff880`06aedae0 00000000`02211e50 : nt!KiServiceLinkage
fffff880`06aed0f0 fffff800`030cc642 : fffff880`06aeda38 00000000`0001226c fffff880`06aedae0 00000000`02211928 : nt! ?? ::FNODOBFM::`string'+0x488a4
fffff880`06aed900 fffff800`030cb1ba : 00000000`00000001 00000000`02210a58 00000000`0224e501 00000000`0001226c : nt!KiExceptionDispatch+0xc2
fffff880`06aedae0 00000000`770d8e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`02210a60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770d8e3d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_c0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_c0000005_IMAGE_csrss.exe

Followup: MachineOwner

Are you overclocking your memory? Have you manually checked the voltages and timing?
I have the XMP profile; it sets the following automatically; DRAM freq: 800.1 MHz, timings: 9-9-9-24-2T. Voltage is set on: 1.5009 V - 1.5018V
*edit* I switched back to stock speed and timings (1333MHz)

Have you done any stability testing. P95 with small FFT's to verify your processor overclock is good?
Yes, I've run Intel stress test and Prime95 (bench, torture & ECM); all passed.

If everything is stock with your memory and you have verified your processor overclock then I would look at bumping up your voltage just a tad. I used to run some corsair dominator memory that needed a little extra voltage to be stable even at stock speed and timings.
*edit* I added 0.256V for the ram(1 +). I also gave a bit more voltage to the Vcore.

Also, I know it's silly but I would assume your video card drivers are up to date and you have checked the forums related to the game to make sure other people aren't having the same issue. There could be application bugs that are causing the issue. =p
Latest driver installed but I haven't checked the forums yet.

Also if you hit F8 or when your booting you can select "Disable automatic restart on system failure." which should allow you to view the error at the time of failure.
*edit* I already unchecked that box
Edited by SortOfGrim - 4/1/13 at 8:25am
post #7 of 13
Quote:
*edit* I added 0.256V for the ram(1 +). I also gave a bit more voltage to the Vcore.

is that a typo? really shouldn't need more than 1.550 volts, +0.050 volts. I would actually even try 1.525 first and then bump it up to 1.550 then 1.575v. JEDEC standards for ddr3 1.5v mem allows for +/- 0.075v variance.

A small bump to vcc as you have already done shouldn't hurt.

Whats your vcore/vcc at?

Any success so far? Seems like you are on the right track. =p
post #8 of 13
Thread Starter 
Quote:
Originally Posted by zer0patches View Post

is that a typo? really shouldn't need more than 1.550 volts, +0.050 volts. I would actually even try 1.525 first and then bump it up to 1.550 then 1.575v. JEDEC standards for ddr3 1.5v mem allows for +/- 0.075v variance.

A small bump to vcc as you have already done shouldn't hurt.

Whats your vcore/vcc at?

Any success so far? Seems like you are on the right track. =p

That was a typo indeed.

RAM: 1.515V (+0.00625v),
CPU: 1.176v, (1.368v @ 4.2GHz / 1.016v @ 1.6GHz)
VCCSA: 1.118v (auto)
PLL: 1.806v (auto)
PCH: 1.065v (auto)
post #9 of 13
Quote:
Originally Posted by SortOfGrim View Post

That was a typo indeed.

RAM: 1.515V (+0.00625v),
CPU: 1.176v, (1.368v @ 4.2GHz / 1.016v @ 1.6GHz)
VCCSA: 1.118v (auto)
PLL: 1.806v (auto)
PCH: 1.065v (auto)

I would bump ram up to 1.550.

CPU voltage looks a little high for the OC.

VCCA is pretty high for your ram / OC already. Intel max spec is 0.971 for your chip. I don;t have a lot of xp with your chipset / socket though so I don;t know what the reasonable limit is but above intel max spec you should expect some degradation. Over time you will not be able to hit the same clocks with the same voltage.

If you have been running these voltages for a long time it could be an issue but every processor is different.

I don't think you would need that much over 0.925 which is the default for your chip with such a low overclock and running stock speed ram.

I would try lowering your PLL a bit. Auto is 1.8 which is usually more than you need. I am running 4.8ghz @1.335v, 2080mhz ram @1.6v ram, 1.7v pll and 1.175vccsa/vtt. Intel max spec for my socket/vccsa is 1.2v though.

Does the game run with everything stock / optimized defaults?

If all your stability testing is passing and other games work and this game won;t work with everything clocked at stock speeds it's possible it could be a game/driver installation issue.

On a side note, Auto is really bad. It always sets way more voltage than you need. I have an Rampage Extreme IV and it was trying to set my vtt/vcca at 1.4 on auto lol.
Edited by zer0patches - 4/3/13 at 9:46am
post #10 of 13
Thread Starter 
Quote:
Originally Posted by zer0patches View Post

I would bump ram up to 1.550.

CPU voltage looks a little high for the OC.

VCCA is pretty high for your ram / OC already. Intel max spec is 0.971 for your chip. I don;t have a lot of xp with your chipset / socket though so I don;t know what the reasonable limit is but above intel max spec you should expect some degradation. Over time you will not be able to hit the same clocks with the same voltage.

If you have been running these voltages for a long time it could be an issue but every processor is different.

I don't think you would need that much over 0.925 which is the default for your chip with such a low overclock and running stock speed ram.

I would try lowering your PLL a bit. Auto is 1.8 which is usually more than you need. I am running 4.8ghz @3.35v, 2080mhz ram @1.6v ram, 1.7v pll and 1.175vccsa/vtt. Intel max spec for my socket/vccsa is 1.2v though.

Does the game run with everything stock / optimized defaults?

If all your stability testing is passing and other games work and this game won;t work with everything clocked at stock speeds it's possible it could be a game/driver installation issue.

On a side note, Auto is really bad. It always sets way more voltage than you need. I have an Rampage Extreme IV and it was trying to set my vtt/vcca at 1.4 on auto lol.

wow, you might think asus/intel has the best in for their product. Let me check stock speeds first.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel - General
This thread is locked  
Overclock.net › Forums › Intel › Intel - General › (SOLVED) PC shuts off without any warning