Windows 7 random BSOD

K76154

New Member
#1
Moving to windows 7 forum
 


Last edited:

K76154

New Member
#2
I have been seeing BSOD for quite a while, but they have been very rare. My guess is that it is related to my memory slots on the mainboard, because I can't boot now if I insert the memory into slot 1 or 4 on the mainboard. The BSOD happened much more frequently recently, and sometimes it can't boot after BSOD. When it can't boot, I have to remove the memory from the mainboard and try to insert it again and again until it works. It's very likely that there's something wrong with the memory slots, but that's still just my guess, and there may be other reasons. So can anyone please help me check the logs and see what's the real cause of this frequent BSOD?
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#3
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88013e34c7a, fffff880049cb738, fffff880049caf90}

Probably caused by : nvlddmkm.sys ( nvlddmkm+35ac7a )

Followup: MachineOwner
Code:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
Hi,
you have quite a few different types of dump file or should I say Bugchecks. The one I posted above is the most frequent one and along with it blaming your GPU driver many of the other dumps with similar bugchecks also mentioned Norton AV. This type of bugcheck means either the above driver is causing the issue or something is causing this driver to crash. We can look through the dump file further and see it was when the system tried to read data from the memory. This could mean either the data or the memory itself is corrupt.

I see your running Norton AV which is well known amongst debugging circles for causing issues. It's also mentioned several times in your dump files too. Please uninstall using this tool:
https://support.norton.com/sp/en/uk/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us
Use MSE in the meantime as it's ultra stable:
http://windows.microsoft.com/en-GB/windows/security-essentials-download

avpnnic.sys Mon Sep 24 18:56:37 2007: AGN Virtual Network Adapter Driver - AT&T? Update if possible.

AppleCharger.sys Mon Jan 10 09:57:29 2011: GIGABYTE On/Off Charge driver. May cause BSOD on Win7/8 systems - uninstall to test

dtsoftbus01.sys Thu Jan 13 08:27:08 2011: Daemon Tools driver. Possible BSOD issues in Win7 uninstall to test.

Neo_0114.sys Fri May 02 05:58:09 2008: SoftEther VPN Project driver. This also appeared as a probable cause please try and update or remove if you have stopped using it:
https://www.softether.org/5-download

nvlddmkm.sys Thu Dec 19 17:02:52 2013: Nvidia GPU driver please update:
http://www.nvidia.com/download/driverResults.aspx/77884/en-uk

nusb3hub.sys Fri Nov 20 10:15:57 2009: NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions) This is actually a Renesas D720200 chip and the most recent drivers can be found here:
http://station-drivers.com/index.ph...SB3-Controller-Drivers-Version-2.1.39.0-WHQL/

vmnetadapter.sys Fri Jul 08 08:43:56 2011: VMware virtual network adapter driver please update:
http://www.vmware.com/support/


Regarding your memory stick issue:

This is taken from your motherboard manual and explains about dual channel memory. If your using an AMD board (like me) the dual channel is always more desirable because it doubles the bandwith. To obtain dual channel however one must place the sticks (when there's only two of course) in certain slots which I've arrowed above. The formula is either 1 & 3 or 2 & 4 as placing them side by side in slots 1 and 2 won't give dual channel.

Have you tried using either configuration shown above?

You need to test your RAM.

Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/

To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Try and run the test overnight if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

Post back with any new dump files or updates
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.