Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: System_thread_exception_not_handled

21 Oct 2010   #1
event id

Windows 7 Ultimate x64

its me again... (my last thread)

and another BSOD, this time i just booted w7 and let it alone ( idle) in the desktop 3 minutes and BAM, this time it doesnt make a reference to the NTFS file, ( hal.dll) im sending the new dumps, HELP!

My System SpecsSystem Spec
21 Oct 2010   #2

Win 8 Release candidate 8400

Quote   Quote: Originally Posted by event id View Post
its me again... (my last thread)

and another BSOD, this time i just booted w7 and let it alone ( idle) in the desktop 3 minutes and BAM, this time it doesnt make a reference to the NTFS file, ( hal.dll) im sending the new dumps, HELP!

These were caused by memory corruption. Please run memtest
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

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

Loading Dump File [C:\Users\K\Desktop\102010-20607-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*;srv*e:\symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`03044e50
Debug session time: Wed Oct 20 23:08:49.599 2010 (GMT-4)
System Uptime: 0 days 0:02:43.410
Loading Kernel Symbols

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002f7ddac, fffff880031396a8, fffff88003138f00}

Probably caused by : memory_corruption ( nt!MiLogPageAccess+1fc )

Followup: MachineOwner

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

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
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002f7ddac, The address that the exception occurred at
Arg3: fffff880031396a8, Exception Record Address
Arg4: fffff88003138f00, 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.

fffff800`02f7ddac 488901          mov     qword ptr [rcx],rax

EXCEPTION_RECORD:  fffff880031396a8 -- (.exr 0xfffff880031396a8)
ExceptionAddress: fffff80002f7ddac (nt!MiLogPageAccess+0x00000000000001fc)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003138f00 -- (.cxr 0xfffff88003138f00)
rax=f683fffffd500000 rbx=fffffa8008eb4000 rcx=00fffa8008eb4220
rdx=fffff683fffffd50 rsi=00000000000002e6 rdi=fffb41fffffea800
rip=fffff80002f7ddac rsp=fffff880031398e0 rbp=0000000000000000
 r8=0000000000000001  r9=fffffa8008e903f8 r10=0000000000000005
r11=0000000000000000 r12=000000000000034e r13=fffff70001080488
r14=fffff80002fedc10 r15=fffffa8007137240
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
fffff800`02f7ddac 488901          mov     qword ptr [rcx],rax ds:002b:00fffa80`08eb4220=????????????????
Resetting default scope



PROCESS_NAME:  csrss.exe


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 fffff800030af0e0

fffff800`02f7ddac 488901          mov     qword ptr [rcx],rax


LAST_CONTROL_TRANSFER:  from fffff80002ee11d8 to fffff80002f7ddac

fffff880`031398e0 fffff800`02ee11d8 : 00000003`00000000 2e600002`5bd0c867 00000000`00000000 00000000`000002e6 : nt!MiLogPageAccess+0x1fc
fffff880`03139930 fffff800`02ef9a0e : fffffa80`08e903f8 fffff880`00000001 00000000`00000001 fffff880`03139bb0 : nt! ?? ::FNODOBFM::`string'+0x21846
fffff880`03139ae0 fffff800`02e8d6e2 : 00000000`000000a4 00000000`00000000 fffffa80`00000000 00000000`00000007 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`03139b80 fffff800`02e8d96f : 00000000`00000008 fffff880`03139c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03139bd0 fffff800`0311c166 : fffffa80`0792e040 00000000`00000080 fffffa80`0790f040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03139d40 fffff800`02e57486 : fffff800`02ff1e80 fffffa80`0792e040 fffff800`02fffc40 203d501c`fdb4eed2 : nt!PspSystemThreadStartup+0x5a
fffff880`03139d80 00000000`00000000 : fffff880`0313a000 fffff880`03134000 fffff880`03139710 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_NAME:  nt!MiLogPageAccess+1fc

FOLLOWUP_NAME:  MachineOwner



STACK_COMMAND:  .cxr 0xfffff88003138f00 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MiLogPageAccess+1fc

BUCKET_ID:  X64_0x7E_nt!MiLogPageAccess+1fc

Followup: MachineOwner
Plus update old drivers
How To Find Drivers:
- 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

Old drivers
AsIO.sys        fffff880`03b72000    644d65f3`03b78000    0x644d6d7300006000    0x416e4c91    10/14/2004 05:53:21                        
ADIHdAud.sys        fffff880`0493f000    644d65f3`049a9000    0x644d6d730006a000    0x4612c785    4/3/2007 17:30:45
My System SpecsSystem Spec
21 Oct 2010   #3
event id

Windows 7 Ultimate x64

edit, tested all 4 sticks, ( 8gb) in the first slot one pass each, no errors ( last 4gb did 2 passes)

removed 2 sticks, restarted the pc several times, no BSOD, i dont get it, i can play the most demanding games for hours using all 8gb with no problems ( never Bsod while playing ) but then im doing nothing and w7 crashes...
My System SpecsSystem Spec

23 Oct 2010   #4
event id

Windows 7 Ultimate x64

so im ruining with just 4 gigs now, and seems to be ok, ( enabled Execute Disable Bit on bios, dont know why it was disabled) uped the vcore, restored my previous mild oc back. Im tryng to find new versions of the drivers you bolded, now luck yet exept this > Version (bot now if its new enough) link

well, apparently it was a ddr2 issue... i was using the same model of ddr2 ram, but 2 of the sticks had qimonda chips, and the other 2 micron and value, removed the value tick ( 6gb total) and now its running perfect, with no hangs. lets see if this lasts!
My System SpecsSystem Spec


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar help and support threads
Thread Forum
I've had this super odd BSOD pop-up at seemingly random times, any help would be greatly appreciated.
BSOD Help and Support
I have a semi new system build and get random blue screens when gaming i think its Logitech software and maybe something else any help would be awesome thanks! On Sat 4/6/2013 10:04:41 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\040613-19359-01.dmp This was probably...
BSOD Help and Support
So after a very long time of no longer receiving any BSODs, I purchased a new graphics card (gtx680). The computer was running just fine until today when I got the bsod SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check code 0x1000007e parameter 1 ffffffff`c0000005 parameter 2 fffff880`0f983ca3 ...
BSOD Help and Support
I have been getting BSoD for quite a few months now (started saving copies and the oldest is April of this year) .. and because of the often occurrence I have a shortcut to my install of "BlueScreenView" on my desktop. The latest BSoD read as: Caused by address: amdppm.sys+28aead0...
BSOD Help and Support
BSOD,system_thread_exception_not_handled + M
Hello again! I'm using Windows 7 home premium 64 bit 8gb. It's my brothers old pc. While mine is away for some tweaks. Anyways I keep getting these Error's SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED I Included a zip with files and picture. From...
BSOD Help and Support
Bsod system_thread_exception_not_handled
(while i was writing here another BSOD appeared) computer is "old" (2009), after many BSOD at windows xp and windows 7 ultimate x64 I installed windows 7 ultimate x86 a week ago. I was prepared for BSOD and after my personal research I uninstalled the display driver, windows installed and...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:25.

Twitter Facebook Google+

Windows 7 Forums

Seven Forums Android App Seven Forums IOS App