Jump to content

Silent Warrior

Members
  • Posts

    341
  • Joined

  • Last visited

Posts posted by Silent Warrior

  1. 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.]

  2. Oh, right. Well, it said '1 file(s) processed, 0 file(s) failed'. Nothing at all besides.

    SMART analysis report:

    Your hard disk is a SAMSUNG HD503HI with firmware 1AJ100E4.

    The average temperature for this hard disk is 30C (MIN=22C MAX=39C) and yours is 27C.

    Your hard disk's S.M.A.R.T. attributes are now being analyzed and a full report about the reliability, health and status of your hard disk is generated:

    Your hard disk is not below any attribute threshold. This is good.

    Your hard disk was never below any attribute threshold. This is good.

    Your hard disk is now being compared to real data used to define normal values for your specific hard disk model. This way, the analysis can automatically use proper operating ranges. The images give you an idea of how each attribute is within such range. Current and raw values are shown for easier reference for experienced users. There are 3001 hard disk models in the current archive.

     

     

    Attribute Current Raw Overall

     

    Raw Read Error Rate

    100

    64

    Very good

     

    Throughput Performance

    252

    0

    Very good

     

    Spin Up Time

    86

    4520

    Very good

     

    Start/Stop Count

    100

    808

    Very good

     

    Reallocated Sector Count

    252

    0

    Very good

     

    Seek Error Rate

    252

    0

    Very good

     

    Seek Time Performance

    252

    0

    Very good

     

    Power On Hours Count

    100

    3339

    Very good

     

    Spin Retry Count

    252

    0

    Very good

     

    Calibration Retry Count

    252

    0

    Very good

     

    Power Cycle Count

    100

    791

    Very good

     

    GSense Error Rate

    100

    1

    Normal

     

    Power Off Retract Count

    252

    0

    Very good

     

    Hardware ECC Recovered

    100

    0

    Very good

     

    Reallocated Event Count

    252

    0

    Very good

     

    Current Pending Sector

    252

    0

    Very good

     

    Offline Uncorrectable Sector Count

    252

    0

    Very good

     

    Ultra DMA CRC Error Rate

    200

    0

    Very good

     

    Write Error Rate

    100

    99

    Very good

     

    Load Retry Count

    252

    0

    Very good

     

    Load Cycle Count

    100

    812

    Very good

    All of the attributes of your hard disk have normal values. This is good.

     

     

     

    The overall fitness for this drive is 100%.

    The overall performance for this drive is 100%.

     

    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.

  3. 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!

  4. ... 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!

  5. 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...)

  6. 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

  7. 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?

  8. 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.)

  9. 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.)

  10. 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?

  11. SUBS17: ... Holy... It IS my X52 causing this, unless there's a frightful delay in the ignition... Oh well, at least my engines fire up now, but I have to fly with a Logitech Extreme 3D Pro. Ick.

     

    Jona: Ah, missed you completely. Well, using a different stick, I'd say my immediate problem is solved. The cause is likely that stick. DCS:WH is the only game/sim I have that have this issue, though. Would a track help diagnosing what's really going on with that stick?

  12. Moving the throttle from off to idle (start) you use: RALT+Home for left engines. RControl+Home for right engine. Use end to turn them off.

    So I've been told, and that's what is written all over - and it does nothing whatsoever in sim. So I would like to find out whether I'm just doing something wrong, there's a scripted restriction in the mission itself, or some kind of problem on my end.

    Hm, maybe I could try a different joystick - my throttle doesn't actually appear to go all the way to 0, and I remember setting the Su-25T's engines on fire by increasing throttle before the engines had started.

  13. Yeah, but I don't get any ignition (APU fires up, engine doesn't move at all), following the procedure in ED's Flight Manual to the letter... There is also no control assigned as 'Throttle to idle detent', or whatever it's called. (By this I mean that there is no slot where you can assign commands for a similarly named trigger/function.)

     

    I'm investigating that... wossname, derelor's checklist, but I have yet to find out what he means by RALT+POS1.

     

    Or are you guys perhaps flying off a different checklist altogether? The X52 I use came pretty cheap and second hand, of course, and the HOTAS mouse is just FUBAR - I SUPPOSE it could be some stick failure somewhere, but let's focus on the checklists. Don't wanna hi-jack.

  14. Oh, eff... Now we have to complete every last little item on your check lists to go through the entire set?

    :helpsmilie::helpsmilie::helpsmilie::helpsmilie:

     

    :P Anyway, #12 sounds like it'll be a blast. Currently beating myself up over #1 and 2, since my stick isn't configured to fully comply with the HOTAS functionality our Hog expects... (Can't set throttle to idle during engine start-up, never mind the 50+ commands NOT mapped to a button.)

  15. I don't quite know what kind of a reply you want, but I'll say one thing about your Super Edit: If you're worried about that, you REALLY should see the arrangements I've used in the past! :D

    Laying a HDD in a vacated 5,25" bay, standing on the bottom of the chassi because I'm too lazy to fight the RAM-modules... If your chassi is standing at all steady, I speak from experience when I say that harddrives don't move around much, even under load.

  16. RAM, maybe? You never did specify how much you have of that. When I went from 1 to 3 Gb all those years past, I did see a marked improvement. Could've been due to a patch (I think I was mostly playing The Witcher at the time, and at almost the same time as I upgraded my RAM, they released a patch that improved loading times quite a bit), but that's always one other option.

×
×
  • Create New...