Black Shark keeps rebooting ...

[SmukY]

... after some time in different missions and random times. First time was while I was flying towards Georgian border with 3 wingmen for first time (one of the missions in first BS campaign), and after half hour flying my computer just rebooted by itself. I thought it was overheating, so I've cleared it of dust and relaunched the mission. It rebooted again. Then I start the Courier mission - reboots after five minutes! I've thought that was a problem in mission or mods or something alike, so removed all 5 mods which I use from modman and I've put only my Ka-50 on a clean map. After take off I was flying around for 10 minutes. Well, same story happened. At least now I can only confirm that the problem doesn't exists in missions. Why are these reboots happening, I don't have any ideas.

 

My computer spec is:

 

C2D E6600 @2.40ghz

GeForce 9800GT 1GB

4GB RAM

550w power supply

 

The other problem is that when the rig reboots, the game doesn't creates any .crash files in Temp folder. Ever. I've checked Event Viewer and found this:

 

Critical    13.4.2011 1:41:08    Kernel-Power    41    (63)
------------------------------------------------------------
The system has rebooted without cleanly shutting down first. 
This error could be caused if the system stopped responding, 
crashed, or lost power unexpectedly.
------------------------------------------------------------
 - System     
   - Provider     
[  Name]  Microsoft-Windows-Kernel-Power    
[  Guid]  {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
   
EventID 41        
Version 2        
Level 1        
Task 63        
Opcode 0        
Keywords 0x8000000000000002    
  
- TimeCreated     
[  SystemTime]  2011-04-12T23:41:08.345215600Z
       
EventRecordID 99303       
Correlation    

   - Execution     
[  ProcessID]  4    
[  ThreadID]  8 
Channel System        
Computer SmukY-PC    

   - Security     
[  UserID]  S-1-5-18

   - EventData     
BugcheckCode 0    
BugcheckParameter1 0x0    
BugcheckParameter2 0x0    
BugcheckParameter3 0x0    
BugcheckParameter4 0x0    
SleepInProgress false    
PowerButtonTimestamp 0

I have the Steam version, and I'm using the Saitek X52 joystick, Simped rudder pedals and TrackIR 4: PRO. Hope any of that informations will help you to find the cause of my problems. :(

 

If you have any questions just shoot 'em!

DxDiag.txt

Error.txt

errors.txt

Edited April 13, 2011 by SmukY

[PoleCat]

This sounds a lot like a hardware issue to me. Perhaps you can run a memory/system/video stress test and/or benchmark to see if stressing the system causes a reboot outside of the game.

 

Please see here. http://support.microsoft.com/kb/2028504

 

Out

Edited April 13, 2011 by PoleCat

[SmukY]

Well I did the stress test with BurnIn Test 6.0.

 

I've keep it running for two hours and no errors were found. And it was testing the CPU, 2D, 3D and all that other stuff simultaneously. I have to mention that there were 2 games which rebooted the computer: The Sims: Medieval and Crysis 2. But they kept rebooting only right after intro videos, not while playing. But that was like only 2 times, and after these reboots they were running normal, I've even completed the Crysis. No hear no see of any reboots ... until playing Black Shark once again after completing the Crysis 2. Dunno. :noexpression:

 

EDIT1: I'll check the link you posted.

 

EDIT2: Nope, nothing useful there. But thanks anyway ... I hope someone has any ideas about this or I'll just uninstall the game and won't run it again until I get the better rig ... like in 10 years.

Edited April 13, 2011 by SmukY

[oritpro]

This could still be a hardware problem or a driver problem. Games and applications runs in user mode or ring 3, and are not capable of crashing Windows 7. Drivers run in kernel mode or ring 0, and can crash Windows 7 or any version of Windows.

 

It looks like your system bugchecked.

 

Do you see a file called \windows\memory.dmp or any files in \windows\minidump that are dated around time your system crashed? If so, they might contain a clue. WinDBG from the Microsoft DDK can be used to inspect these files and there's a Systernals tool available as well. The former would be better.

 

Sometimes these spontaneous reboots don't generate a memory dump:

* Right click on My Computer

* Select properties

* Click the advanced tab

* Click the startup and recovery button

* Uncheck the automatically restart checkbox under system failure

 

This should prevent the computer from restarting and allow you to see the cause of the bugcheck the next time it happens.

[SmukY]

Nope, the minidump map is empty. But i'll uncheck this auto restart after system failure and i'll take a photo if it will display any informations. Thanks. I'll report ASAP.

 

EDIT: Strange ... Until I unchecked this automatic restart I didn't experienced any reboots! I even managed to complete the Courier mission. I'll do this campaign mission where I spotted those reboots for first time again and I'll see if there will be same too. Otherwise, you'll be first to know.

[oritpro]

Simply un-checking the automatic restart box wouldn't solve a spontaneous bugcheck problem.

 

I suspect that there is something wrong with your video card. I've seen video hardware "partially fail" where a small section of the GPU chip responsible for a specific feature will go out and cause a system crash when it's called to do work by an application such as a game. Burn-in test might not be exercising that section/feature of the GPU so I'd consider that test inconclusive at this point.

 

Any hardware failure will cause Windows to intermittently reboot or shutdown. Driver problems are more likely to result in a memory dump whereas hardware failures do not.

[Mustang]

What is your OS? 32 or 64 bit?

[SmukY]

64-bit. Maybe is that impossible, but that's what happened... it does look that the un-checking box for automatic restart actually fixed my Black Shark game. I've managed to complete the mission in which my rig rebooted like 3 times after half hour playing, as I described before. It took like one and half hours to complete and I didn't experienced any problems.

 

EDIT: Well oritpro ... you were right. This didn't helped that much, because rig got rebooted again while playing BS. And also no .crash, error files were created, the minidump map is still empty, I can't find any memory.dmp file in windows map. Even with un-checked automatic restart option, the machine still just rebooted without showing any informations. Only blackscreen, BIOS load up and then it ask me how if I want normal start-up of windows or safe mode and etc. I will run the WinDBG ...

[PoleCat]

Try running memtest http://www.memtest.org/ (at least one full pass) and then Rithdrbl http://www.daionet.gr.jp/~masa/rthdribl/ (Let rthdrbl run for a while to stress the video card) or furmark http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

 

If it is your memory or your video card these might expose which it is. Failing that I would also suspect your PSU. If you can switch it out and try another do so and test again.

 

Best of luck.

 

Out

Edited April 13, 2011 by PoleCat

[oritpro]

This sounds like a hardware problem. A driver problem will usually result in a memory dump and the problem driver will appear on the stack preceeding a call to KeBugcheck.

 

It could be anything; Video card, sound card, chipset, processor, etc. Start with the simple things first.

* If you've overclocked anything in your system before, even if it's not overclocked now, then those components are likely suspects.

* Disable your sound card in the BIOS or device mangler and play without sound. See if the problem re-occurs.

* Beg, borrow, steal another video card even if it's not as good as the one your using. It should be able to play the game at minimum settings though. See if the problem re-occurs.

 

Beyond that, I am out of ideas.

Edited April 13, 2011 by oritpro

[SmukY]

Well it does looks that the main cause of those reboots which occures only in the Black Shark remains unknown. Did ran a memtest, both rthdrbl and furmark tests, no errors/glitches or smth found.

 

oritpro, I was playing with overclocking but that was some time ago, so I'm running default frequency of CPU like 1 year or so. Maybe it's just that my rig is becoming too old and can't run the game in the way I want. If I get a chance I will try the Black Shark on other video card, and about sound - I've disabled it and yet the rig still crashes.

 

Well, thanks for you both for your effort. Maybe the formatting at one time will solve the problems, but this will not be that soon, because I don't have the time and mood for going all over this shit with installations of everything I need. Anyway, again thanks for your help and patience ...

[TAIPAN_]

Hi,

I may know what it is... I had this EXACT problem and it was only black shark that stressed my system to the point of rebooting from not enough amps to my graphics card.

 

Which power supply do you own?

What brand and what amps?

 

I had an 850w and not a good brand, when I investigated I found the 12v rail to be not so many amps. So I upgraded to a Corsair HX1000 - after the PSU upgrade I never ever had a reboot again.

 

So it was definitely power supply ;)

[SmukY]

Hmm, yeah, it's very possible that's my PSU is a main cause of those reboots. When I was buying this rig 4 years ago, I bought one cheap LC Power PSU for 90 or 100€ too and it provides 550w for my rig. I'll have to borrow the other PSU from any friends, the problem is just that I don't believe if anyone of my friends actually invested more than 150€ in their PSU. :)

[TAIPAN_]

Yep but I think with a powerful graphics card and a quad core you need stable power and amps.

 

Got any specs on your psu re the amps on 12v?

 

With PSU brand name matters more than any other component.

 

This one for example http://www.newegg.com/Product/Product.aspx?Item=N82E16817139011

[SmukY]

Ok, the Black Shark now is not the only game which reboots randomly - The TDU2 causes same spontaneous reboots after starting the game and I still don't know why those reboots are happening and what's their main cause. It's very posible that's a PSU, but currently my wallet is thick like as a plain paper. Anyway The Windows event viewer has same error log named Kernel-Power (Event ID 41) and they're logged in times when the both games crashed. I've tried to change the audio drivers (I had High Definition Audio, now I have Realtek High Definition Audio), disabled all USB devices except mouse and keyboard and yet errors are still happening. But I'm surprised why I don't have any problems in DCS: Warthog? It can run like all the day and there won't be any reboots/errors.

 

If that helps, my motherboard is an Asus P5K. Forgot to mention that. Now I'm downloading the SP1 for Windows 7 but I somehow doubt that will significantly help.

 

It's posible that the dust (which is very hard to reach with vacuum cleaner) in PSU can somehow interfere with computer's working?

 

EDIT: Well it does looks that the SP1 actually helped me. I will reinstall the Black Shark back to see if there are improvements too.

Edited April 27, 2011 by SmukY

[Bodo]

Dunno if it's been mentioned but it's too hot and I can't be bothered to read!!

 

I would check your CPU temperature using Core Temp or Real Temp and then run an Intel Burn Test.

 

Here are the links

 

Intel Burn Test

 

Core Temp

 

Real Temp

 

Run Intel burn test on a high setting for at least 5 passes, monitor your CPU temperature using one of the apps. This will at least eliminate any possible problems there. I would also go into your BIOS and load the defaults and only adjust settings like boot device to be your main OS installed drive, also you could disable any hardware you don't use like serial ports/LPT ports etc.

 

After this I would then do a full reseating of your GPU and also check your memory is seated properly. Then I would run a memtest for at least 2-3 passes. After this I would also suggest reinstalling every driver for your system. So, a full reinstall of your motherboard drivers, a reinstall of your GPu drivers, preferably cleaning them off first (nvidia's driver install allows for a clean install option) then install sound card and other peripheral drivers after that.

 

Hope this helps. Sorry if I've reiterated others' points.

[SmukY]

Nope, believe me, it's not the overheating, the CPU temperature levels are below average (i checked them right after rebooting). Memtest was fine, and I hardly believe that the reinstalling of drivers could help anything. Now I'm installing the BS and I will report if I'll encounter any reboots.

[Bodo]

Ok, point taken, but, what/how do you mean you checked them after rebooting?

 

You need to check them when they're under load, I'd say.

 

Kernel power problems means your BIOs isn't set up with the correct voltage requirements for your components. Reset the BIOS to default and then set your DRAM and CPU voltages to the rated specification. After that, consider the PSU.

 

List your full PC spec, please. Every component, HDDs, GPU, CPU, RAM amount etc...

Edited April 27, 2011 by Bodo

[oritpro]

It's posible that the dust (which is very hard to reach with vacuum cleaner) in PSU can somehow interfere with computer's working?

 

EDIT: Well it does looks that the SP1 actually helped me. I will reinstall the Black Shark back to see if there are improvements too.

 

Don't use a vacuum cleaner on your computer, use canned air instead. You risk zapping your system with static electricity using a vacuum cleaner.

 

If you've updated all your drivers and the problem still occurs then it's likely a hardware issue...possibly something wrong with the OS that a re-install might fix.

[EtherealN]

Don't use a vacuum cleaner on your computer, use canned air instead. You risk zapping your system with static electricity using a vacuum cleaner.

 

This needs repeating, because it is extremely important.

I myself is fortunate enough to actually have an air compressor in the garage, but the function is the same.

 

Static electricity is a very real threat to many computer components, and for some components you can kill them with so little that you won't actually feel the discharge.

[71st_Mastiff]

yes I some how killed a hard drive and there was no indication I had static when I did all the discharges for it.

[SmukY]

Problem is solved. I had to buy new PSU, because the previous one was apparently ageing and it wasn't producing full wattage and that's why the 3D games were rebooting after some minutes. I've bought Corsair's modular 750w PSU (I've found one relativelly cheap, for around 130€) and it'll be good even for the new computer when I'll be building one. I'm very appreciated and I want to say thanks for all of you who took some time to help me.

Edited May 4, 2011 by SmukY

[Bodo]

:) Good news, and good PSU.

[oritpro]

Glad to hear you fixed it. Having a bad power supply is like putting bad gas in your car, it simply won't run right. For those that suspected the power supply, good call!

 

I have several Corsair PSU's and they are solid in my book.