BSOD Happens Randomly

[Scythan]

Hello. I haven't been playing any high-end games or anything, but getting BSODs that seem to be connected with DirectX or video card issues. My first post here, so let me know if you need any additional info. I filled in my specs on my profile.

Thanks

K

 

[zigzag3143]

Hello. I haven't been playing any high-end games or anything, but getting BSODs that seem to be connected with DirectX or video card issues. My first post here, so let me know if you need any additional info. I filled in my specs on my profile.

Thanks

K

Welcome

This one was caused by memory_corruption, possible because of your sptd.sys driver. SPTD.sys is used by alcohol and daemon tools and is a huge cause of BSOD's.

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\041511-32947-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e9ae50
Debug session time: Fri Apr 15 17:07:39.133 2011 (GMT-4)
System Uptime: 0 days 10:42:23.293
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88010bd20f3, fffff88004935698, fffff88004934f00}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: 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: fffff88010bd20f3, The address that the exception occurred at
Arg3: fffff88004935698, Exception Record Address
Arg4: fffff88004934f00, 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: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+1a3
fffff880`10bd20f3 6409488b        or      dword ptr fs:[rax-75h],ecx

EXCEPTION_RECORD:  fffff88004935698 -- (.exr 0xfffff88004935698)
ExceptionAddress: fffff88010bd20f3 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x00000000000001a3)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88004934f00 -- (.cxr 0xfffff88004934f00)
rax=01cbfbb126f18f21 rbx=fffff8a001bc8010 rcx=fffffa8006659c20
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa8006650000
rip=fffff88010bd20f3 rsp=fffff880049358d0 rbp=000000000002440f
 r8=fffffa80069b3a00  r9=fffff88004935901 r10=0000000000000000
r11=fffffa8006606010 r12=0000000000000000 r13=0000000000000000
r14=fffffa80069b3b20 r15=0000000000000002
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x1a3:
fffff880`10bd20f3 6409488b        or      dword ptr fs:[rax-75h],ecx fs:0053:01cbfbb1`26f18eac=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

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 fffff80002f050e0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+1a3
fffff880`10bd20f3 6409488b        or      dword ptr fs:[rax-75h],ecx

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88010bcf803 to fffff88010bd20f3

STACK_TEXT:  
fffff880`049358d0 fffff880`10bcf803 : 00000000`00000000 fffffa80`069b8010 00000000`00000003 fffff8a0`01bc8010 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x1a3
fffff880`04935910 fffff880`10be965d : fffffa80`00000000 fffff8a0`01bd0050 fffffa80`00000000 fffffa80`069b3b20 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd6f
fffff880`04935ae0 fffff880`10be9398 : fffff880`02f67f40 fffff880`10be8d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04935cd0 fffff880`10be8e96 : 00000000`00000000 fffffa80`069b2480 00000000`00000080 fffffa80`06606010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04935d00 fffff800`02f707c6 : 00000000`03a09eb7 fffffa80`0664fa10 fffffa80`03cd1040 fffffa80`0664fa10 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04935d40 fffff800`02cabc26 : fffff880`02f63180 fffffa80`0664fa10 fffff880`02f6dfc0 fffff880`0124d534 : nt!PspSystemThreadStartup+0x5a
fffff880`04935d80 00000000`00000000 : fffff880`04936000 fffff880`04930000 fffff880`04935690 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgmms1
    fffff88010bd20f3 - dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+1a3
    [ 74:64 ]
1 error : !dxgmms1 (fffff88010bd20f3)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff88004934f00 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

I would also run memtest to verify your memory

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

 

[Dave76]

Please fill out your system specs, this will help with trouble shooting.

 

[Scythan]

Thanks, I uninstalled the driver that may be causing the problems. Just burned the memtest disk and will try that out ASAP. I also re-added my specs to my profile (guess I forgot to save when I had added them before). Thanks for the quick reply, and I'll let you know what happens.

 

[Dave76]

Run memtest with both RAM cards installed first, if you see any errors, stop the test.

Use this tutorial: RAM - Test with Memtest86+

 

[Scythan]

Okay, I let the boot disk memtest run for 5 passes, no errors. Since there's no errors, do I still need to swap out the ram like you said? I'm not all that comfortable with taking apart the computer, but I will if it's needed

 

[Dave76]

You need to run the test for a minimum of 7 passes, test # 5 and #7 usually find errors if they are there.
Run it overnight.

When you run memtest86+ you are looking for bad RAM cards, bad motherboard slots, so you need to follow the testing procedure in the tutorial.
Sometimes errors from these tests can be corrected by adjusting the settings.
RAM - Test with Memtest86+

Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.

For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums


Have you been checking your temperatures?

Use Real Temp , to check the CPU temps when at idle, under load and/or testing. Not on memtest86+ as it's a stand alone test.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and integrated memory controller voltages are.

 

[Scythan]

Here are the snips from the program. I'll do the memtest again overnight and get the rest of the info tomorrow. Thanks again for your help.

 

[Dave76]

The CPUZ info looks good.

Post the voltage settings from your BIOS, the CPU, RAM and integrated memory controller voltages.

 

[Scythan]

I hope this is what you are looking for:

CPU Vcore 1.120 V
3.3V 3.360 V
5V 5.129 V
12V 11.880 V

Also the memtest did 15 passes overnight, no errors.

 

[Scythan]

I left Real Temp on for a while, and played some Diablo 2. Let me know if there's something specific I should do with it on. Here are the temps:

Minimums
38 36 37 36

Maximums
66 58 59 57

 

[Dave76]

I hope this is what you are looking for:

CPU Vcore 1.120 V
3.3V 3.360 V
5V 5.129 V
12V 11.880 V

Also the memtest did 15 passes overnight, no errors.

CPU Vcore is the right one.
The other three are the system rail voltages, basically the 3v, 5v, 12v power supply feeds.

For these voltages in your BIOS look under 'Cell Menu' and scroll down.

Look for DRAM voltage.

For the integrated memory controller, look for 'CPU Vtt Voltage'.

If these only show a offset option, +0.001, select the smallest value increase. It should then show you the voltage number.


Are you using the Intel stock CPU cooler?
The temps look like the stock cooler, which are usually high compared to a $25-40 after market CPU cooler.
If you are running games and other high load programs, I would suggest a different CPU cooler. There are several that will keep your temps at idle 28c (room temp) full load 58c.

 

[Scythan]

Ugh, I posted but didn't see that it had an error and didn't go through. I've been having a lot of trouble posting here; sometimes it takes 4 or 5 tries for a post to go through.

I got the numbers:

CPU Vtt Voltage
Auto: 1.097V
Min: .451V
Max: 2.018V

DRAM Voltage
Auto: 1.600V
Min: .978V
Max: 1.898V

I'm pretty sure I have the stock cooler, but I don't really play any high load games, and the BSODs don't seem to happen any more frequently when playing games.

 

[Dave76]

Bump your CPU Vtt Voltage to 1.150v then run memtest86+ again for minimum 7 passes or overnight.

Let us know the results.


When was your last BSoD?

 

[Scythan]

I set the voltage to 1.149V (the closest it would go) and ran memtest overnight, no errors. I realized though that I've been using memtest86, not memtest86+. Should I redo the test tonight with that one instead? Also, I haven't gotten a BSOD since I've posted on here. They don't happen all that frequently, but this is a good sign

 

[Dave76]

Good news.

I would get the memtest86+ and run the test again, just to be sure.

 

[Scythan]

Just want to let you know that I ran the test (no errors) and haven't gotten a BSOD still. I'm going to pronounce it fixed unless it happens again. Thanks so much for your help

 

[Dave76]

Good news.

Let us know if there are no crashes after a week.