BSOD help

aircon · 17 Sep 2010

Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: GA-MA790GPT-UD3H
BIOS: Award Modular BIOS v6.00PG
Processor: AMD Phenom(tm) II X4 945 Processor (4 CPUs), ~3.0GHz
Memory: 4096MB RAM
ati 5770 graphics card

I need some help troubleshooting the cause of my BSOD issues. It happens randomly. During idle and during heavy loads. I have RMAd the video card, RAM, swapped the power supply, tweaked the bios, changed the video card drivers, and other things. I am running out of ideas. If anyone can help me it would be greatly appreciated. i have attached several mini dumps. thanks

zigzag3143 · 17 Sep 2010

aircon said:

Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: GA-MA790GPT-UD3H
BIOS: Award Modular BIOS v6.00PG
Processor: AMD Phenom(tm) II X4 945 Processor (4 CPUs), ~3.0GHz
Memory: 4096MB RAM
ati 5770 graphics card

I need some help troubleshooting the cause of my BSOD issues. It happens randomly. During idle and during heavy loads. I have RMAd the video card, RAM, swapped the power supply, tweaked the bios, changed the video card drivers, and other things. I am running out of ideas. If anyone can help me it would be greatly appreciated. i have attached several mini dumps. thanks

The majority of these still point to the video driver or card. You may have ram'ed the card but there may be a problem on the mobo slot. You also have a few drivers that could use updating. Other causes mentioned, memory management, tcpip, etc.

If you are overclocking STOP, if you are running a RAID update its driver.

Code:

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


Loading Dump File [C:\Users\K\Desktop\New folder (4)\070710-18018-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03291e50
Debug session time: Wed Jul  7 19:21:02.141 2010 (GMT-4)
System Uptime: 0 days 3:53:47.530
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80072184e0, fffff88002c065a4, ffffffffc0000001, 3}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+65a4 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80072184e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002c065a4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+65a4
fffff880`02c065a4 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`061cea18 fffff880`044faef8 : 00000000`00000116 fffffa80`072184e0 fffff880`02c065a4 ffffffff`c0000001 : nt!KeBugCheckEx
fffff880`061cea20 fffff880`044ce569 : fffff880`02c065a4 fffffa80`065d8000 00000000`00000000 fffffa80`03a09410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`061cea60 fffff880`044faca5 : fffffa80`072184e0 fffffa80`072184e0 fffffa80`072184e0 fffffa80`03a09410 : dxgkrnl!DXGADAPTER::PrepareToReset+0x109
fffff880`061ceaa0 fffff880`045a1f07 : fffffa80`072184e0 00000000`00000000 fffffa80`071b8d50 fffffa80`03a09410 : dxgkrnl!TdrIsRecoveryRequired+0x245
fffff880`061cead0 fffff880`045cfd7e : fffffa80`ffffffff 00000000`000db3a4 fffff880`061cec30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`061cebb0 fffff880`0459d29e : fffffa80`03a09410 ffffffff`feced300 fffffa80`071b8d50 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`061cebf0 fffff880`045c9e7a : 00000000`00000000 fffffa80`071b8d50 00000000`00000080 fffffa80`03a09410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`061ced00 fffff800`03369a86 : 00000000`02a1a7c7 fffffa80`065b0b60 fffffa80`039d4040 fffffa80`065b0b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`061ced40 fffff800`030a2b06 : fffff800`0323ee80 fffffa80`065b0b60 fffff800`0324cc40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`061ced80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+65a4
fffff880`02c065a4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+65a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4be0c88c

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

aircon · 17 Sep 2010

i updated some drivers and i am not overclocked. im actually underclocked in ram. what do u recommend me doing if it still doesnt work?

Jonathan_King · 17 Sep 2010

Underclocking RAM is not a good idea, actually. Make sure your RAM speed meets or exceeds your motherboard speed.

If you have to underclock something, underclock your CPU.

I see different version of your ATI drivers installed, but there is still a chance you have a corrupted driver. I recommend removing your existing ATI drivers with Driver Sweeper, and installing this version: ATI Radeon

You will want Option 2- Driver only.

On to the other causes.

Install this Realtek network driver: Realtek

Code:

Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)

Uninstall Daemon Tools, as it is using SPTD. Then use this tool to uninstall SPTD: http://www.duplexsecure.com/download...t-v174-x64.exe

Code:

sptd.sys     Sun Oct 11 16:55:14 2009 (4AD24632)

Next, remove Norton with this tool: ftp://ftp.symantec.com/public/englis...moval_Tool.exe

Norton is known to cause BSODs on Vista and 7 machines. Microsoft Security Essentials is what we recommend as a replacement.

Also, uninstall Gigabyte's Easy Saver program, as it is known to cause BSODs.

Code:

gdrv.sys     Thu Mar 12 23:22:29 2009

Finally, run a RAM test tonight, when you're about to leave for bed, and let it run overnight: RAM - Test with Memtest86+

Let us know how it works out!

...Summary of the Dumps:

Code:

BugCheck 50, {fffff8a0186fa778, 0, fffff8000354b26a, 2}
Probably caused by : memory_corruption ( nt!MiRelocateImagePfn+3a )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff8000325b664, fffff880096ede30, 0}
Probably caused by : memory_corruption ( nt!MiValidateImagePages+294 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {48, 2, 1, fffff80003388b1f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {41284, 62fe001, 29c7, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 116, {fffffa800463c420, fffff88004558e84, ffffffffc0000001, 3}
Probably caused by : atikmpag.sys ( atikmpag+6e84 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {41201, fffff68000264cc0, 9e0000001135c847, fffffa80044a25b0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bb2 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {411, fffff683ff7847c8, 5ef000009a0b98c6, fffff683ff5847c9}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6051 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {41201, fffff680001f91d8, a450000016204847, fffffa800428bc80}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bb2 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck BE, {fffff880019490d0, 800000000473a121, fffff8800730d790, a}
Probably caused by : hardware ( tcpip!TcpTcbFastDatagram+18d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {fffffffffffffff8, 0, fffff80003593b94, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpChargeQuotaForObject+d0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {fffff8800b63ef00, 1, fffff80003597b93, 2}
Probably caused by : ntkrnlmp.exe ( nt!RtlpWow64CtxFromAmd64+193 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff960000c7779, fffff8800a2183c0, 0}
Probably caused by : win32k.sys ( win32k!SearchIconCache+39 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffda8006a86390, 0, fffff8800461d2e8, 7}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+398 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 116, {fffffa8004b3d4e0, fffff88004586c80, 0, 2}
Probably caused by : atikmpag.sys ( atikmpag+6c80 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {ffffe27fffffffe0, 2, 1, fffff80003305349}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffda8004150d20, 0, fffff88004f9d2e8, 7}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+398 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffd8a00c33d2c8, 0, fffff88004dfb70e, 7}
Probably caused by : atikmdag.sys ( atikmdag+35e70e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffda8004604a00, 0, fffff880047582e8, 7}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+398 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffd8a00cc0d348, 0, fffff88004d7c70e, 7}
Probably caused by : atikmdag.sys ( atikmdag+35e70e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {ffffe27fffffffe0, 2, 1, fffff80003309349}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {fffffa7ff9ffffd8, 2, 1, fffff800030a7274}
Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+1ca )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffd8a00d5e25c8, 0, fffff88004dd014e, 7}
Probably caused by : atikmdag.sys ( atikmdag+33b14e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffda8003e070d0, 0, fffff880044b22e8, 7}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+398 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffd8a00f3b2064, 0, fffff880047b2cf7, 7}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {ffffffffc0000005, fffff800030afe7e, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+13e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {ffffe27fffffffe0, 2, 1, fffff800030a7e7e}
Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+13e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

aircon · 18 Sep 2010

i did what the previous guy said buy updating and stuff and got another BSOD.. will try what what you said jonathan. will post results asap.

aircon · 18 Sep 2010

ugh.. i did everything but the memtest and i got a bsod again.. i will run the memtest today. i already RMAd one set of ram before as well as my video card. could it be my mobo? thats the only thing i havent replaced yet.. i attached 3 recent minidumps.

aircon · 18 Sep 2010

So I have been running memtest for a few hours now. No errors.

Jonathan_King · 18 Sep 2010

Appears to be caused by hardware; which piece, it does not tell.

If you can RMA motherboard, please do so.

What PSU are you using? Make/Model.

...Summary of the Dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 18 16:23:07.171 2010 (UTC - 4:00)
System Uptime: 0 days 0:32:20.950
BugCheck 3B, {c0000005, fffff96000056b7e, fffff88009b8afd0, 0}
Probably caused by : win32k.sys ( win32k!xxxInternalDoSyncPaint+6e )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  iTunes.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 18 15:10:43.744 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:14.508
BugCheck 1000007E, {ffffffffc0000005, fffff800032a1032, fffff88004fa1b28, fffff88004fa1390}
Probably caused by : memory_corruption ( nt!MiResolveDemandZeroFault+2e2 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 18 15:00:56.870 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:13.634
BugCheck 1000007E, {ffffffffc0000005, fffff88002a36b56, fffff88002fa82b8, fffff88002fa7b20}
Probably caused by : hardware ( netbt!ReadParameters+69d )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨