Starcraft 2 BSOD reboot error

Dave76 · 20 Dec 2012

Your motherboard manual gives info for 1, 2 and 4 RAM cards, some motherboards don't support 3 RAM cards. You can sometimes adjust settings to get 3 cards to work but, not always. It's a controller limitation.

Dual channel, there are two channels from the RAM slots to the CPU. One RAM card can only be in single channel, two RAM cards can be in Dual channel if installed in the correct slots. Depending on the way the motherboard is designed, the imbalance of RAM in different channels can cause instability.
Motherboards that support 3 RAM cards always list the corresponding information in the manual.
Your system would run better, probably at stock settings, with 2 or 4 RAM cards.

Let us know if it is stable.

Namish · 21 Dec 2012

Dave76,

I tried stability with the new voltage settings and BSODed. I put the settings back to auto / auto and tried using only 2 sticks of ram. I BSODed. While trying to write this post my screen blacked out again and it said my video drivers recovered. Here's the Grab ALL with the newest crashes and a snip of the video driver error.

Kyle

x BlueRobot · 21 Dec 2012

The latest dump file, I could see was dated as 13/12/12, try uploading the dump files again manually:

Code:

%SystemRoot%\Windows\Minidump

Namish · 21 Dec 2012

x BlueRobot,

Outside of Grab All I really am not sure how to find he dump files in order to upload them.

Kyle

x BlueRobot · 21 Dec 2012

Go the directory I specified, you will need to substitute the %SystemRoot% for C:\Windows\:

Code:

C:\Windows\Minidump

You may change C:\ for the partition which you installed Windows; C: is the default where Windows is usually installed. You may type the above path within the search box, and it should take you straight to the folder.

Dump Files - Configure Windows to Create on BSOD

Make sure Windows is also configured to create a Minidump file upon BSOD.

Layback Bear · 21 Dec 2012

I have been watching this thread and I have one question if I may.
Has the power supply been replaced?
I will go back to watching.

Dave76 · 22 Dec 2012

We need the new crash dumps.

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* Be sure the 'Overwrite any existing file' box is checked.
* OK your way out.
* Reboot if changes have been made.

Did you disable Driver Verifier?

The last information is still blaming the graphics card or drivers. Install newer and/or older drivers.

Going by the previous crashes, let's test with two RAM cards and bump the voltages.
Keep only the two RAM cards installed in the orange slots, for testing.
Change the voltages in the BIOS again.
CPU/NB Voltage 1.250v
DRAM Voltage 1.600v
Test for stability, best to run memtest86+ again.

These types of crashes can be caused by a bad PSU, the best way to check is to connect a known good PSU.
You can run the OCCT Power Supply test for at least one hour, be sure to monitor your CPU and GPU temps.
Set the time before you start.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.

Your last System Event Log is from December 1.
To check the System Event Log settings.
1. Start Event Viewer.
2. In the console tree, expand Windows Logs and select System.
3. On the Action menu, click Properties.
4. In the General Tab, ensure 'Enable logging' is checked.
Maximum log size should be 20480
Under 'When maximum event log size is reached': select 'Overwrite events as needed (oldest events first)'
Click OK.

If you are still not getting new System Event Logs, you can 'Clear Log' on the same page.

Namish · 22 Dec 2012

All,

Wow lots of responses here. I will edit this post as I complete all of the suggested steps. For now here's some answers.

-My Write debugging information tab was set to Kernel memory dump, it's now set to Small memory dump
-I Attached the few files inside my Minidump folder
-The file MEMORY.DMP was to big to attach, let me know if you need it.
-Driver verifier is not yet disabled
-The power supply has not yet been replaced
-I have 43,515 system logs right now, the newest occurring on 12/22/12
-Running 2 sticks in orange slots with the new suggested voltages.
-Service exception BSOD with 3 min to go on OCCT power supply 1 hour test. No graphs created. Not happy. Redoing.
-I will repost the dmps and grab alls for all the new crashes after Memtest and OCCT complete successfully.

Thanks guys,
Kyle

x BlueRobot · 22 Dec 2012

Code:

BugCheck 24, {1904fb, fffff880083ab6e8, fffff880083aaf40, fffff80002c76f72}

Probably caused by : ntkrnlmp.exe ( nt!ExReinitializeResourceLite+f2 )

Code:

2: kd> .cxr fffff880083aaf40
rax=fffff880083ab958 rbx=fffffa8006671660 rcx=fffffa8006671660
rdx=fffffa8005648a00 rsi=fffffa8006671620 rdi=0100000000000000
rip=fffff80002c76f72 rsp=fffff880083ab920 rbp=0000000000000745
 r8=0000000000000002  r9=0000000000000000 r10=fffff880010c95c0
r11=fffff8a003438a90 r12=0000000000000000 r13=fffffa8004bf3180
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExReinitializeResourceLite+0xf2:
fffff800`02c76f72 8b7708          mov     esi,dword ptr [rdi+8] ds:002b:01000000`00000008=????????
2: kd> kb
  *** Stack trace for last set context - .thread/.cxr resets it
RetAddr           : Args to Child                                                           : Call Site
fffff880`012c8f8c : fffff880`083ab9f0 00000000`00000745 fffffa80`06671620 fffffa80`05905bb0 : nt!ExReinitializeResourceLite+0xf2
fffff880`012459b2 : fffff800`02e39280 fffff880`083abb01 fffff880`083ab9e1 fffff8a0`03438a90 : Ntfs!NtfsDeleteFcb+0x10c
fffff880`012cb6bc : fffffa80`05905bb0 fffffa80`04bf3180 fffff8a0`03438a90 fffff8a0`03438ed0 : Ntfs!NtfsTeardownFromLcb+0x1e2
fffff880`0124d0b2 : fffffa80`05905bb0 fffffa80`05905bb0 fffff8a0`03438a90 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xcc
fffff880`012db223 : fffffa80`05905bb0 fffff800`02e39280 fffff8a0`03438a90 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`012ca3c7 : fffffa80`05905bb0 fffff8a0`03438bc0 fffff8a0`03438a90 fffffa80`04bf3180 : Ntfs!NtfsCommonClose+0x353
fffff800`02ca5641 : 00000000`00000000 fffff800`02f8e500 fffffa80`0751c001 00000000`00000002 : Ntfs!NtfsFspClose+0x15f
fffff800`02f32e5a : 00000000`00000010 fffffa80`0751c040 00000000`00000080 fffffa80`0398f9e0 : nt!ExpWorkerThread+0x111
fffff800`02c8cd26 : fffff880`02fd5180 fffffa80`0751c040 fffffa80`07260820 fffff880`012dca70 : nt!PspSystemThreadStartup+0x5a
00000000`00000000 : fffff880`083ac000 fffff880`083a6000 fffff880`083ab9e0 00000000`00000000 : nt!KiStartSystemThread+0x16

Code:

Usual causes:  Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

Run some hard-drive diagnostics and follow these steps:

Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

Post a screenshot of Crystal Disk Info summary:

Screenshots and Files - Upload and Post in Seven Forums

Make sure you have the latest firmware for SSD, and ensure all the SATA and Power cables are connected to the drive.

Check for any file system errors and bad sectors using Option #2 of:

Disk Check

Use this command with Disk Check:

Code:

chkdsk C: /f /r

Namish · 22 Dec 2012

All,

-Here's the OCCT Power supply test results and Crystal Disk summary.
-I have no blank CDs so the Hard Drive Diagnostic Procedure test will have to wait a while.

Kyle