Solved BSOD playing Wildstar Random

CSGR · Mar 26, 2015

Hello,

I have been intermittently experiencing BSOD while playing different games but primarily Wildstar. The problem seemed to go away for over 2 months but has recently returned.

Thank you in advance for any advice / help.

Colin

View attachment 59667

Gator · Mar 26, 2015

Hello CSGR,

Here is your last dump, it references DirectX and your Graphics driver

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 119, {700, 1b6c08, 100000001b6c06, 0}

*** WARNING: Unable to verify timestamp for [COLOR=#ff0000]nvlddmkm.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcCompletedPacket+93ee )

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

Processing initial command '!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck'
6: kd> !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=#ff0000]VIDEO_SCHEDULER_INTERNAL_ERROR (119)[/COLOR]
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000700, The subtype of the bugcheck:
Arg2: 00000000001b6c08
Arg3: 00100000001b6c06
Arg4: 0000000000000000

I see you have the latest drivers for your video card, try reverting back 1 or 2 updates and test to see if its more stable.
Drivers | GeForce

Other BSOD's point to multiple causes with no real direction so its best to do some troubleshooting

First, remove Avast
https://www.avast.com/uninstall-utility

Enable Windows Defender
http://www.eightforums.com/tutorials/21962-windows-defender-turn-off-windows-8-a.html

Download and Run Memtest86+ (Run for 8 passes or until you receive any errors. If you receive errors either your Memory or Memory controller is bad)
RAM - Test with Memtest86+ - Windows 7 Help Forums

Ensure you are not having troubles with DirectX
Run DirectX Diagnostic Tool

I see you have Furmark installed, run a stress test with it

Report back with the results.

CSGR · Mar 27, 2015

Thanks for the reply and the advice,

I reverted the GeForce driver to the last release (347.88)
Removed Avast and enabled windows defender
Ran Memtest86+ and it failed on the first pass. I reduced the dram frequency after reading about some issues with 12gb of ram and re ran Memtest86+ for 8 passes with no errors
Completed the DirectX diag tool with no errors found
Stress test with Furmark pass with no issues

I thought everything was ok and the problem was with the memory but tonight I was watching a video in my web browser on screen 2 while sitting at the log in screen for a game on screen 1. I had another BSOD with the error message "whea_uncorrectable_error"

I have attached another zip from this crash. Could you please have a look at the new files.
View attachment 59727

Thanks,
Colin

Gator · Mar 27, 2015

This time you have the following BSOD, which isn't helpful in an of itself. This Bugcheck can mean a few different things.

Code:

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

Use !analyze -v to get detailed debugging information.

[COLOR=#ff0000]BugCheck 124[/COLOR], {0, ffffe0002ced1028, f2000000, 14}

Probably caused by : GenuineIntel

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

Processing initial command '!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck'
8: kd> !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=#ff0000]
WHEA_UNCORRECTABLE_ERROR (124)[/COLOR]
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe0002ced1028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000014, Low order 32-bits of the MCi_STATUS value.

But upon further digging... You are most likely crashing due to a TLB error, most likely due to your processor or ram

Code:

===============================================================================
Common Platform Error Record @ ffffe0002ced1028
-------------------------------------------------------------------------------
Record Id     : 01d0688c328f9267
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/27/2015 13:35:34 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe0002ced10a8
Section       @ ffffe0002ced1180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR=#ff0000]Error Type    : TLB error[/COLOR]
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000206c2
Processor ID  : 0x0000000000000012

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffe0002ced10f0
Section       @ ffffe0002ced1240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000012
CPU Id        : c2 06 02 00 00 08 20 12 - ff e3 9e 02 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffffe0002ced1240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffe0002ced1138
Section       @ ffffe0002ced12c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
[COLOR=#ff0000]Severity      : Fatal

Error         : DTLBL0_ERR (Proc 8 Bank 4)[/COLOR]
  Status      : 0xf200000000000014

Run a stress test on your CPU
Video Card - Stress Test with Furmark - Windows 7 Help Forums

Also, you mentioned there are errors in your memory, this is usually very telling.

Move onto Step 3 in the link below to figure out which Ram module may be bad
RAM - Test with Memtest86+ - Windows 7 Help Forums

CSGR · Mar 29, 2015

This issue appears to be solved! Thank you for your help.
After some further research regarding my motherboard and specific ram setup I made some adjustments to ram timing and QPI voltage in Bios and have extensively tested with memtest86+ 4.2 and stress tested both video and cpu I am happy to report no more BSOD.

Once again thank you very much!

Colin

Gator · Mar 29, 2015

Good to know you got it fixed!

Let us know if anything else happens.

Solved BSOD playing Wildstar Random

CSGR

New Member

My Computer

System One

Gator

Power User

My Computer

System One

CSGR

New Member

My Computer

System One

Gator

Power User

My Computer

System One

CSGR

New Member

My Computer

System One

Gator

Power User

My Computer

System One