first of all, win7 64bit
aus m4178lt-m le motherboard
ati rad 5670
So ive had my computer for months without any problems, a prebuilt off newegg
Then i start getting BSODs. They usually occured within the first 10 minutes of playing WoW. I would get a BSOD that said something along the lines of "IRQL not less or equal" or "page fault in non page area" and i remember one time "memory manegement". Then after i got the first blue screen of the day, what normally happend was it would blue screens on start up. So then I would frustrate and go into safe mode and try to fix things. Then while in safe mode i of course search the problem, i find it has to do with out of date drivers, so i go and update my display driver. Then i restart and no more blue screens for the rest of the day! then the next day the same thing happens, i turn on computer and play WoW, and within first 10 minutes i get a blue screen and go into safe mode and do something and then no more blue screens for the rest of the day. while in safe mode i tried updating display, removing leftovers from previous AV (northan), uninstalling a few programs. and after i did one of those things i went back and played WoW normally for the rest of the day.
So I got sick of the blue screens, and set BIOS to boot on CD, put in windows cd that came with computer and reinstalled windows (i chose the option that erases personal data). After that i of course updated drivers, specefically the display driver i updated via internet, and i installed the motherboard stuff with CD. And I thought this had fixed it for good.
But the next day I go on wow and again, with in the first 10 minutes, i get "memory management" BSOD. The only thing i had installed sense reinstalling windows was WoW and AVG. Therefore i come to the conclusion that AVG was the cause, so i uninstall AVG, then things seem normal for a bit but then i get another blue screen. So at this point I search more about the BSOD and decide i need to test RAM. I run memtest with bootable CD and memtest passes my ram 3 times. So then i search more and find about ASACPI.sys causing problems, and I remember seeing it somewhere but i was not sure where, so I decide that could be my problem and I decided to do what a post on some forums said to do about the problem, which was rename ASACPI.sys to ASCPI.old, and I did that. How ever im still having problems, and I have a memory dump of BSOD, i belive its only sense after i reinstalled windows.
please help
All of these are memory exceptions and the two most recent are caused by rdyboost.sys. I would stop using it and run memtest to verify your memory.
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.
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\Windows_NT6_BSOD_jcgriff2\122810-78000-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*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 Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a4a000 PsLoadedModuleList = 0xfffff800`02c87e50
Debug session time: Tue Dec 28 20:14:07.372 2010 (GMT-5)
System Uptime: 0 days 0:00:22.136
Loading Kernel Symbols
.............................................
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
.....Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {ffffffffc0000005, fffff88001004090, fffff88003339868, fffff880033390c0}
Probably caused by : rdyboost.sys ( rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+94 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88001004090, The address that the exception occurred at
Arg3: fffff88003339868, Exception Record Address
Arg4: fffff880033390c0, 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:
rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+94
fffff880`01004090 440fb702 movzx r8d,word ptr [rdx]
EXCEPTION_RECORD: fffff88003339868 -- (.exr 0xfffff88003339868)
Cannot read Exception record @ fffff88003339868
CONTEXT: fffff880033390c0 -- (.cxr 0xfffff880033390c0)
Unable to read context, Win32 error 0n30
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ac9a3a to fffff880012387f2
STACK_TEXT:
fffff800`00b9cc98 fffff800`02ac9a3a : 00000000`0029e937 fffffa80`051614c8 fffff800`02c42c40 00000000`00000001 : 0xfffff880`012387f2
fffff800`00b9cca0 fffff800`02ac46cc : fffff800`02c34e80 fffff800`00000000 00000000`00000000 fffff880`03f19db0 : nt!PoIdle+0x53a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
FOLLOWUP_IP:
rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+94
fffff880`01004090 440fb702 movzx r8d,word ptr [rdx]
SYMBOL_NAME: rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>::_ST_REGION_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+94
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: rdyboost
IMAGE_NAME: rdyboost.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc48a
STACK_COMMAND: .cxr 0xfffff880033390c0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_rdyboost!B_TREE_unsigned_long,ST_STORE_SMD_TRAITS_::_ST_REGION_ENTRY,4096,NP_CONTEXT_::BTreeSearchKey+94
BUCKET_ID: X64_0x7E_rdyboost!B_TREE_unsigned_long,ST_STORE_SMD_TRAITS_::_ST_REGION_ENTRY,4096,NP_CONTEXT_::BTreeSearchKey+94
Followup: MachineOwner
---------
Quote
it passed 3 times
