Have you tried uninstalling WoW and then installing a fresh copy?
Event ID 245, Source: Win32k (Win32k)
Application Wow.exe locked the primary surface 2 time(s).
What exactly is this error an indicator of? I've been getting this, and when it happens, the screen freezes for about 1-2 seconds. It is completely irregular, and sometimes I can go 30-40 mins without it happening, just to have it happen twice in 5 mins.
- System
- Provider
[ Name] Win32k
- EventID 245
[ Qualifiers] 16384
Level 4
Task 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2010-07-14T18:25:08.281125200Z
EventRecordID 41040
Channel System
Computer Owner-PC
Security
- EventData
Wow.exe
2
000000000300280000000000F5000040000000000000000000000000000000000000000000000000
--------------------------------------------------------------------------------
Binary data:
In Words
0000: 00000000 00280003 00000000 400000F5
0008: 00000000 00000000 00000000 00000000
0010: 00000000 00000000
In Bytes
0000: 00 00 00 00 03 00 28 00 ......(.
0008: 00 00 00 00 F5 00 00 40 ....õ[email protected]
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
What exactly is this error an indicator of? I've been getting this, and when it happens, the screen freezes for about 1-2 seconds. It is completely irregular, and sometimes I can go 30-40 mins without it happening, just to have it happen twice in 5 mins.
- Status
- Not open for further replies.
1 - 11 of 11 Posts
No, I haven't, because I don't have the discs on hand and it's going to take me 7 hours to download it.Have you tried uninstalling WoW and then installing a fresh copy?
I burned it onto DVD's from my old PC, did something get corrupted in the process? Is that what the error is indicating?
Though, I have run the WoW repair which didn't find anything, though I suppose it wouldn't.
Tell me, would alt+f4ing the game prevent it from reporting to EventViewer properly? Because I played for two hours and only got the freeze twice, and after alt+f4ing from the game, there were no win32k errors in eventviewer.
This is all after having run the game in selective startup mode, os I'm really confused.
This is all after having run the game in selective startup mode, os I'm really confused.
It's possible that something got corrupted - but I really don't know what's happening here. I'm just using the usual troubleshooting steps.
Download a fresh copy (despite the time required) and see if that helps.
Download a fresh copy (despite the time required) and see if that helps.
BTW - if you burn it to a CD/DVD to transfer to another system - burn it at a very slow speed.
Well, I found out that the error happens when I close it. Even when I don't experience any freezes, closing the game itself will cause the win32k error.
And I also get the freezes in Age of Conan, but nothing else.
I'm thinking it's HDD related, as I use a caviar green.
Selective Startup seemed to have significantly reduced how often the issue occured, so again it's possible that something was using up HDD activity.
And I also get the freezes in Age of Conan, but nothing else.
I'm thinking it's HDD related, as I use a caviar green.
Selective Startup seemed to have significantly reduced how often the issue occured, so again it's possible that something was using up HDD activity.
Please provide this info for us: http://www.techsupportforum.com/f217/blue-screen-of-death-bsod-posting-instructions-452654.html
I'm not experiencing any BSODs, so I don't know how that information would be relevant. My problem is 0.5-1.0 second freezes in specific games.Please provide this info for us: http://www.techsupportforum.com/f217/blue-screen-of-death-bsod-posting-instructions-452654.html
Although the title of the post relates to BSOD's, if you'd have a look at the reports that are generated you'll find that only two of the reports (out of 29 or more reports) will relate to BSOD's. The rest relate to the system state.
It would appear that my issue was related to my catalyst settings.Although the title of the post relates to BSOD's, if you'd have a look at the reports that are generated you'll find that only two of the reports (out of 29 or more reports) will relate to BSOD's. The rest relate to the system state.
For some reason, the game was dropping to 2d clocks, which were incredibly low in my version of the catalyst drivers (157mhz core/300mhz memory). I bumped it up to 400mhz core / 1200mhz memory for 2d clocks, and I was able to play for roughly 2 1/2hr without an issue.
1 - 11 of 11 Posts
- Status
- Not open for further replies.
Tech Support Forum
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!
Full Forum Listing
Top Contributors this Month
View All
spunk.funk
139 Replies
SpywareDr
56 Replies
wolfen1086
43 Replies
Recommended Communities
