BSOD Win 7 x64 please help

Please fill out your system information. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.

You can make this easier by downloading Speccy.

Your dmp file shows an error code of 7E, memory corruption.

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

Code:

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_063010-17862-01.zip\063010-17862-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02e3fe50
Debug session time: Wed Jun 30 10:24:39.191 2010 (GMT-4)
System Uptime: 0 days 0:20:35.331
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002c8b1e3, fffff880009a98d8, fffff880009a9140}

Probably caused by : memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+4d3 )

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

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: fffff80002c8b1e3, The address that the exception occurred at
Arg3: fffff880009a98d8, Exception Record Address
Arg4: fffff880009a9140, 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: 
nt!MiInsertPageInFreeOrZeroedList+4d3
fffff800`02c8b1e3 498938          mov     qword ptr [r8],rdi

EXCEPTION_RECORD:  fffff880009a98d8 -- (.exr 0xfffff880009a98d8)
ExceptionAddress: fffff80002c8b1e3 (nt!MiInsertPageInFreeOrZeroedList+0x00000000000004d3)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a9140 -- (.cxr 0xfffff880009a9140)
rax=0000000000000000 rbx=fffffa8001b9b100 rcx=6000000001e98100
rdx=02000000000a32b0 rsi=0000000000000000 rdi=00000000000933b0
rip=fffff80002c8b1e3 rsp=fffff880009a9b10 rbp=fffff880009a9b80
 r8=5ffffa8001e98100  r9=0000000000000000 r10=fffff80002eac400
r11=0000058000000000 r12=fffffa8003600000 r13=000000000003ac00
r14=0000000000000780 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!MiInsertPageInFreeOrZeroedList+0x4d3:
fffff800`02c8b1e3 498938          mov     qword ptr [r8],rdi ds:002b:5ffffa80`01e98100=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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

FOLLOWUP_IP: 
nt!MiInsertPageInFreeOrZeroedList+4d3
fffff800`02c8b1e3 498938          mov     qword ptr [r8],rdi

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002cb96c6 to fffff80002c8b1e3

STACK_TEXT:  
fffff880`009a9b10 fffff800`02cb96c6 : fffffa80`01b9b100 00000000`000933b0 00000000`00000002 00000000`00000000 : nt!MiInsertPageInFreeOrZeroedList+0x4d3
fffff880`009a9c10 fffff800`02f17a86 : fffffa80`0374fb60 00000000`00000080 fffffa80`0374f040 fffff800`02c50af9 : nt!MmZeroPageThread+0x895
fffff880`009a9d40 fffff800`02c50b06 : fffff800`02dece80 fffffa80`0374fb60 fffff800`02dfac40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiInsertPageInFreeOrZeroedList+4d3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

STACK_COMMAND:  .cxr 0xfffff880009a9140 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MiInsertPageInFreeOrZeroedList+4d3

BUCKET_ID:  X64_0x7E_nt!MiInsertPageInFreeOrZeroedList+4d3

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

I find the following outdated drivers on your system. Win 7 does not like older drivers and they can cause conflicts.

amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB)
ccHPx64.sys Fri Jun 19 19:28:39 2009 (4A3C1F27)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
SRTSP64.SYS Mon Jun 22 22:45:21 2009 (4A4041C1)
SYMEFA64.SYS Tue Jun 23 17:52:39 2009 (4A414EA7)
SYMEVENT64x86.SYS Wed Jun 24 16:19:12 2009 (4A428A40)
SYMFW.SYS Mon Jul 06 20:29:22 2009 (4A5296E2)

Let's begin with updating these drivers.

How to update drivers (if you have a laptop, go to your laptop manufacturer's website first):

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Post back when you have updated these drivers and rebooted. Also please post if we can help you with this process.

If you are still receiving BSOD's, we will proceed to the next steps.

Thank you very much. I'll update the drivers and get back to you.
Also, if it shows memory corruption then does that mean that i should swap out my memory sticks? This is a newly built computer.
the driver reference link you posted doesn't seem to be a link.

I can't seem to find an update for those drivers.

jyeo said:

Thank you very much. I'll update the drivers and get back to you.
Also, if it shows memory corruption then does that mean that i should swap out my memory sticks? This is a newly built computer.

Not necessarily. Other things like drivers, incompatible programs, etc can corrupt memory. That is why I like to start by addressing the drivers. Our next step, if this does not solve the problem will be to test the RAM.

The driver reference link you posted doesn't seem to be a link.

I can't seem to find an update for those drivers.

Yes, I will try to find the correct link for you and I will help you with the drivers.

Thanks for fill in your system specs. That makes it easier.

Amdxata.sys with description Storage Filter Driver is a driver file from company Advanced Micro Devices belonging to product Storage Filter Driver. It is an AMD driver.

Global Provider of Innovative Graphics, Processors and Media Solutions | AMD

ccHPx64.sys - I have not been able to track this one down yet.

GEARAspiWDM.sys -

The process CDRom Class Filter Driver or Filter Driver for 2k and XP or CD/DVD Class Filter Driver or CD DVD Filter or GEAR ASPI Filter Driver belongs to the software GEAR.wrks or GEAR CDRom Filter or GEARAspi or GEARAspiWDM or Norton Ghost or MixMeister Studio Demo or MixMeister Pro or GEAR 32bit Driver Installer or MixMeister CD-R Drivers or Drive Image or Norton Save and Restore or CD DVD Filter or GearDrvs or iTunes or GEAR ASPI Filter Driver or GEAR driver installer for x

by GEAR Software Inc (www.gearsoftware.com).

SRTSP64.SYS - Symantec AutoProtect - AutoProtect - Symantec Corporation.

SYMEFA64.SYS - Norton Internet Security (NIS) (Symantec)

SYMEVENT64x86.SYS - More NIS. Symevent64x86.sys with description Symantec Event Library is a driver file from company Symantec Corporation belonging to product SYMEVENT

SYMFW.SYS - NIS firewall filter driver (Symantec)

Completely unistall NIS using the Symantec uninstall tool > Info > Tool. Do not uninstall with the Windows uninstaller. Norton may well be the cause of your BSOD's; it is a known cause conflict with Win 7 as are many security suites. I understand that NIS 2010 works with Win 7; but my personal opinion is that I would not install it on my system.

After you uninstall NIS using the uninstall tool, reboot and install MSE.

Report back.

Very good and thank you for reporting back with your solutions. Let's see how it runs. If you get another BSOD, post back and attach it ASAP. Post back in a couple of day and let us know it you are still BSOD free. Then we can mark this thread as solved.

Thank you for your service to the nation. I was a one star - but that star was in the middle of my chevrons, a sergeant major. That flag is the Gold Star flag, authorized to those families who have lost a spouse, son or daughter in the line of duty during a time of conflict.

Thanks for the update, jyeo. I hope the computer continues to run smoothly. But those drivers should definitely be updated.