Windows exception c00005 origin KERNEL32.dll

[kittytessapuppy]

Showroom continuously crashes just as the game loads in, this is the only error I can find in my logs. I have no idea what it means, I have, in fact, tried searching it, but it seems any errors are simply similar in the code, but not the originating dll. I don't know what to do, Amy help is appreciated.

[GrantSP]

You've left the details a little sparse so I'll give a generalised response. That exception is an "unhandled" exception meaning Windows has no way of figuring out which executable, or a function inside it, caused the error.

However since it is in Kernel it is probably due to a driver error, perhaps Windows updated and you are yet to restart to force the changes.

Alternatively you may be trying to have some software run in the background, like Steam's overlay, and that is messing with your system. Try the trusted: switch off, let sit for 5 minutes and reboot method. After that examine what you were doing and what software was running and try to replicate the error.

[kittytessapuppy]

My apologies, since I'm mobile, I find it difficult to give error logs since I cannot simply copy and paste them. I will attempt to write out the latest error that has popped up accurately...

 

INFO (date time string): Windows Exception (c0000005). Origin: "C:/Steam/steamapps/common/Skyrim/tesv.exe" (8b437c). Last hook call: structure HINSTANCE__ *__stdcall LoadLibraryW_rep(const wchar_t *)

 

That's the last error in my logs. Does it mean anything to you guys?

[GrantSP]

My apologies, since I'm mobile, I find it difficult to give error logs since I cannot simply copy and paste them. I will attempt to write out the latest error that has popped up accurately...

 

INFO (date time string): Windows Exception (c0000005). Origin: "C:/Steam/steamapps/common/Skyrim/tesv.exe" (8b437c). Last hook call: structure HINSTANCE__ *__stdcall LoadLibraryW_rep(const wchar_t *)

 

That's the last error in my logs. Does it mean anything to you guys?

Nothing to worry about with that log entry. Note it is flagged as: INFO, not ERROR. MO's 'hooking' mechanism can't find something that it was expecting and just exited without knowing from where.

Unless you are experiencing actual CTDs or other problems, I suggest you just continue on modding/playing.

[kittytessapuppy]

Well, it does ctd, that's the only thing I could find on my logs that might possibly have been causing it. If that's not, in fact, the case, then I don't know what's causing my CTDs. I'm just so confused xd

[GrantSP]

We have a thread specifically for CTDs & related issues here. Read through that and see if you can pinpoint your issue.