Random BSOD

[Letg]

Im having some random BSOD every now and then. Usually it happens while playing. My screen just goes "pixely" and after a second BAM, BSOD. It have been happening more often now, and i think not every of them have made minidumps becouse there were just 3.

This computer is just few weeks old and OS is x64.

Also, my OS isnt in english so some of the files might be in different language.

EDIT: System specs are at my profile if needed.

EDIT2: Also i have ran Prime95 for hour without any problems (i know, i should run it longer but didnt have time when i did it.) Also Furmark for testing if it was my temps. I did try some in-windows memtester too and it didnt say anyting about errors.

 

[CarlTR6]

Hi, Letg and welcome to the forum. All three of your dumps indicate memory corruption and one blames a video driver, atikmdag.sys. How long did you run Furmark? Did you run it until your temps leveled off? Did the temps get too high? I suggest that you run it again folowing the instructions in this tutorial:http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html. Post back with your results.

Uninstall Daemon Tools or Alcohol or whatever CD virtualization program you are running. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Select uninstall; do NOT select reinstall.

Here is a free alternative CD virtualization program that does not use the sptd.sys driver.
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

I suggest that you uninstall Comodo. Comodo is known to cause BSOD's on some Win 7 systems. Dowload Revo Uninstaller (free) and use it to completely uninstall Comodo. Once you get your system stable, you can try Comodo again. In the meantime, make sure Windows Firewall is turned on.

It appears that you are Running Windows Defender Defender causes problems with Win 7. Download and install Microsoft Security Essentials. It supersedes Defender, offers much better protection, and runs smoothly with Win 7. MSE will turn Windows Defender off; you don't have to do anything.

Once you have installed MSE and uninstalled Comodo and sptd.sys, run your system and see if it is more stable. Post back and let us know. If you get another BSOD, upload it and we will go from there and do some hardware testing.

Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c63000 PsLoadedModuleList = 0xfffff800`02ea0e50
Debug session time: Mon Dec 20 14:22:26.322 2010 (GMT-5)
System Uptime: 0 days 5:19:20.337
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88004c112ae, fffff8800a3fa8c0, 0}

Probably caused by : atikmdag.sys ( atikmdag+3992ae )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88004c112ae, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800a3fa8c0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
atikmdag+3992ae
fffff880`04c112ae 8178083000bebe  cmp     dword ptr [rax+8],0BEBE0030h

CONTEXT:  fffff8800a3fa8c0 -- (.cxr 0xfffff8800a3fa8c0)
rax=002e003000300036 rbx=000000000000004d rcx=fffff8a000ba0df0
rdx=fffffa80042257f0 rsi=0000000000000069 rdi=fffffa8005c8cd38
rip=fffff88004c112ae rsp=fffff8800a3fb298 rbp=fffffa8005c8c600
 r8=fffffa8005c8c600  r9=0000000000000069 r10=fffff88004878000
r11=fffff8a00ddf3448 r12=0000000000000001 r13=fffffa80042257f0
r14=ffffffffc000000d r15=fffffa8005aad000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
atikmdag+0x3992ae:
fffff880`04c112ae 8178083000bebe  cmp     dword ptr [rax+8],0BEBE0030h ds:002b:002e0030`0030003e=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88004c112ae

STACK_TEXT:  
fffff880`0a3fb298 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x3992ae


FOLLOWUP_IP: 
atikmdag+3992ae
fffff880`04c112ae 8178083000bebe  cmp     dword ptr [rax+8],0BEBE0030h

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+3992ae

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cef1f94

STACK_COMMAND:  .cxr 0xfffff8800a3fa8c0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+3992ae

BUCKET_ID:  X64_0x3B_atikmdag+3992ae

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

 Debug session time: Wed Dec 22 15:31:32.756 2010 (GMT-5)
System Uptime: 0 days 6:22:14.130
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffffff, 8, ffffffffffffffff, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42837 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffffffffffff, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: ffffffffffffffff, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0e0e0
 ffffffffffffffff 

FAULTING_IP: 
+5c94952f01afde38
ffffffff`ffffffff ??              ???

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  uTorrent.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88007a811c0 -- (.trap 0xfffff88007a811c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88007a813f8 rbx=0000000000000000 rcx=fffff88007a813f8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=ffffffffffffffff rsp=fffff88007a81358 rbp=fffff88007a814a0
 r8=0000000000000000  r9=0000000000000000 r10=fffff8800128d700
r11=fffffa8003efd5e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
ffffffff`ffffffff ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d56f14 to fffff80002cd6740

STACK_TEXT:  
fffff880`07a81058 fffff800`02d56f14 : 00000000`00000050 ffffffff`ffffffff 00000000`00000008 fffff880`07a811c0 : nt!KeBugCheckEx
fffff880`07a81060 fffff800`02cd482e : 00000000`00000008 fffffa80`057e0e40 fffffa80`04c78600 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`07a811c0 ffffffff`ffffffff : fffff880`012e3a0c fffffa80`00000000 fffffa80`057e0e40 fffff880`07a814a0 : nt!KiPageFault+0x16e
fffff880`07a81358 fffff880`012e3a0c : fffffa80`00000000 fffffa80`057e0e40 fffff880`07a814a0 00000000`00000000 : 0xffffffff`ffffffff
fffff880`07a81360 fffff880`0100323f : fffff880`07a81501 fffffa80`0678ac10 fffff880`07a88000 00000000`00000002 : Ntfs!NtfsFsdClose+0x20c
fffff880`07a81460 fffff880`010016df : fffffa80`04c78600 fffffa80`0678ac10 fffffa80`04947e00 fffffa80`0678ac10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`07a814f0 fffff800`02fec78e : fffffa80`057e0e40 fffffa80`04b1b890 fffffa80`057e0e40 fffffa80`04c78600 : fltmgr!FltpDispatch+0xcf
fffff880`07a81550 fffff800`02cdb8b4 : fffffa80`04d59580 fffff800`02fd9260 fffffa80`03b65080 00000000`ff060001 : nt!IopDeleteFile+0x11e
fffff880`07a815e0 fffff800`02fda0e6 : fffff800`02fd9260 fffff880`01022cb0 fffff880`07a819d0 fffffa80`09c8fc10 : nt!ObfDereferenceObject+0xd4
fffff880`07a81640 fffff800`02fcfe84 : fffffa80`04b0ac50 fffff880`01022cb0 fffffa80`09f7f700 fffff680`0001a601 : nt!IopParseDevice+0xe86
fffff880`07a817d0 fffff800`02fd4e4d : fffffa80`09f7f700 fffff880`07a81930 fffffa80`00000040 fffffa80`03b65080 : nt!ObpLookupObjectName+0x585
fffff880`07a818d0 fffff800`02fba36a : fffff880`07a81ac8 00000000`0098e7f8 fffff8a0`02db5a01 fffff800`02fbcdad : nt!ObOpenObjectByName+0x1cd
fffff880`07a81980 fffff800`02cd5993 : fffffa80`03ca7b60 fffff880`07a81ca0 fffffa80`03ca7b60 00000000`c0000034 : nt!NtQueryAttributesFile+0x149
fffff880`07a81c20 00000000`779e012a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0098e7b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779e012a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42837
fffff800`02d56f14 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42837

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+42837

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+42837

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

 

[Letg]

First of all, thanks for the help.
No crashes so far, i did everything except Furmark as i did it before. I waited until Furmark was at max temp (didnt go higher) and didnt see any artifacts or crashes.

There is one thing i noticed while checking one other thing at CPU-Z. I have A-DATA Technology 1333mhz CL9 2x2gb kit. Now look at the picture i attached. Shouldnt it be running in different latency? Can this cause BSOD?

My BSOD have been very random so i dont know yet if this is stable or not, but i hope so.

 

[CarlTR6]

It probably is not your graphics card; but since one of the dumps blamed the graphics card, we needed to check that possibility. Since your temps leveled out and were not too high during Furmark, your video card is probably just fine. I suspect is was SPTD.sys and Defender causing conflicts and, possibly Comodo.

I am not a hardware Guru; but I will ask the hardware Gurus to look at your post and answer your question about latency. I am glad you are running stable so far.

 

[Hopalong X]

I don't see anything wrong with the latency.

CL9 running 8 isn't unusual. If it were 5 or 11 maybe. Your Bios controls the voltage which controls speed which sets timings etc.

Asus moboard bios is probably set Auto on the RAM which is default. When usage kicks up it will adjust to load BUT CPU-Z does not show this well.

On mine not at all. CPU-Z shows the same all the time.
Look at the pic below.

It actually is running 8-8-8 at 720MHz. Not any of those are even listed.

So simple terms it is perfectly fine.
CPU-Z is good for CPU info and just basic RAM info.

Mike

 

[CarlTR6]

Thank you Mike; I appreciate it.

 

[Dave76]

What was your GPU temp during the Furmark test?

What GPU driver are you using?

Are you overclocking the CPU?

What is your BIOS version?

Your RAM running at 8-8-8-20 shouldn't be a problem, as Hopalong X mentioned.

D/L and run Memtest86+, follow the steps in the tutorial below.
RAM - Test with Memtest86+

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.

Post the information here.


Have you been checking your temperatures?

Use Speed Fan or Core Temp , run one of these and check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and tell us what the CPU, RAM and North Bridge (NB) voltages are.

 

[Letg]

What was your GPU temp during the Furmark test?

Maximum of 85*C if i remember right. That shouldnt be too high for my card.

What GPU driver are you using?

10.12

Are you overclocking the CPU?

Everything is running at stock speed.

What is your BIOS version?

Second newest, newest one doesnt fix anything else than some "Update LAN option ROM to 2.35 ". Dont know what that even is. Current version that i have is 1005

Have you been checking your temperatures?

Yes, they are all fine. During Prime95 my CPU doesnt even go over 49*C
At idle its at 30*C

Go to your BIOS and tell us what the CPU, RAM and North Bridge (NB) voltages are.

RAM = 1,55V
CPU = Auto (1.320)
NB = Auto (1.150)

D/L and run Memtest86+, follow the steps in the tutorial below.

I will do that if my computer BSOD again becouse currently i cant keep it on for long times during xmas.


Still no BSOD or crashes after changing anti-virus and deleting that driver. Hopefully it will stay this way

 

[CarlTR6]

Thank you, Dave.

 

[Dave76]

@Carl, your welcome, as always.



Letg, I hope you don't get another BSoD either.

If you do, run memtest86+, if you get errors you can stop the test and then follow the steps in the tutorial.
Let us know the results.

Depending on the memtest86+ results we can try adjusting the RAM settings and voltages.

 

[Letg]

Okay, new BSOD appeared. I was playing WoW for mayby 20min and second after clicking "Exit Game" computer crashed.
I will upload the dump file so you can check it too.
This time it was BAD_POOL_CALLER.

I will also start testing my RAM now.

 

[CarlTR6]

Nothing new in the dump. We will wait for the Memtest results.

 

[Letg]

Zero errors after 7 passes.

I also included my RAM settings to this post, if needed.

EDIT: Decided to go with lower settings just to be sure, so its running 9-9-9-24 now.
Thats becouse i think these RAM are specced to that speed, not 8-8-8-20.
Row Cycle Time is at 32 now. I would like someone to confirm if these are right for this RAM.

 

[Dave76]

Zero errors with memtest86+, that's good.
Unfortunately it doesn't mean there are no RAM issues, now run Prime95 as mentioned below.

Looser timings won't hurt anything.

Go to BIOS and check the DRAM voltage, post it here.
Should be at least 1.5v. If it is still 1.55v it's ok, just leave it there.

The SPD tab from CPUZ is the manufacturers recommended settings at different DRAM Frequencies.
Your previously posted SPD, JEDEC #2 for 533 MHz is 7-7-7-20 and command rate 2T.

You can leave them at 8-8-8-20 if your happy with that, you won't see any difference in performance from 7-7-7-20.
If you want to change for testing, enter the first four timings, 7-7-7-20, manually and leave the rest in auto.
Make sure the Command rate stays at 2T.
Leave it in DC Mode: Unganged.

Run Prime95 torture test, this will test CPU and RAM. For at least one hour.

CPU - Stress Test with Prime95

When you open Prime95 click 'Options' tab > Torture Test > select 'Blend', fill in number of threads to run.
Be sure to watch the CPU temps with Core Temp.
Stop the test if the temps get to 60 deg C.
AMD Phenom II x6 1055T Product Details


Let us know the results.

 

[Letg]

I just started Prime95 Blend test, but i dont think this will fail.
I have ran Blend for over hour before and it CPU didnt even get over 50*C thanks to my Mugen 2.
But if it fails, i will report here.

EDIT: I left my RAM settings to 9-9-9-24 just to be sure that it isnt causing this. Also i raised voltage from 1.55 to 1.625 (a friend of mine suggested to raise it a little).
Also i noticed something when i loosened the timings. Usually when i login to WoW, my FPS is VERY low for mayby 5 second, but now it didnt do that. Im not sure if thats permanent change or i was just lucky, i will test that more when Prime has stopped running.

 

[Letg]

After over hour of Prime, no errors/crashes.

Temps: CPU: 48*C
MoBo: 27*C

Also, is it safe to have RAM voltage up to 1,5625?
Re-checked the voltages and it was 1,562 and not 1,625 ^^.

 

[Dave76]

Good news that Prime95 passed.

The RAM voltage should be alright for your system.

When you posted the NB voltage was this from the CPU/NB Voltage?
If this is not what you posted, check it and post it here.
You might have to set it to Manual to get a voltage reading.

Since the tests all passed, try to re-create the last BSoD from your game.

 

[Letg]

Yes, it was from CPU/NB Offset Voltage and it was on [Auto], but next to it reads 1.150 on gray, so i think its on 1.150V.
I have played some time now without any errors or crashes. Hopefully it was becouse of too tight timings/low voltage.
If i get a crash, i will post it here.

 

[Dave76]

More good news, I hope it's going to be stable for you from now on.

If you get another crash post here.

The next step with the RAM would be some voltage adjustments for RAM and CPU/NB.
You have to be very careful with CPU/NB voltage.

Let us know how it's going, if you have no crashes in the next week drop us a post.

 

[CarlTR6]

I am glad they your system is doing much better. Good work.