Kingdoms of Amalur Freezing during Gameplay

indythedefender

Honorable
Jan 4, 2013
19
0
10,510
So a few months back I bought KoA. I'd heard a ton of good things from friends, so I snapped it up once it went on sale. Unfortunately, whenever I press a key on my keyboard the game freezes and I have to use taskmanager to exit. Apparently this problem is unique to me. The only mention I've found said the solution was to "wait for an update". Seeing as that's highly unlikely, any fixes?
 
Have you tried using a different keyboard? Possibly a PS/2, just to be sure.

Some gaming USB keyboards have sky high polling rates which end up hogging resources, and it isn't the first time I see this kind of issue. Most of the times a PS/2 keyboard (either native or through an adapter) fixed it.
 


I would do that, but I also forgot to mention I'm playing this on a laptop. Yes, with a crap integrated graphics card (Intel HD 3000). Any other ideas?
 
Erm...how can an HD 3000 even play KoA? Even minimum details should stutter heavily with that...

In any case, if it's a laptop, I don't think it's the kb. High polling rates apply to gaming peripherals, not common ones.
Let the game freeze on purpose and then close it down, then open up the Event Viewer and, under "Administrative Events", look for the latest ones by ordering them by date and time, descending.
Can you find anything there?
 


According to the error report in Event Viewer, "Reckoning.exe version 1.0.0.2 stopped interacting with Windows and was closed."

As for the first part, many many years of getting used to 20 FPS my friend. I had to go through Bioshock Infinite with 15 FPS.
 


I get it, I'm an idiot. Lol.
 
I believe the HD 3000 is the minimum system requirement to play it, if I recall correctly, and at least for the GPU part. It's just that I feel it's not playable anyway, as my definition of playable is quite different on PCs 😛 (60+ FPS at a higher detail than medium, which is usually where consoles are set).
Getting a desktop or a laptop literally means nothing nowadays, as there are equivalent power/price systems in both categories if you know where to look; it's just a matter of whether or not you want it to be portable or easily upgradeable.

About the event viewer, I forgot to mention you should have copy-pasted the contents of the detail tab in XML format, sorry about that...
Once you select KoA's error record, the bottom part of the page will give a brief description of what happened. You should see a "Details" tab slightly above that description; select that, select the XML radio button and copy the entire content of it, then paste it here.
 


Thanks, I'll do that as soon as I get home!
 


+ <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Hang" />
<EventID Qualifiers="0">1002</EventID>
<Level>2</Level>
<Task>101</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-09-19T19:06:48.000000000Z" />
<EventRecordID>195981</EventRecordID>
<Channel>Application</Channel>
<Computer>Mark-THINK</Computer>
<Security />
</System>
- <EventData>
<Data>Reckoning.exe</Data>
<Data>1.0.0.2</Data>
<Data>23bc</Data>
<Data>01cfd43ca15e6aa7</Data>
<Data>94</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\KOAReckoning\Reckoning.exe</Data>
<Data />
<Binary>55006E006B006E006F0077006E0000000000</Binary>
</EventData>
</Event>
 
Hmmm....
Looks indeed like an error related to the game itself rather than to some library. Might be an incompatibility with some hardware/software you got, as there is no information but the game's executable data. If an application hangs or crashes for an external reason, you usually see the faulty library module in that report, but there's none here.

You say that happens as soon as you press a keyboard button, yes? I still advise you to try with an external keyboard in this case, even USB works. I suppose you have at least a free USB slot on the laptop, don't you?
If you haven't tried already, also do verify the game's cache from Steam (a.k.a. repair it) for good measure.
 


I did try to verify the cache, I'll get back to you as soon as I get a keyboard.