BSOD STOP: 0x0000007E on New Build

[WrongtownReilly]

Hi All,

I'm having trouble with seemingly random BSOD's on my new build. The specs are as follows;

MoBo: Gigabyte PA67A-UD3-B3
CPU: Intel Core i7 2600 3.4GHz
GPU: Asus Nvidia GT440
Memory: 2x Crucial 4GB DDR3 PC3-10600
PCI: Belkin Firewire 800 Card
OS: Windows 7 Home Premium 64-Bit


The BSOD seems to be happening at random and the screen shows the following code:

STOP: 0x0000007E (0xFFFFFDFFFC0000005, 0xFFFFF80003113349, 0XFFFFF880009A9998, 0xFFFFF880009A9200


I'm also getting a message saying my display adaptor has stopped working but has recovered which may point to the graphics card as the culprit.

I've tried memtest on the RAM and also sfc /scannow but neither have returned any errors. I've also updated my Bios and downloaded the latest graphics drivers from the NVidia website.

I have attached the .dmp file from the latest crash in case this helps track down the issue. I'm not sure of how to analyse it myself.

Can anyone suggest a possible solution to this? This has happened a few times today alone and is the source of much frustration!

Thanks,
Reilly

 

[zigzag3143]

Hi All,

I'm having trouble with seemingly random BSOD's on my new build. The specs are as follows;

MoBo: Gigabyte PA67A-UD3-B3
CPU: Intel Core i7 2600 3.4GHz
GPU: Asus Nvidia GT440
Memory: 2x Crucial 4GB DDR3 PC3-10600
PCI: Belkin Firewire 800 Card
OS: Windows 7 Home Premium 64-Bit


The BSOD seems to be happening at random and the screen shows the following code:

STOP: 0x0000007E (0xFFFFFDFFFC0000005, 0xFFFFF80003113349, 0XFFFFF880009A9998, 0xFFFFF880009A9200


I'm also getting a message saying my display adaptor has stopped working but has recovered which may point to the graphics card as the culprit.

I've tried memtest on the RAM and also sfc /scannow but neither have returned any errors. I've also updated my Bios and downloaded the latest graphics drivers from the NVidia website.

I have attached the .dmp file from the latest crash in case this helps track down the issue. I'm not sure of how to analyse it myself.

Can anyone suggest a possible solution to this? This has happened a few times today alone and is the source of much frustration!

Thanks,
Reilly

Reilly hard to diagnose from one DMP but I do notice that Your Avast service was the active thread at the time of the crash. I would remove and replace it with Microsoft Security Essentials to test if nothing else

http://files.avast.com/files/eng/aswclear5.exe

http://www.microsoft.com/security_essentials/

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


Loading Dump File [C:\Users\K\Desktop\050711-18080-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03058000 PsLoadedModuleList = 0xfffff800`03295e50
Debug session time: Sat May  7 05:22:37.370 2011 (GMT-4)
System Uptime: 0 days 0:23:27.291
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffea8008d960f0, 1, fffff800030cd80c, 7}


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

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: ffffea8008d960f0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800030cd80c, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800033000e0
 ffffea8008d960f0 

FAULTING_IP: 
nt!ObfDereferenceObject+2c
fffff800`030cd80c f0480fc11f      lock xadd qword ptr [rdi],rbx

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  AvastSvc.exe

 

[WrongtownReilly]

Hi zigzag, thanks for your reply.

I've attached five additional dumps to this post.

Thanks for the Avast suggestion, I will try replacing it with MSE and report back.

Thanks,
Reilly