Maximus V Extreme x TurboVHelp.exe

[JorgeANeto]

Hi everyone,

Sorry for the illiteracy. 🙂

I’ve just upgraded my system by including some RAM and replacing my defective Sabertooth mobo by a fresh Maximus V Extreme. The motherboard is excellent and is allowing me higher CPU’s clock very easily in comparison to the previous one.
However, since the upgrade I’m experiencing the following issue: everything runs ok and smoothly until I try to install this peripheral:


Saitek x52 Pro Flight System (rear panel USB)


After to install its driver, the computer freezes after a while and never reboot: the reboot process halts with a popup saying: “Access violation at address 0042D7DE in module 'TurboVHelp.exe'. Read of address 0000000”

The only way out is to proceed a system restore one step before to install that driver, and the systems returns to work correctly and boots normally. The scenery was repeated three times. With the driver installed – system crashes and never returns. Without it, system works fine. So, it’s reproducible.

Since that Saitek forum is a joke (as well as their support) I thought to post here. I’ve been searching for TurboVhelp.exe error in several forums (ASUS included) and the solutions presented seem harmless (e.g. “try to remove and reinstall Asus Suite” – of course it has been done). I'm surprised Asus has not provided a workaround for a usual problem like that so far.

Regards.

By the way, the setup is:

• Mobo – Asus Maximus V Extreme
  
• 16 Gb RAM Ripjaws 2133 Mhz.
  
• Intel i7 2700K @ 4.6 Ghz
  
• MSI 580GTX Lighting x 2 (SLI)
  
• Sound off board Sound Blaster X-Fi Titanium.
  
• ATX Corsair 1200W
  
• Other peripherals as racing wheels, joysticks and so on seem to work correctly.
  

[TenBlade]

Hola, Jorge.
Have you added additional RAM? Meaning, all your sticks did not come in the same box?!
Are you hoping for a stable overclock with that Turbo-program?!

Both points above are no-nos.
RAM sticks that are identical but not factory tested for compatibility will give you all sorts of trouble.
And I´d say struggle no more with AiSuite, you got a killer overclocking board, it should be overclocked in BIOS. Lots of help here for that. I think the world has yet to see a completely bug-free desktop overclock.

Edit: Since you´re installing a flight stick I presume you´re a simmer. Let me invite you to join Fly ROG AirWays, in the top bar go: Community/Groups, read the discription and just sign up. Read the discussions, add your comments, etc.

[feniks]

sounds like memory fault to me.

running 4 sticks calls for some tweaking in BIOS, usually it will never works in XMP mode this way. try manual config to same speed/frequency and voltage but loosen timings or the other way around lower speed and use it with same timings and voltage.

test the memory stability with MemTest86+ 4.20, there is a bootable USB installer too:
http://www.memtest.org/download/4.20/memtest86+-4.20.exe.zip

at least 1 pass for short use, but for daily use you should run it over night (~12 passes on 8GB, 6-8 passes on 16GB) and make sure there is no errors.

[SUKARA]

What kind of the AI-suite version are you using? (version V2.01.01)?

If not,maybe you can try to upgrade the tool for test again

http://support.asus.com/Download.aspx?SLanguage=zh-tw&p=1&s=39&m=MAXIMUS%20V%20EXTREME&os=30&ft=14&f...

[JorgeANeto]

Thank you guys for the responses.

Actually I've replaced all the old RAMs sticks (3 x 2 Gb) for (4 x 4 Gb), but I didn't test them. I'm doing this right away using MemTest as suggested. I’m using last Asus Suite 2.01.01 version indeed.

I'll post the results afterwards, didn’t know 4 RAM sticks might cause problems and require some tweaking. Let’s wait for the tests results.

Regards,

[feniks]

incompatible RAM will cause it, the timings of Tri Channel RAM were not designed to necessarily fit to what a Dual Channel controller likes ... I'd suggest getting a compatible memory designed for Dual Channel.

[JorgeANeto]

That's what I was thinking, but cannot find a RAM issue at all.

Closure: the 16 Gb RAM sticks were exhaustively tested and no errors at the end. The TurboVHelp.exe persistis but, mysteriously, it's no longer halting the system, actually it became only a popup error message without further implications.

The workaround was to boot in safe mode and rename TurboVhelp.exe as TurboVHelp.**** or whatever... the popup error has stopped and, as far as I tested, no other side effects have been detected.

Any other info related to this issue I'll post if it'd be the case.

Regards.