Windows 7: Random Bsods

hi,

for the last few weeks i have been plague with bsod seemly random, not sure what the problem is. I have tried just about everything, I was thinking it was a problem with the memory. I just reinstalled(today) hoping that would fix the problem but already have had 2 crashes. i'm thinking it a problem with ethier the motherboard or memory so kinda of hopeing someone can point me the right way so i know who to talk 2 should it be a hardware problem.

i will post any other dumps should more crashes happen.

Also should more info be needed please just ask



Thanks for your time

Hi.

It's memory corruption.

So, uninstall your antivirus and firewall apps to test. Don't just disable because that will be of no use.

If still not good, run Memtest86+ overnight to test the RAM.

It's also good to make sure the Vdimm (RAM voltage), timings and frequency are set correct for your specific RAM. Use the spd tab of CPU-Z to check the correct model number. Then visit the RAM maker's site for info on it. Set the motherboard bios accordingly.

Further, these drivers are old and should either be updated to latest or uninstalled from the system:

CTAUDFX CTAUDFX.DLL Mon Apr 09 09:08:39 2007
CTSBLFX CTSBLFX.DLL Mon Apr 09 09:08:42 2007
ha10kx2k ha10kx2k.sys Mon Apr 09 09:08:15 2007
COMMONFX COMMONFX.DLL Mon Apr 09 09:08:38 2007
ctsfm2k ctsfm2k.sys Mon Apr 09 09:08:11 2007
emupia2k emupia2k.sys Mon Apr 09 09:08:10 2007
nvm62x64 nvm62x64.sys Fri Oct 17 17:01:06 2008
ctprxy2k ctprxy2k.sys Mon Apr 09 09:08:30 2007
ctoss2k ctoss2k.sys Mon Apr 09 09:08:14 2007
ctaud2k ctaud2k.sys Mon Apr 09 09:08:29 2007
ASACPI ASACPI.sys Sun Mar 27 22:30:36 2005 <<< check this one first

Thank you for your time and help

Can someone help me? I have random crashes to. heres my dump file. I would really appreciate it.

Please start your own thread for your benefit and also for the OP too. Thanks.

Hi and welcome

I took a look at the dmp and its cause is pretty obvious. Memory corruption. That may have been caused by the old drivers listed below. They point out it was not a clean install as microsoft reccomends. You may also have a heat issue

I would download and run memtestx86 for several hours (overnight prefered)
Update the old drivers
Run a system file check to run type cmd in search>right click and run as admin>
SFC/SCANNOW

Let us know the results


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


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

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a4a000 PsLoadedModuleList = 0xfffff800`02c87e50
Debug session time: Sun Nov 22 18:19:37.702 2009 (GMT-5)
System Uptime: 0 days 0:35:45.261
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {40800000404, 2, 1, fffff80002adca73}

Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+c3 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000040800000404, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002adca73, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf20e0
0000040800000404

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiUnlinkFreeOrZeroedPage+c3
fffff800`02adca73 f0488300ff lock add qword ptr [rax],0FFFFFFFFFFFFFFFFh

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff880009a9a10 -- (.trap 0xfffff880009a9a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000040800000404 rbx=0000000000000000 rcx=0000000000000008
rdx=fffffa8003903070 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002adca73 rsp=fffff880009a9ba0 rbp=0000000000000036
r8=0000000000000000 r9=0000000000000000 r10=fffffa8003903090
r11=fffff880009a9c08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!MiUnlinkFreeOrZeroedPage+0xc3:
fffff800`02adca73 f0488300ff lock add qword ptr [rax],0FFFFFFFFFFFFFFFFh ds:00000408`00000404=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002abb469 to fffff80002abbf00

STACK_TEXT:
fffff880`009a98c8 fffff800`02abb469 : 00000000`0000000a 00000408`00000404 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009a98d0 fffff800`02aba0e0 : 00000000`00000000 fffffa80`01a94a20 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009a9a10 fffff800`02adca73 : 00000000`00000000 00000000`00000000 fffffa80`039d3b60 fffff800`02b034c5 : nt!KiPageFault+0x260
fffff880`009a9ba0 fffff800`02b03006 : 00000000`000000ff 00000000`00000036 00000000`00000001 00000000`00000000 : nt!MiUnlinkFreeOrZeroedPage+0xc3
fffff880`009a9c10 fffff800`02d5f166 : fffffa80`039d3b60 00000000`00000080 fffffa80`039d3040 fffff800`02a9a479 : nt!MmZeroPageThread+0x551
fffff880`009a9d40 fffff800`02a9a486 : fffff800`02c34e80 fffffa80`039d3b60 fffff800`02c42c40 00043842`000436d8 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiUnlinkFreeOrZeroedPage+c3
fffff800`02adca73 f0488300ff lock add qword ptr [rax],0FFFFFFFFFFFFFFFFh

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiUnlinkFreeOrZeroedPage+c3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiUnlinkFreeOrZeroedPage+c3

BUCKET_ID: X64_0xA_nt!MiUnlinkFreeOrZeroedPage+c3

Followup: MachineOwner

Hope this helps and if you have more crashes upload them so we can narrow our focus.

Ken J++
---------

update 2 days later

well i pulled the the device theat had the old drivers (old sound card). but still have some crashes. got my memeory timmings right and everything. ran both windows 7 mem test and memtest 86 and came up clean but with sfc scan windows found errors.
so would a full "clean" reistall help? hopefully this can be norrowed down to find the issuse as this is pretty annoying.


Thanks again

Bloodshot

A driver switched stacks using a method that is not supported by the operating system. The one in my quote is still on the system. This looks to be the likely cause of problems. Obviously, I had a hunch as per "check this one first."

You could also scan with Malwarebytes to be on the safe side.

thanks again, I went and removed the file so we will see thanks man though i feel like a rookie lol

You're welcome, although I'd check after rebooting to see that it hasn't returned. If so, update it somehow.

No need to feel like that. Less than one percent of users do not know how to debug so well, is my guess.