Neverwinter Blue Screen of Death

oblique000 · May 2013

So everytime I play Neverwinter (since the recent patch) about half an hour after I start playing my computer blue screens with the error "Kernal Data Inpage Error". It only does this when im playing Neverwinter. I looked up the error I got, and I tried the fix but it continues to happen everytime I try to play. Can anybody help me?

oblique000 · May 2013

bumpppppppp

jmasterzero · May 2013

I'm having the same problem. I had two separate instances of a BSOD. I'm using an NVIDIA GeForce 8800 GTS card, all the drivers are up to date, and I don't have any other programs running that might conflict, so I'm at a loss.

oblique000 · May 2013

just downloaded the new patch and my game is still crashing

sneakypaladin · May 2013

Bumped because I have the same issue

lozadeeks · May 2013

Bump same issue, can't stay in the game for more than a few minutes now.
Wondering if it's possibly our computers?

oblique000 · May 2013

Bump pls halp

miyahgi · May 2013

I am having the same problem.

Windows 7 Home Premium
Nvidia Geforce GTX 550 TI ver. 320.18

Event Log Error:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> 
  <EventID>41</EventID> 
  <Version>2</Version> 
  <Level>1</Level> 
  <Task>63</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000002</Keywords> 
  <TimeCreated SystemTime="2013-05-27T22:24:54.741609200Z" /> 
  <EventRecordID>92191</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="4" ThreadID="8" /> 
  <Channel>System</Channel> 
  <Computer>Gaming</Computer> 
  <Security UserID="S-1-5-18" /> 
  </System>
- <EventData>
  <Data Name="BugcheckCode">0</Data> 
  <Data Name="BugcheckParameter1">0x0</Data> 
  <Data Name="BugcheckParameter2">0x0</Data> 
  <Data Name="BugcheckParameter3">0x0</Data> 
  <Data Name="BugcheckParameter4">0x0</Data> 
  <Data Name="SleepInProgress">false</Data> 
  <Data Name="PowerButtonTimestamp">0</Data> 
  </EventData>
  </Event>

dameduloc · May 2013

Bumps aren't helpful.

System specs ARE (OS/video card/driver version), output of any errors and/or dxdiag.

Before you go ALL WILLY NILLY with long posts in regards to errors/system spec...please, for all that's green and fuzzy, wrap in

CODE

tags

darminion · May 2013

Well, I've just experienced the same problem. For the past couple of days the game had already been giving me system-freezing lock-ups, but a couple of minutes ago it gave me a full-blown BSoD.

Forgot to note down what it said on account of kinda freaking out. Last thing I want is my hardware dying while I'm poor.

System Specs:

OS: Win7 Home Premium 64bit
Processor: Intel Core i5-2500 @ 3.30GHz
Graphic card: AMD Radeon HD 6800 series, most recent driver
RAM: 8GB
DirectX 11

darminion · May 2013

Ok, this is getting ridiculous. Since my previous post the game has given me not one, not two, but six complete system lock-ups followed by a Blue Screen of Death. The majority of them happen about 5-10 minutes after starting the game.

Whatever you guys did with the last patch, it severely broke the game for me.

dameduloc · May 2013

http://support.microsoft.com/kb/2028504#method3

The Stop error code and the PowerButtonTimestamp are listed as zero. For example, consider the following scenarios:
The Stop error BugcheckCode value is listed as zero. Circumstances can prevent writing the Stop error BugcheckCode information before the computer restarts or shuts down. In this case, a BugcheckCode value of zero is logged. Also, perhaps no Stop error occurred, and the shutdown resulted from a power loss. For example, on a portable computer, this could mean that the battery is removed or completely drained. Or, on a desktop computer, this could mean that the computer was unplugged, or a power outage occurred.
The PowerButtonTimestamp is listed as zero. Circumstances can prevent writing the PowerButtonTimestamp information before the computer restarts or shuts down. In this case, a value of zero is logged. This can occur if the power button is pressed and held for at least four seconds when Windows has an operation running that prevents writing the event to disk. You might also see this scenario if the computer is “hard-locked” and therefore unresponsive to any input, and the computer has to be powered off. To determine whether the computer is unresponsive, try pressing the CAPS LOCK key to toggle the CAPS light on the keyboard.
To check whether this scenario is occurring, press the CAPS LOCK key on the keyboard. When you do this, if the CAPS LOCK light on the keyboard does not change when you press the CAPS LOCK key, the computer may be completely unresponsive (hard hang).

This scenario usually indicates a problem with the hardware. To help isolate the problem, check the following items:
Overclocking: Disable overclocking to see whether the issue occurs when the system is run at the correct speed.
Check the memory: Verify the memory by using a memory checker. Verify that each memory chip is the same speed and that it is configured correctly in the system.
Power supply: Make sure that the power supply has enough wattage to appropriately handle the installed devices. If you added memory, installed a newer processor, installed additional drives, or added external devices, such devices can require more energy than the current power supply can provide consistently.
Overheating: Check whether the system is overheating by examining the internal temperature of the hardware.
Defaults: Reset the system back to the system defaults to see whether the issues occur when the system is running in its default configuration.

If you see that the computer generates a Stop error that contains a BugcheckCode value that is not reported in an event ID 41, change the restart behavior for the computer. To do this, follow these steps:
Right-click My Computer, and then click Properties.
Click Advanced system settings.
Click the Advanced tab.
In the Startup and Recovery section, click Settings.
Click to clear the Automatically restart check box.

darminion · May 2013

And even more crashes, up to a point that the game has literally become unplayable.

How the hell do you even manage to break a game this badly by just updating a couple of zones?

llunauk · November 2013

I just started playing this game today and I've had 3 blue screens and about a hours worth of play.

Neverwinter Blue Screen of Death

Comments