401 - BSOD + possible fix
Hello, last night QuestHelper caused BSOD on my Windows Vista while playing WoW. This happened just exactly when i clicked on flightmaster in Orgrimmar, Questhelper collected info about all discovered flighpaths(QH wasn't installed before). Just before BSOD, something slightly lagged and my PC restarted. Also every time I find new fligh master, qh causes a slight lag for a second which is kinda annoying.
Possible workaround for this - please add /qh disable flight(or something like this), a command which would totally disable everything related to flight paths tracking by questhelper. Even when you disable in menu flight timer, questhelper still tracks something about flightpaths(it says new flightpath discovered for example). I already use /qh solo for similar reasons(lag for few sec when joining groups). Would be great if you would give command to disable flight path tracking :)
| User | When | Change |
|---|---|---|
| divinewind420 | Aug 19, 2009 at 02:38 UTC | Changed status from New to Fixed |
| PKZeppelin | Jun 17, 2009 at 01:29 UTC | Create |
- 2 comments
- 2 comments
Facts
- Last updated
- Aug 19, 2009
- Reported
- Jun 17, 2009
- Status
- Fixed - Developer made requested changes. QA should verify.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
- Votes
- 0
- Reply
- #2
divinewind420 Aug 19, 2009 at 02:38 UTC - 0 likesAssuming some patch has fixed it since then.
- Reply
- #1
divinewalker Jun 23, 2009 at 20:25 UTC - 0 likesTry version 1.0.23, the CPU usage was adjusted so may work better for you now.
BSOD is likely not QH related unless you are using the streaming Trial account version then QH is not currently compatible and any use of it is on your own for now.