BSOD Error - STO Related

[Husker]

So i had to re install Windows due to some random problem slowing it right down, something to do with Skydrive. Anyway, i've just re installed and everything is running fine except when i try to patch STO.

I've installed it perfectly and i can login but while it's patching on the launcher i get a BSOD with the error "driver irql_less_or_not_equal" which is odd because i'm using all the same drivers and the same copy of Windows as i did before i had this problem.

I had thought it would be graphics driver related so i even updated to the beta drivers but still same problem. I can only get so far in the patching process before it pops up with this error.

Any ideas??? I can't play until this is resolved.

Oh and btw my setup is:

AMD 8350
Asus M5A97 R2.0
8gb Corsair Vengeance
SSD (os) + 2x 500gb Seagates in RAID-0
Sapphire Toxic R9 270X
Corsair RM1000
Pioneer BD-Rom

[Husker]

I'm now getting this error too. It happens after i type in my login details on the launcher.

"A Hog returned an error while trying to read. Restart in 9"

Disabled on demand patching but still no go.

[Prototype_No.98]

To quote Sherlock Holmes...
"Eliminate all other factors, and the one which remains must be the truth"

I assume you done the obvious; Reinstalled drivers, reinstalled STO, updated windows ect.
So Im going to throw a wide theory out there, could it be your clock speeds?
Try lowering your memory clock ratio for a start and see if that works.

[cmdraftbrn]

bsod: http://sto-forum.perfectworld.com/showt ... light=bsod


check your firewalls and antivirus

[Pip]

I found some similar threads that also pointed to antivirus software. There's a diagnostic tool that you can use to view the mini dumps created during the BSOD, which should narrow down the offending file or dll.

http://www.tomshardware.com/faq/id-1653 ... ndows.html

Best of luck. Missed you out there today.

[JarekCyphus]

Yikes. For your sake, I do hope it's one of those phantom software disagreements, because in my experience, IRQL_NOT_LESS_OR_EQUAL BSODs (depending on the fault code) are nine times out of ten one of two things. 1. (most of the time) It's failed RAM. 2. Bad HDD header creating corrupted sectors.

Watch for the BSOD to happen again. If your code is 0x0000000A, you have a RAM problem and will need to run a memtest ASAP. The sooner you identify the cause of the RAM problem (socket or stick), the sooner you can make a quick repair (assuming it's just the stick) and get the show back on the road.

[Husker]

It was antivirus. I can get in game now only to come across another problem. When loading the saved UI settings it crashes back to desktop. Not major, I can setup my UI manually.

I actually thought it was network related because of the NETIO.sys error. Net I/O is afaik a conflicting file or setting or corrupt file in network drivers which I re installed. Turns out it was a corrupt install of AVG.

Thanks for the help guys

[Dancamvet]

Yay, well done tech bods! Com'on Husker we've got Heralds/Borg/enemies to kill.

[cmdraftbrn]

when in doubt. shut everything off and turn them on again one at a time

[JarekCyphus]

It was antivirus. I can get in game now only to come across another problem. When loading the saved UI settings it crashes back to desktop. Not major, I can setup my UI manually.

I actually thought it was network related because of the NETIO.sys error. Net I/O is afaik a conflicting file or setting or corrupt file in network drivers which I re installed. Turns out it was a corrupt install of AVG.

Thanks for the help guys

Thank god. NETIO is pesky. I've never run into it myself, but a quick sleuth through google unveils a host of causes, ranging everywhere from conflicts with AVG Free and Avast to IP Switch Utility and Overwolf (Overwolf is a big one, I'm finding).

Only cause for concern would be if you reinstalled AVG again and it was still corrupted. If that occurs, install it into another harddrive and see if that resolves the issue. If so, you've got a bad sector in your HDD, which—most of the time—is relatively simple to correct, unless your hard drive is an SSD. No saving that one once it starts to go.