Windows 7: Ramdom BSOD in Win 7 Ultimate

Hello all.

I have win 7 Ultimate x86 on my machine but randomly i get BSOD that is very anoying. In the begginen i found that Daemon Tools was the cause of that and after i upgrade everything was fine.

What happened now? Can anyone debug and tell me? I m suspecting that Internet Download Manager is the cause but can anyone tell me fro sure?

Thx in advance

well both dumps contained memory corruption. I would start there

I would
download and run memtestx86 (preferably overnight)
if overclocking stop
run a system file check by typing cmd in search>right click and run as admin>\
sfc /scannow



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


Loading Dump File [C:\Users\K\Desktop\111409-29734-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c4a000 PsLoadedModuleList = 0x82d89570
Debug session time: Sat Nov 14 07:15:46.839 2009 (GMT-5)
System Uptime: 0 days 0:11:21.167
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {14, 2, 0, 82cbf10b}

Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+5 )

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

0: 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: 00000014, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 82cbf10b, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82da9700
Unable to read MiSystemVaType memory at 82d890c0
00000014

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiFindNodeOrParent+5
82cbf10b f7401400ffffff test dword ptr [eax+14h],0FFFFFF00h

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: 9da3568c -- (.trap 0xffffffff9da3568c)
ErrCode = 00000000
eax=00000000 ebx=8558bba8 ecx=00000000 edx=00000000 esi=8558bba8 edi=82d6bd20
eip=82cbf10b esp=9da35700 ebp=9da35700 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!MiFindNodeOrParent+0x5:
82cbf10b f7401400ffffff test dword ptr [eax+14h],0FFFFFF00h ds:0023:00000014=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 82cbf10b to 82c82b5b

STACK_TEXT:
9da3568c 82cbf10b badb0d00 00000000 82d78148 nt!KiTrap0E+0x2cf
9da35700 82cfd08e 9da35714 9da3572c 82cfd1b3 nt!MiFindNodeOrParent+0x5
9da3570c 82cfd1b3 00000000 8558bb80 8558bc10 nt!MiLocateAddressInTree+0x11
9da3572c 82cab537 8558bb80 00000000 00000000 nt!MiGetSharedProtos+0x5d
9da3574c 82c75677 ad2e38f0 84c6af08 84c6af10 nt!MiComputeStartingOffset+0x61
9da35794 82c736f1 00000076 857ff000 9da3583c nt!MiIdentifyPfn+0x28b
9da357c0 82e2de9e 857ff060 b2272e09 9da35850 nt!MmQueryPfnList+0xaf
9da35808 82e5f07e 9da35c01 b2272e89 00000000 nt!PfpPfnPrioRequest+0xde
9da35888 82e445af 00000000 9da35c01 9da35cd0 nt!PfQuerySuperfetchInformation+0xea
9da35d00 82e420fb 0000004f 00000000 00000000 nt!ExpQuerySystemInformation+0x24a4
9da35d1c 82c7f79a 0000004f 0136ed50 00000014 nt!NtQuerySystemInformation+0x76
9da35d1c 771764f4 0000004f 0136ed50 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0136cc10 00000000 00000000 00000000 00000000 0x771764f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiFindNodeOrParent+5
82cbf10b f7401400ffffff test dword ptr [eax+14h],0FFFFFF00h

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiFindNodeOrParent+5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbffc

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiFindNodeOrParent+5

BUCKET_ID: 0xA_nt!MiFindNodeOrParent+5

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

hope this helps and let us know the results


Ken N

Thank u for your quick answer.
Almost every BSOD i have seen in WIN 7 (not only in my PC but also in friends) it says about memory problems.
I don't have any probs with my hardware for sure. I have also test with memtest and everything is ok.

I m sure that there is not any hardware related prob because when i install Vista everything runs smooth for months, without any prob. The BSOD happens only when i install the beautifull but stupid win 7....

This can still be a low NB voltage in bios problem. I've seen it before when going from Vista to Windows 7, instablity for no apparent reason at all on my own machine and quite a few others, easily fixed by upping the NB voltage a tad. Are you running the 2T command rate on your memory?

Passing memtest doesn't mean much. Try running Prime Blend and see how far you can get with it.