BSOD 1033 while playing any game

Kainex99 · Feb 20, 2014

Hello, after installing two SSD in raid 0, I've been getting BSOD 1033 while playing games, mostly it's MEMORY_MANAGEMENT, but sometimes it's SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Attached are dump files. BSOD does not seem to happen when system is idle.

My mostly Dell XPS 8000 rig (5 years old or so):

Windows 7 home premium x64, SP1 (original OS, full retail)-cloned from HDD to SSD's in raid 0
CPU: i7 860-no overclock
Motherboard: X231R
Memory: PNY DDR3-1033
Graphics card: Nvidia GTS 240
Sound Card: On board Realtek
Monitors: 20" Samsung Syncmaster 2232 BW
hard drives: 2 x Samsung 840 EVO SSD, 250gb each, in raid 0
PSU: 500W Dynex
Cooling: stock dell fans
Keyboard Logitec wireless solar
Mouse: Logitech M310 wireless
Internet speed: satellite

Drivers all updated, manually and through windows update
Heat does not seem to be issue, Speccy has CPU/GPU temps within range
Chkdisk ran, no problems
Memtest ran for 10+ hours, no errors
Driver verifier causes immediate crash on boot, does not tell which driver caused error
bluescreenviewer points to ntoskrnl.exe almost every time.

Any help would be appreciated, thank you.

Arc · Feb 24, 2014

Hi Kainex99.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Let us know the results.
_______________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002fc7127, fffff88002868378, fffff88002867bd0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+35fd2 )

Followup: MachineOwner
---------

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002fc7127, The address that the exception occurred at
Arg3: fffff88002868378, Exception Record Address
Arg4: fffff88002867bd0, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExAllocatePoolWithTag+517
fffff800`02fc7127 4c8b4908        mov     r9,qword ptr [rcx+8]

EXCEPTION_RECORD:  fffff88002868378 -- (.exr 0xfffff88002868378)
ExceptionAddress: fffff80002fc7127 (nt!ExAllocatePoolWithTag+0x0000000000000517)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88002867bd0 -- (.cxr 0xfffff88002867bd0;r)
rax=fffffa801159c060 rbx=fffffa800cd09180 rcx=ff7ffa800cd09180
rdx=0000000000000001 rsi=00000000000000e2 rdi=0000000000000001
rip=fffff80002fc7127 rsp=fffff880028685b0 rbp=0000000000001000
 r8=0000000000000001  r9=fffff80002e1d000 r10=fffffa800cd08148
r11=0000000000000001 r12=fffffa800cd08140 r13=0000000000000000
r14=fffffa801159c060 r15=00000000484c764e
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!ExAllocatePoolWithTag+0x517:
fffff800`02fc7127 4c8b4908        mov     r9,qword ptr [rcx+8] ds:002b:ff7ffa80`0cd09188=????????????????
Last set context:
rax=fffffa801159c060 rbx=fffffa800cd09180 rcx=ff7ffa800cd09180
rdx=0000000000000001 rsi=00000000000000e2 rdi=0000000000000001
rip=fffff80002fc7127 rsp=fffff880028685b0 rbp=0000000000001000
 r8=0000000000000001  r9=fffff80002e1d000 r10=fffffa800cd08148
r11=0000000000000001 r12=fffffa800cd08140 r13=0000000000000000
r14=fffffa801159c060 r15=00000000484c764e
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!ExAllocatePoolWithTag+0x517:
fffff800`02fc7127 4c8b4908        mov     r9,qword ptr [rcx+8] ds:002b:ff7ffa80`0cd09188=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ca100
GetUlongFromAddress: unable to read from fffff800030ca1c0
 ffffffffffffffff 

FOLLOWUP_IP: 
nvlddmkm+35fd2
fffff880`05836fd2 ??              ???

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff88005836fd2 to fffff80002fc7127

STACK_TEXT:  
fffff880`028685b0 fffff880`05836fd2 : fffff880`00000001 fffff880`02868748 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0x517
fffff880`028686a0 fffff880`00000001 : fffff880`02868748 00000000`00000000 00000000`00000000 00000000`80000000 : nvlddmkm+0x35fd2
fffff880`028686a8 fffff880`02868748 : 00000000`00000000 00000000`00000000 00000000`80000000 00000000`0000e9eb : 0xfffff880`00000001
fffff880`028686b0 00000000`00000000 : 00000000`00000000 00000000`80000000 00000000`0000e9eb fffffa80`0f267000 : 0xfffff880`02868748


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nvlddmkm+35fd2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52f651cf

STACK_COMMAND:  .cxr 0xfffff88002867bd0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+35fd2

BUCKET_ID:  X64_0x7E_nvlddmkm+35fd2

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_nvlddmkm+35fd2

FAILURE_ID_HASH:  {83ec38e2-b565-09e7-a8db-f36687bc1543}

Followup: MachineOwner
---------

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05801000 fffff880`063fa000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Feb 08 21:18:31 2014 (52F651CF)
    CheckSum:         00BC7EE8
    ImageSize:        00BF9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

BSOD 1033 while playing any game

Kainex99

New member

My Computer

Arc

New member

My Computer