I'm fortunate that I work in an environment where I can log into the game from my office... That said I can't get STO to work on my system, though it does play other games like WoW just on lowered settings...But STO doesn't just not play, it gives me a BSOD when I try to run it...
I double click the game icon, it gives me a message about my video settings and I can choose "Lowered Settings" or "Recommended Settings" either one I choose flashes my screen black like it's about to load, but then goes to a BSOD with a bunch of error messages on it.
Unfortunately I didn't write down the specific messages

maybe later i'll update this with the info...
System specs are
Windows XP SP3
Intel Core 2 Quad @ 2.66
2GB mem
Intel Chipset on the video card - unfortunately I don't know any of the specs for it..
Comments
he's using a quad core with windows xp..
talk about a waste :P
Actually someone in my fleet is using a onboard video card and can still play with all the settings down to their minimum. not sure what his specs are.. but it is possible.
Not all integrated video are created equal and I'm not surprised the OP can't run the game as the vid card is below minimum spec.
Try setting game to safe mode in the STO launcher to get all the settings down to minimum.
Intel HD graphics should work
But yes a quad core on xp is such a waste LOL invest in windows 7 64bit trust me you wont reget it
Also post a dxdiag report might help out
Start / run type dxdiag then click save all infomation and post on the forums
I work in an environment where I can log into the game from my office
Not my system, not gonna upgrade it
Cheers
AMD 9950 quad core
vista 64 ultimate
gigabyte - 9800gt
geil black dragon - 8gig
So im guessing ther may be a problem with the game for some users
If it gets fixed in the next couple of days then fine if not i'll just cancell my subscription & go bk to playing eve
Blue Screen crashing? I'm betting that it is a driver issue. what's the blue screen error code ?
If it's rebooting too quickly, you can go into System Properties -> Advanced and under the Startup/Recovery settings button, uncheck the "Automatically restart" checkbox. That way the BSOD will stay on screen long enough to read.
This could be a driver issue, but just as likely could be an overheat, bad memory, bad video card, or any number of other things, most of them hardware-related.
1, Seems fine in safe mode no blue screen yet, but obviously i dont want to play is safe mode
Update your drivers and check you GPU and system ram.
As for the BSOD : PAGE_FAUlT_IN_NOPAGE RER
STOP 0x00000050 0x00000001 0x8053B902 0x00000001
And Here the DxDaig
System Information
Time of this report: 2/13/2010, 08:35:28
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_qfe.080814-1300)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 01/09/09 15:16:56 Ver: 08.00.14
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 5200+, MMX, 3DNow (2 CPUs), ~2.7GHz
Memory: 3072MB RAM
Page File: 338MB used, 4618MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode
DxDiag Notes
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.
DirectX Debug Levels
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
Display Devices
Card name: NVIDIA GeForce 8400 GS
Manufacturer: NVIDIA
Chip type: GeForce 8400 GS
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_06E4&SUBSYS_82781043&REV_A1
Display Memory: 512.0 MB
Current Mode: 1024 x 768 (32 bit) (85Hz)
Monitor: Dell M990
Monitor Max Res: 1600,1200
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.9621 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 1/11/2010 23:03:33, 6359168 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 1/11/2010 23:03:33, 10276768 bytes
Device Identifier: {D7B71E3E-45A4-11CF-6656-73A200C2CB35}
Vendor ID: 0x10DE
Device ID: 0x06E4
SubSys ID: 0x82781043
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run
Sound Devices
Description: Realtek HD Audio output
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_10438290&REV_1001
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RtkHDAud.sys
Driver Version: 5.10.0000.5730 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 10/31/2008 06:38:08, 4942336 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 8000, 192000
Static/Strm HW Mix Bufs: 33, 32
Static/Strm HW 3D Bufs: 33, 32
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: Yes, Yes
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
Sound Capture Devices
Description: Realtek HD Audio Input
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: RtkHDAud.sys
Driver Version: 5.10.0000.5730 (English)
Driver Attributes: Final Retail
Date and Size: 10/31/2008 06:38:08, 4942336 bytes
Cap Flags: 0x41
Format Flags: 0xFFF
Pretty conclusive evidence you have a fault on your machine, not with the game
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: n/a
Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Registry: OK
Test Result: Not run
DirectInput Devices
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: USB-compliant keyboard
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x0518, 0x0001
FF Driver: n/a
Device Name: USB-compliant keyboard
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x0518, 0x0001
FF Driver: n/a
Poll w/ Interrupt: No
Registry: OK
USB Devices
+ USB Root Hub
| Vendor/Product ID: 0x10DE, 0x055E
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 4/13/2008 19:15:38, 59520 bytes
| Driver: usbd.sys, 8/23/2001 07:00:00, 4736 bytes
Gameport Devices
PS/2 Devices
+ HID Keyboard Device
| Vendor/Product ID: 0x0518, 0x0001
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 4/13/2008 19:09:50, 14592 bytes
| Driver: kbdclass.sys, 4/13/2008 19:09:48, 24576 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 4/14/2008 05:43:22, 40840 bytes
| Driver: kbdclass.sys, 4/13/2008 19:09:48, 24576 bytes
|
+ HID-compliant mouse
| Vendor/Product ID: 0x0461, 0x4D42
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouclass.sys, 1/8/2009 15:41:28, 23040 bytes
| Driver: mouhid.sys, 1/8/2009 15:38:03, 12160 bytes
|
+ HID-compliant mouse
| Vendor/Product ID: 0x0518, 0x0001
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouclass.sys, 1/8/2009 15:41:28, 23040 bytes
| Driver: mouhid.sys, 1/8/2009 15:38:03, 12160 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 4/14/2008 05:43:22, 40840 bytes
| Driver: mouclass.sys, 1/8/2009 15:41:28, 23040 bytes
DirectPlay Service Providers
DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.5512)
DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.5512)
DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.5512)
DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.5512)
Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.5512)
IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.5512)
Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.5512)
Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.5512)
DirectPlay Voice Wizard Tests: Full Duplex: Not run, Half Duplex: Not run, Mic: Not run
DirectPlay Test Result: Not run
Registry: OK
DirectPlay Adapters
DirectPlay8 Serial Service Provider: COM1
DirectPlay8 TCP/IP Service Provider: Local Area Connection 2 - IPv4 -
DirectPlay Voice Codecs
Voxware VR12 1.4kbit/s
Voxware SC06 6.4kbit/s
Voxware SC03 3.2kbit/s
MS-PCM 64 kbit/s
MS-ADPCM 32.8 kbit/s
Microsoft GSM 6.10 13 kbit/s
TrueSpeech(TM) 8.6 kbit/s
DirectPlay Lobbyable Apps
Disk & DVD/CD-ROM Drives
Drive: C:
Free Space: 451.6 GB
Total Space: 476.9 GB
File System: NTFS
Model: ST3500630AS
Drive: F:
Free Space: 23.5 GB
Total Space: 238.5 GB
File System: NTFS
Model: Seagate FreeAgentDesktop USB Device
Drive: E:
Model: PIONEER DVD-RW DVR-112 USB Device
Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.5593 (English), 1/8/2009 15:06:23, 62976 bytes
Drive:
Model: HL-DT-ST DVDRAM GSA-4160B
Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.5593 (English), 1/8/2009 15:06:23, 62976 bytes
Well, since I bought this machine last year, I've hadn't had a problem with BSOD until this week, with this game! Sigh. Any reconmendations besides updating the drivers (which I've already done)?
Reinstall windows?
Please remember, it might not be the game that caused it. Anything can happen to make windows crash. it's one of the downfalls of using a microsoft operating system. It could be perfectly fine one night. You log on the next morning and you get a ton of errors.
And may i suggest you get a new video card, as it's a very low end card.
Keep in mind that there is a patch that was released by Microsoft on Tuesday that has been known in certain circumstances to cause XP machines to blue screen. So far Microsoft has no idea what is causing this issue
http://blogs.technet.com/msrc/archive/2010/02/12/update-restart-issues-after-installing-ms10-015.aspx
My setup is a:-
E2180 OC'd from 2 ghz to 3.2 on stock cooling.
2GB 800mhz generic ram
2 x 512gb Hdd's
Windows 7 64bt ultimate edition
ATI 4850HD with a cheap aftermarket cooler thrown on. Fan runs at between 60-80%
So as you can see, my comp is a low-mid range comp, and i have none of the problems that the majority of players seem to have. It all depends on how you set up and configure your system to get the best out of it.
Just because a setup might work with one or two games, doesnt mean it will work with others.
i think my system cost around £200 to build 2 years ago, so it will probably be even cheaper now.
A quick search reveals this as an issue with the display driver. Remove it, download a fresh copy and reinstall. See if that works...
http://support.microsoft.com/kb/329293
A couple of other things:
* The driver version looks weird. I'm not 100% clear on Nvidia's numbering system, but my driver is 8.17.11.9621. Might be because you're on XP, 32-bit, or using an 8400GS while I'm using a 260GTX. Definitely a good idea to download a new copy, regardless.
* If you upgrade to Windows 7, you will have to use one of the workarounds, since upgrading from XP to 7 is not officially supported.
Windows is not alone in that aspect, a HDD failure will make ANY OS to fail big.
And the BSOD's aint due to Windows, the reason people tends to think that is because of a happening back in time when, excuse the language "*****slap" and it's follower "teardrop" was written. Those programs sent bad packets to windows that resulted in a BSOD, and they were abused for months, millions of people was attacked over IRC alone this way, and thus the rumors about windows began. This was with Windows 95 and early versions of Windows 98. Once it was resolved it never happen again, but rumors are hard to kill.
Amyway BSOD's come from either broken hardware or memoryleaks in drivers, or in some cases overheating. If you have a genuine copy of Windows you can find tools on the DVD or on Microsoft's webpage that helps you find the reason to BSOD's. A STOP Code can in some cases explain what happen, but most often it triggers different codes each time, it can list different files each time aswell. When you have used windebug to analyse the stop you can as a last resort use it to stresstest drivers, one by one, this is dangerous tho as it might lead to another BSOD and also dataloss when the stop occurs, but if you dont have any other program open while running the stresstest you can pinpoint the driver(s) causing the BSOD and replace them with different versions.
Actually, you'll never see a STOP code on Win 9x operating systems. It's specific to O/S based on the NT kernel (NT, 2000, XP, Vista and now 7).
Last night at home, where my computer has a nice graphics card and plenty of processing power and memory, I got a BSOD whilst playing STO, right in the middle of a ground mission. I'm hoping that it was a bit of a one-off. Does anyone know of any recent issues that might cause it? I've played for quite a few hours on that computer and it's the first time there's been a problem.
Just let it do extended tests. The standard didnt find the issue for me.
While doing a mission tonight (forgot what one) I was in a ground combat area and as soon as a plasma grenade exploded I BSOD. This has happened to me before and I tracked the issue down to "Soft Particles." I am able to run everything at max without issues but it never fails that when I enable this at some point a grenade explosion will cause my PC to blue screen. I enabled it a few days back with the newest patch and haven't had issues so I thought this issue was fixed.
Sadly this time my entire PC is nuked.
The BS popped up as usual and I didn't pay much attention to it as I've seen it before (so I've no idea what error code it was.) However when the system restarted it BSOD instantly. No mater what now whenever the computer tries to boot it blue screens. :mad:
I can boot the PC in safe mode though. I just have no idea what to do to fix it. So far all I've tried doing is uninstalling the video drivers but that didn't. I also tried using my XP cd to "repair" the drive but again, nothing. So I'm out of ideas and need some help here.
*Edit*
The Blue Screen that pop ups for a fraction of a second on restart does not have an error code. I was able to record it with my camera and here's a picture of it... CLICK
Oh also worth noting is that the BS appears regardless if I move the HD to another computer (this computer) and try to boot it. So it's not my video card that's nuked or anything but something on the drive.
System Information:
Intel Core 2 Quad Q9300 @2.5GHz
4 Gigs RAM
ATI Radeon 4870HD (Driver 10.2)
Win XP Pro. (Latest Updates)
Anyone?
I'm running games like METRO: LAST LIGHT on Max settings.
But when i run this game. I get BSOD.
AMD-FX-8350 Eight Core
8GIG RAM
Sapphire R9 280X Toxic (Best version of the R9 280x)
So you see... This has nothing to do with our hardware. This is an issue with the game itself.
Gonna try install the steam version instead and see if anything different happens.
If it still persists ill just have to stop playing.
CPU: AMD 8320 Black Edition 8 core 3.5Ghz/4.2Ghz OC
Cooler: Cooler Master Hyper 212 plus +Artic Silver 5 Goo
Mobo: Gigabyte 970A-D3P AM3/AM3+
RAM: Gskill Ripjaws X 16Gbs-2x8GBs 1866Mhz ----tryed 8gbs 4x2gbs kingston 1333mhz
GPU: MSI Radeon HD7870Ghz OC Edition
tryed xfx hd 5570
Hdd: Sandisk 128GB SSD boot drive
2x1Tb Hitachi 7200RPM Hdd
2Tb WD MyBook 7200RPM external Hdd
PSU: Rosewill Hive 650W 80+Bronze Full Modular
Case: Rosewill Challenger USB3.0v Mid-tower
OS: W7 64bit Home premium