Jump to content

Silent Warrior

Members
  • Posts

    341
  • Joined

  • Last visited

About Silent Warrior

  • Birthday 11/08/1983

Personal Information

  • Flight Simulators
    X-Plane 9.62
    MS Flight Simulator X + Acceleration
  • Location
    Gothenburg, Sweden
  • Occupation
    Student
  1. Did... this actually... make sense to anyone...? Anyway, checking out some of the posted download links for the fun of it.
  2. beers: I've been using Avast since the millennium was young, if not before, and never had a problem of any kind with it. Well, besides the annoyance of their VIRUS DATABASE UPDATED message - way too loud back then. It has played nice with everything so far, and kept out of the way. Spybot Search & Destroy is another can o' worms, though... (It's already uninstalled - interfered with something, but I don't remember what.) I'm running HDTune now (free trial), and everything is again said to be OK. Running an error scan, and the speed typically lies between 90 and 100 MB/s. 102.8 seems to be the top speed. [update: The speed does decay - halfway through it's hovering around 80 MB/s. That doesn't worry me, though.]
  3. Oh, right. Well, it said '1 file(s) processed, 0 file(s) failed'. Nothing at all besides. SMART analysis report: It's funny, though - all of a sudden FSX has decided to work normally again... (That is, no BSOD, only random and far-apart near-freezes. Yay.) W3rd, but it would imply something was up with my graphics drivers in this case. I'll have to see what happens when Mass Effect 3 hits this baby.
  4. SMART... I know how to check that in Linux, but in Windows...? Anyway - if that's really the problem, Samsung needs a good beating. This disk isn't even one year old. (Well... at least I THINK it isn't... Time does fly, and all that.)
  5. Pyroflash: ... And all of a sudden we have progress. The crash dumps don't point to the same cause, though - one pointed to the HDMI-connection driver (not used - WTF?), another dxgmms1.sys, yet another at corrupted memory, one more... that looks like the bluescreen, and I can't make a shred of sense from it. Pool Corruption looks sort of significant. There are still others, a few memory corruptions... Nothing is consistent. I guess it could be heat, then, but I'll try making a clean reinstall of my graphics drivers first. If I can figure out how - they don't appear in the Uninstall a program list anymore... RIPTIDE: Antivirus: Avast Free, latest available. I think. The last major update was a while ago, now. I'm also using Win7 Home, so BitLocker shouldn't even be an option. I have to confess, though, that I haven't actively investigated. [update] Oh, get the **** outta here! I was just restarting, and THEN it threw a BSOD! Now I'm getting frustrated for real!
  6. ... What... the... HELL?? Uh, as it's a warning, and time stamps imply this isn't the blue screen, but I see a warning about some VSS being denied access to the root volume - "Denying administrators from accessing voume roots can cause many unexpected failures, blablabla". What... is my computer doing to itself? :huh: Effin start and play games, don't go chasing shadows! ... AAAAAAAAAH! What is all this stuff?? Dude, I'm gonna need until May to find out what I'm supposed to be looking for... 55000+ events for Applications alone!
  7. Reinstalled? :) It's my first Win7 install - I don't remember exactly when I installed it, though. I didn't get it in the initial craze. (I notice that the WinXP-computer I keep right next to it (didn't want to throw out the old gear after the upgrade) runs just fine, with less fresh components...)
  8. Hey, I'm getting blue screens, and I'm getting nervous... Just recently, FSX started throwing blue screens right and left. Odd, thought I, but not long before I also started getting strange near-freezes (sim halts for x minutes, then continues like nothing ever happened) that were mostly taken care of by reducing scenery to the lowest setting (autogen etc., not the mesh). Now, instead of these near-freezes, I get a blue screen whenever I enter the 3D world. The BSOD mentions IRQL_something_something_something. Until recently, I would say that this does not happen with X-Plane 9 (which incidentally sits on another HDD - and a much older one), but just the other day I had a blue screen there as well. When I run Scandisk/chkdisk/whatever they're calling it now, I see a whole ton of stuff that's on 'orphaned nodes' or something. What I have done is run a RAM test - Memtest86+ 4.20, I think, courtesy of Linux. I have not observed this in Linux, which is installed on the same HDD as FSX (Linux, to be fair, has nothing that puts the system to the strain comparable to FSX, though), and I haven't played much else in Windows at the moment - going through some videogames. (I'd be interested to see what happens in NWN2, but with that game I have issues like you wouldn't believe... NORMALLY. What the snap? It wasn't like this back in 2006...) Tips/suggestions? Can someone help me troubleshoot? [update]Uh... Well, Linux doesn't have BSODs, but you get my point... OR ELSE! :P
  9. http://www.gp.se/nyheter/sverige/1.844901-jas-plan-far-inte-lyfta-i-hogtrycket :megalol: You might wanna get a translation of that, but the jist of it is that Sweden's finest piece of aerial engineering, located at one certain base, is temporarily grounded because the air pressure is so high at the moment. The responsible officer was erring on the side of caution, as the computers gave a couple of error messages - bad policy to launch fighters that complain about pressure, apparently. Somehow hilarious, innit?
  10. Both A10 and FSX stress the CPU the most. Well, depending on the settings, etc etc, but you'll notice a bigger bump by upgrading the CPU. I don't know much about Intel's CPUs of that generation, but it does sound like a pretty good one... *Shrug* As for graphics in A10, any card handling DirectX 9 should be enough - which would mean anything you can find in even generic stores, not specialized on computer components. FSX does have a DirectX 10 preview (which appears to crash with several add-on aircraft, incidentally), but I don't really know if the mesh taxes the GPU much... Beefy VRAM would likely be preferable (min. 512+ Mb). CPU: Consider Core i5 / Phenom II GPU: GeForce 4xx and up / Radeon HD 5770 and up (I have a problem where the text in the ATC window doesn't render quite correct with a 6850, though my experience is otherwise the stuff of legends. If only it wouldn't hang for x minutes every so often with autogen scenery enabled, that is.)
  11. Hm... I may have mixed something up here, but wasn't StarForce removed from FC2 with the latest patch? Or was that straight LO? So, did you install just now, or have you applied all patches?
  12. Of course, of course. I'll just have to debate with myself about whether I should yet a little while. I hope you'll forgive me for asking, though: Have you had any problem at all, using this stick? The Warthog flying/starting fine? Are the controls in good order, according to the Test tab? (My present X52 wasn't that good, see - moody HOTAS-mouse that hooked into Windows' mouse, with an offset that meant my cursor would be constantly pulled to the left unless I activated a profile where the mouse-thingy had no assigned function.)
  13. That didn't seem to work - though I didn't, in fact, UNmap the RCtl/RAlt-combos... *Weeping for my impending DCS + Logitech Extreme 3D Pro experience*
  14. Jona: I have a .trk for you, but I can't seem to upload it here. (Too big? 4,5 Mb...) I used only RWin + Home, and engines wouldn't fire, with the X52 attached. When I use my other stick, this problem doesn't manifest, though I haven't prepared a .trk for it yet. This can be reproduced. I guess I'll see what, if anything, Saitek can tell me. Sabre: When I tried #12 (v. 1.1.10), I think some scripts misfired. I'm not the best pilot here, of course, but when I was instructed to form up with the instructor, he was several miles away (... it's possible that this should be phrased dead opposite), and a number of minutes later of following him around I'm told I didn't arrive at the steerpoint in time. (... WTF? Right out of the blue.) So, then I said 'Oh, screw it', or something to that effect, and proceeded to the next indicated steerpoint on the TAD at full throttle, reducing altitude to between 500 and 1500, and heard bugger all from the instructor after leaving his side. *Shrug* Guess you never anticipated the extent of my ineptitude, eh?
  15. A little tentative prod, encouraging patience a while longer. :) My X52 is doing some w3rd things, so I might be in the market for a replacement. Are you willing to send it to Sweden?
×
×
  • Create New...