very strange BSODs

[encht]

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

 

[zigzag3143]

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.

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

 

[encht]

I alread ran memtest it passed 3 times

 

[encht]

another random bsod, attached new file

 

[zigzag3143]

another random bsod, attached new file

Yet another memory exception caused by your video driver. How many passes did you run memtest for? You need to run it for at least 5-6, and may need to run it one memory stick at a time

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\122910-27253-01.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`02a4d000 PsLoadedModuleList = 0xfffff800`02c8ae50
Debug session time: Wed Dec 29 01:17:52.988 2010 (GMT-5)
System Uptime: 0 days 0:39:18.752
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002aae155, 1, 21}

Probably caused by : hardware ( nt!MmSetAddressRangeModified+299 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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: fffff80002aae155, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000021, Parameter 1 of the exception

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!MmSetAddressRangeModified+299
fffff800`02aae155 834f2107        or      dword ptr [rdi+21h],7

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000021

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf50e0
 0000000000000021 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009020a90 -- (.trap 0xfffff88009020a90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000102 rbx=0000000000000000 rcx=fffffa8003da5f60
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002aae155 rsp=fffff88009020c20 rbp=fffff88009020ca0
 r8=fffffa80042210e8  r9=0000000000000000 r10=fffffffffffffffb
r11=fffff88002f63101 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MmSetAddressRangeModified+0x299:
fffff800`02aae155 834f2107        or      dword ptr [rdi+21h],7 ds:0bf8:00000000`00000021=????????
Resetting default scope

MISALIGNED_IP: 
nt!MmSetAddressRangeModified+299
fffff800`02aae155 834f2107        or      dword ptr [rdi+21h],7

LAST_CONTROL_TRANSFER:  from fffff80002afea17 to fffff80002abef00

STACK_TEXT:  
fffff880`09020208 fffff800`02afea17 : 00000000`0000001e ffffffff`c0000005 fffff800`02aae155 00000000`00000001 : nt!KeBugCheckEx
fffff880`09020210 fffff800`02abe542 : fffff880`090209e8 fffffa80`03daf660 fffff880`09020a90 00000000`00002478 : nt! ?? ::FNODOBFM::`string'+0x460da
fffff880`090208b0 fffff800`02abd0ba : 00000000`00000001 fffffa80`03daf660 00000000`00000000 fffff880`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`09020a90 fffff800`02aae155 : fffffa80`03daf660 00000000`00002478 fffff880`09020bf8 fffffa80`03da5f60 : nt!KiPageFault+0x23a
fffff880`09020c20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmSetAddressRangeModified+0x299


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MmSetAddressRangeModified+299
fffff800`02aae155 834f2107        or      dword ptr [rdi+21h],7

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MmSetAddressRangeModified+299

FOLLOWUP_NAME:  MachineOwner

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_NAME:  hardware

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

 

[encht]

Im about to go to sleep and i will leave memtest running for some hours.
i dont think this matters but i got memtest from Memtest86.com - Memory Diagnostic instead of the link u metioned above with .org

 

[encht]

I memtest over night and it got stuck on test 8 before even passing once. it started doing something else at the lower portion of the screen, heres some info it displayed.

max contiguos errors: 1
errors per mem slot 0:999999999
1:1
I also got new blue screens, uploaded the them,

I APRETCIATE YOUR HELP

 

[encht]

I tested both of the ram sticks with memest individually, in different slots, and it all passed....

im thinking the 1 time where i got 1 error was a one time thing and was just a "max contiguous error" what ever that means

 

[encht]

any ideas? i think when i tried reinstalling windows it just installed over it instead of erasing all of the old data, so i could try reinstalling it again ? yes no? im really stumped

 

[encht]

anything