Grim Dawn

Grim Dawn

View Stats:
Ploppy Sep 19, 2015 @ 6:50am
BSOD Crash: Page fault in non-paged area :/
Blue Screen of Death crash :(

Had this happen 2 times last night, each time I play about 40-60 minutes of gameplay before the game crashed then went to a blue screen with the message 'Page fault in non-paged area'.

I tried this fix and it didn't work for me:

http://www.tomshardware.co.uk/answers/id-2084584/page-fault-paged-area-bsod.html

It seems that I may have faulty RAM if it's not Grim Dawn causing the problem - according to a lot of people online it's rarely a software error that causes Blue Screen but I'm not a wizard so I don't know exactly :D

I also tried playing Mad Max afterwards and I had no problems at with at least 3 hours gameplay.

Does anyone else have any ideas what it may be? Is it Grim Dawn causing the issue?
Last edited by Ploppy; Sep 19, 2015 @ 6:53am
< >
Showing 1-10 of 10 comments
SevR Sep 19, 2015 @ 7:17am 
Download and run Mem Test86, if you are not dual booting a Linux O/S. Most Linux distributions will give you an option to run Memtest at the GrUB operating system selection list.

Memtest will put your memory sticks through the paces with 9 different tests per module and tell you if one or more is bad. http://www.memtest86.com/

Since many other Grim Dawn users are not having the same BSOD issue, it's most likely due to your mixture of hardware and software that is causing the operating system to fault. The trick is figuring out where it lies.
mikeydsc Sep 19, 2015 @ 7:22am 
Its more likely a DEP error. For info https://en.wikipedia.org/wiki/Data_Execution_Prevention.
How to turn on/off http://techblissonline.com/enable-disable-dep-in-windows-xp-vista/

You can also go the the preboot screen if your BIOS supports it to test the memory without any additional downloads.
Last edited by mikeydsc; Sep 19, 2015 @ 7:23am
Ploppy Sep 19, 2015 @ 8:01am 
Originally posted by SevR:
Download and run Mem Test86, if you are not dual booting a Linux O/S. Most Linux distributions will give you an option to run Memtest at the GrUB operating system selection list.

Memtest will put your memory sticks through the paces with 9 different tests per module and tell you if one or more is bad. http://www.memtest86.com/

Since many other Grim Dawn users are not having the same BSOD issue, it's most likely due to your mixture of hardware and software that is causing the operating system to fault. The trick is figuring out where it lies.

Yes, I thought that since few users have posted the issue it's most likely my hardware.

Thanks for the link ;)
Ploppy Sep 19, 2015 @ 8:01am 
Originally posted by mikeydsc:
Its more likely a DEP error. For info https://en.wikipedia.org/wiki/Data_Execution_Prevention.
How to turn on/off http://techblissonline.com/enable-disable-dep-in-windows-xp-vista/

You can also go the the preboot screen if your BIOS supports it to test the memory without any additional downloads.

I will check this out, thanks ;)
Ploppy Sep 21, 2015 @ 7:35am 
Update on the crash - so far it hasn't happened with other games.

I have currently played soldier for 146 minutes, starting in Devils Crossing and working my way to Dead mans Gulch, no crashes but I did have the sound bug/missing combat effects which happens around Twin Falls area.

Note that my 2 BSOD crashes were both in the Warden's Lab/Transit area.

I hope the devs can figure this one out but I have no real idea how to reproduce it apart from replaying soldier in the transit area.

Maybe the amount of mobs you can hit with soldier is casuing a spam issues with the RAM, hmm.
Rhis  [developer] Sep 21, 2015 @ 1:52pm 
BSODs are almost exclusively caused by driver issues and hardware failures. Even if this only seems to happen when playing Grim Dawn, it's still almost impossible that the game is the cause. If it was, we'd be seeing it happen to more people than just one.

For a BSOD to happen, something has to go badly wrong on the system, on a level that games generally don't even have access to.

If you haven't already tested your RAM based on the advice above, I'd recommend doing so.
Last edited by Rhis; Sep 21, 2015 @ 1:52pm
Ploppy Sep 21, 2015 @ 2:33pm 
Originally posted by Rhis:
BSODs are almost exclusively caused by driver issues and hardware failures. Even if this only seems to happen when playing Grim Dawn, it's still almost impossible that the game is the cause. If it was, we'd be seeing it happen to more people than just one.

For a BSOD to happen, something has to go badly wrong on the system, on a level that games generally don't even have access to.

If you haven't already tested your RAM based on the advice above, I'd recommend doing so.

Just the confirmation I was looking for, thank you :)

It was probably a lot of things going on that was giving the RAM a stress test and caused the error.

I've been playing a LOT of Grim Dawn today and hadn't a single crash at all so fingers crossed it stays that way for me :D
Dialtone Sep 21, 2015 @ 2:48pm 
I had a few BSOD's a couple months ago, can't remember which game I was playing when it first happened. The problem got worse though and would even happen while at desktop. Before I narrowed it down to memory and removed the problem chip the BSOD's corrupted some operating system files. So after getting the system is stable again I had to reformat and leave out half my RAM. But all's good for now. :)

Edit: I Forgot to mention my point, "Page fault in non-paged area" was the type of BSOD crash I had too. Memory's often the cause.
Last edited by Dialtone; Sep 21, 2015 @ 2:51pm
Ploppy Sep 21, 2015 @ 3:04pm 
Originally posted by Dialtone:
I had a few BSOD's a couple months ago, can't remember which game I was playing when it first happened. The problem got worse though and would even happen while at desktop. Before I narrowed it down to memory and removed the problem chip the BSOD's corrupted some operating system files. So after getting the system is stable again I had to reformat and leave out half my RAM. But all's good for now. :)

Edit: I Forgot to mention my point, "Page fault in non-paged area" was the type of BSOD crash I had too. Memory's often the cause.

I've not had this error before with RAM but I had the old 'win 7 desktop freeze' issue with RAM on my old build, I had to go down form 8GB to 6GB :/

I have a friend who bought 16GB of RAM for a rendering PC and he ended having to remove most of it unitl he had 6GB.

I suppose the moral of the story is 'get ready to buy more RAM' :D
mikeydsc Sep 21, 2015 @ 3:54pm 
Ram you get what you pay for. Pay the extra few bucks for the good stuff and you wont have problems from the chinese made stuff.

Also run chkdsk to see if you have bad blocks of memory on your HDD. Can cause corruption of files and more. For instance the page file is using a bad sector.
< >
Showing 1-10 of 10 comments
Per page: 1530 50

Date Posted: Sep 19, 2015 @ 6:50am
Posts: 10