WayneLigon
Adventurer
WoW name: Icemane, Guild: Enduring Nobility on Feathermoon
OK, I know some EN people were going to try Deadmines, perhaps, this weekend. Like to join you, but I can't. I'm not starting this damn game until I see if I ever get a response back from tech support. WoW seems to be causing a system-wide instability in my machine. I got like four Error 132's yesterday afternoon while trying to play and after that my machine started acting weird again, as it described in a couple other threads I posted in this area. Blue screens and spontaneous rebooting, mainly, memory allocation errors, etc.
No virus, no adware. I've run memcheck86+ and Microsoft's memory checker on it to no avail. I've updated video and audio drivers, I've followed the instructions Blizzard has up on their site to no avail. All that the support board has on Error 132 is 'we know about it and we're working on it' That was in November, presumably during the beta, and no further Blizzard staff response has been forthcoming, even though that's the number one responded-to item on the board.
I posted my latest error log, which quickly went to like page 10+; maybe I'm a stupid person but even accounting for MMPORG players being pretty whiny if I was a Blizzard executive and saw that kind of activity on a support board for my game, I'd crap a gold brick.
I'm normally a patient person when it comes to computers. I work with the things every day. I've never seen something affect a machine like this. I'm not a person to go 'OMFG Is Brokken!!!111', but damn it, it is. Something specific to this particular game took my brand new PC built for gaming and turned it into a paperweight for a week until I could pay someone to fix it, and now it's probably going to do it again.
I mailed off the error logs and a copy of the system info that DxDiag gave me to the support staff. No response yet. If y'all don't see me soon - or, perhaps, ever again, this is why.
OK, I know some EN people were going to try Deadmines, perhaps, this weekend. Like to join you, but I can't. I'm not starting this damn game until I see if I ever get a response back from tech support. WoW seems to be causing a system-wide instability in my machine. I got like four Error 132's yesterday afternoon while trying to play and after that my machine started acting weird again, as it described in a couple other threads I posted in this area. Blue screens and spontaneous rebooting, mainly, memory allocation errors, etc.
No virus, no adware. I've run memcheck86+ and Microsoft's memory checker on it to no avail. I've updated video and audio drivers, I've followed the instructions Blizzard has up on their site to no avail. All that the support board has on Error 132 is 'we know about it and we're working on it' That was in November, presumably during the beta, and no further Blizzard staff response has been forthcoming, even though that's the number one responded-to item on the board.
I posted my latest error log, which quickly went to like page 10+; maybe I'm a stupid person but even accounting for MMPORG players being pretty whiny if I was a Blizzard executive and saw that kind of activity on a support board for my game, I'd crap a gold brick.
I'm normally a patient person when it comes to computers. I work with the things every day. I've never seen something affect a machine like this. I'm not a person to go 'OMFG Is Brokken!!!111', but damn it, it is. Something specific to this particular game took my brand new PC built for gaming and turned it into a paperweight for a week until I could pay someone to fix it, and now it's probably going to do it again.
I mailed off the error logs and a copy of the system info that DxDiag gave me to the support staff. No response yet. If y'all don't see me soon - or, perhaps, ever again, this is why.
