Hi, I play STO for some time and after my better fun i invite my friend to STO.
He downloaded game from steam, after login game start updated, then crash windows.
We are looking for this problem on google, we try turn down firewal, antivir program, he dont have TeamViewer, we try force veryfi and on-demand, we try update all drivers and we try run in save mode.
He have Windows 7, exactly some PC like is my:
CPU: Intel I-5 4570 4core 3,20
Ram: 8GB
Graphic card: NVIDIA GeFoce GTX 760
I try put all my game files into rar and send him, but nothing, after login game start patch and all windows crash in blue.
Please some tips? Please help me find problem and get back to STO universe.
I'd have to agree in that it sounds like his system is unstable and memory is the first thing i would look at. There are many other possibilities like PSU, drivers, vid card, sound card, cpu, all sorts of settings in your bios, etc, etc. Extremely doubtful that it's a problem with the game.
Please do:
1) Open start, click on "Run"
2) type: eventvwr (and press enter)
3) Search for the specific BSOD event
4) Copy & paste that code on this forum.
That's quite the paradox, how could you nerf nerf when the nerf is nerfed. But how would the nerf be nerfed when the nerf is nerfed? This allows the nerf not to be nerfed since the nerf is nerfed? But if the nerf isn't nerfed, it could still nerf nerfs. But as soon as the nerf is nerfed, the nerf power is lost. So paradoxally it the nerf nerf lost its nerf, while it's still nerfed, which cannot be because the nerf was unable to nerf.
Please do:
1) Open start, click on "Run"
2) type: eventvwr (and press enter)
3) Search for the specific BSOD event
4) Copy & paste that code on this forum.
That's quite the paradox, how could you nerf nerf when the nerf is nerfed. But how would the nerf be nerfed when the nerf is nerfed? This allows the nerf not to be nerfed since the nerf is nerfed? But if the nerf isn't nerfed, it could still nerf nerfs. But as soon as the nerf is nerfed, the nerf power is lost. So paradoxally it the nerf nerf lost its nerf, while it's still nerfed, which cannot be because the nerf was unable to nerf.
Apparently he uses the latest NVIDIA driver (Driver File Version: 9.18.0013.3523 (English) - 3/4/2014 16:35:23).
Apparently STO isn't the only one with the 0x80*02 error while using these drivers. Have you tried to do a rollback?
Not yet but i try rollback it and let you now, but it is strange why windows crash after start patching this is not look like graphic problem but i try and let you now.
Comments
please post a copy of your dxdiag
1) Open start, click on "Run"
2) type: eventvwr (and press enter)
3) Search for the specific BSOD event
4) Copy & paste that code on this forum.
It might look something like:
0xc0000007e (etc) or 0x07e
I call it, the Stoutes paradox.
System Information
Time of this report: 4/10/2014, 16:40:36
Machine name: UNNAMED-PC
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130828-1532)
Language: Czech (Regional Setting: Czech)
System Manufacturer: MSI
System Model: MS-7821
BIOS: BIOS Date: 05/17/13 11:18:21 Ver: 04.06.05
Processor: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (4 CPUs), ~3.2GHz
Memory: 8192MB RAM
Available OS Memory: 8136MB RAM
Page File: 4614MB used, 11656MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 64bit Unicode
DxDiag Notes
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Input Tab: No problems found.
DirectX Debug Levels
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
Display Devices
Card name: NVIDIA GeForce GTX 760
Manufacturer: NVIDIA
Chip type: GeForce GTX 760
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_28471462&REV_A1
Display Memory: 4038 MB
Dedicated Memory: 1990 MB
Shared Memory: 2048 MB
Current Mode: 1680 x 1050 (32 bit) (60Hz)
Monitor Name: Obecn
................................................................
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2014-04-07T19:08:04.515217600Z" />
<EventRecordID>37145</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>unnamed-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">209</Data>
<Data Name="BugcheckParameter1">0x8</Data>
<Data Name="BugcheckParameter2">0x2</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0xfffff88001425a1d</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>
Apparently STO isn't the only one with the 0x80*02 error while using these drivers. Have you tried to do a rollback?
I call it, the Stoutes paradox.
Not yet but i try rollback it and let you now, but it is strange why windows crash after start patching this is not look like graphic problem but i try and let you now.
i just reinstal windows and all work just fine