Getting different BSOD in win7 64

Hi!

Sinse i installed Windows 7 64 i been having som problems with system crashes.

I get different types of BSOD:s

IRQL_NOT_LESS_OR_EQUAL

page_fault_in_nonpaged_area

and somethimes the system freeze and i have to reboot it.

i have formated the os 2-3 times but still the same, i hade win 7 32 before without
any problems at all. so this is getting on my nerves..

ive read the minidump but dont really know what to go next.. i dont know how you do to read what drivers that where in use from the minidump in WinDbg

I attached the minidmp file.. Hope you can help me.

Best regards.

Lets try again :)

i recently did some memtesting so i only have 2gig ram installed, original 4gig

And i se now when i did the report that one driver is not installed..

I have checked it trough and i dont know what driver that is missing..

CarlTR6 said:

This is a BugCheck error A, IRQL_NOT_LESS_OR_EQUAL - BSOD Index. It is a hardware or hardware related error. The dump file blames memory corruption.

Code:

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Windows7_BSOD+perfmon report.zip\Windows7_BSOD_jcgriff2\080510-19656-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a53000 PsLoadedModuleList = 0xfffff800`02c90e50
Debug session time: Thu Aug  5 15:00:24.673 2010 (GMT-4)
System Uptime: 1 days 11:00:32.609
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
...........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {28, 2, 0, fffff80002b05410}

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

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

1: 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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002b05410, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfb0e0
 0000000000000028 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiFindNodeOrParent+0
fffff800`02b05410 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  iexplore.exe

TRAP_FRAME:  fffff8800318d5c0 -- (.trap 0xfffff8800318d5c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b05410 rsp=fffff8800318d758 rbp=0000000000000000
 r8=fffff8800318d7a0  r9=0000000000000000 r10=fffffa8003d2a0f0
r11=fffffa8003d04330 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiFindNodeOrParent:
fffff800`02b05410 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h ds:0488:00000000`00000028=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ac2b69 to fffff80002ac3600

STACK_TEXT:  
fffff880`0318d478 fffff800`02ac2b69 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0318d480 fffff800`02ac17e0 : fffffa80`03f15000 fffffa80`03d2a138 00000000`0000000e fffff880`0492fbb6 : nt!KiBugCheckDispatch+0x69
fffff880`0318d5c0 fffff800`02b05410 : fffff800`02b09197 fffff880`009e9180 00000000`00000002 00000000`00000001 : nt!KiPageFault+0x260
fffff880`0318d758 fffff800`02b09197 : fffff880`009e9180 00000000`00000002 00000000`00000001 fffff700`01080488 : nt!MiFindNodeOrParent
fffff880`0318d760 fffff800`02b0911d : 00000000`63416d4d 00000000`00000002 00000000`00000000 00000000`00001000 : nt!MiLocateAddressInTree+0x17
fffff880`0318d790 fffff800`02b09228 : 00000000`00000000 fffffa80`0232b000 fffffa80`0192cb28 fffffa80`03d2a1a8 : nt!MiGetSharedProtosAtDpcLevel+0xbd
fffff880`0318d7e0 fffff800`02a6119b : fffff800`02c39c18 fffff800`02ad6b90 fffff880`0318d8d8 fffff880`009e9180 : nt!MiGetSharedProtos+0x18
fffff880`0318d810 fffff800`02bc97d0 : e3700000`74974c46 fffffa80`03d2a130 fffff880`009e9180 fffff800`02ad1621 : nt! ?? ::FNODOBFM::`string'+0x927b
fffff880`0318d840 fffff800`02bc99b0 : fffffa80`030a6060 00000003`00000000 fffffa80`03d2a0f0 fffffa80`03d2a1a8 : nt!MiEmptyPageAccessLog+0x160
fffff880`0318d8b0 fffff800`02bc9bb6 : fffffa80`0192c000 00000000`0000089b fffff680`003afc28 00000000`00000000 : nt!MiAllocateAccessLog+0x80
fffff880`0318d8e0 fffff800`02b2b568 : 00000003`00000000 09b00000`7a742025 00000000`00000000 00000000`0000089b : nt!MiLogPageAccess+0x46
fffff880`0318d930 fffff800`02b4599e : fffffa80`030a63f8 fffff880`00000001 00000000`00000001 fffff880`0318dbb0 : nt! ?? ::FNODOBFM::`string'+0x21806
fffff880`0318dae0 fffff800`02ad7de2 : 00000000`00006ac1 00000000`00000000 fffffa80`00000000 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x49716
fffff880`0318db80 fffff800`02ad806f : 00000000`00000008 fffff880`0318dc10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`0318dbd0 fffff800`02d68a86 : fffffa80`01908b60 00000000`00000080 fffffa80`0184fb30 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`0318dd40 fffff800`02aa1b06 : fffff800`02c3de80 fffffa80`01908b60 fffff800`02c4bc40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0318dd80 00000000`00000000 : fffff880`0318e000 fffff880`03188000 fffff880`0318d830 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiFindNodeOrParent+0
fffff800`02b05410 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiFindNodeOrParent+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0

BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0

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

I will look further and be right back. Refresh you page in about 15 minutes. I will edit this post.

Okey!, So time to put som serious memtesting time then?

CarlTR6 said:

This is a BugCheck error A, IRQL_NOT_LESS_OR_EQUAL - BSOD Index. It is a hardware or hardware related error. The dump file blames memory corruption.

Code:

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Windows7_BSOD+perfmon report.zip\Windows7_BSOD_jcgriff2\080510-19656-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a53000 PsLoadedModuleList = 0xfffff800`02c90e50
Debug session time: Thu Aug  5 15:00:24.673 2010 (GMT-4)
System Uptime: 1 days 11:00:32.609
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
...........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {28, 2, 0, fffff80002b05410}

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

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

1: 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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002b05410, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfb0e0
 0000000000000028 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiFindNodeOrParent+0
fffff800`02b05410 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  iexplore.exe

TRAP_FRAME:  fffff8800318d5c0 -- (.trap 0xfffff8800318d5c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b05410 rsp=fffff8800318d758 rbp=0000000000000000
 r8=fffff8800318d7a0  r9=0000000000000000 r10=fffffa8003d2a0f0
r11=fffffa8003d04330 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiFindNodeOrParent:
fffff800`02b05410 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h ds:0488:00000000`00000028=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ac2b69 to fffff80002ac3600

STACK_TEXT:  
fffff880`0318d478 fffff800`02ac2b69 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0318d480 fffff800`02ac17e0 : fffffa80`03f15000 fffffa80`03d2a138 00000000`0000000e fffff880`0492fbb6 : nt!KiBugCheckDispatch+0x69
fffff880`0318d5c0 fffff800`02b05410 : fffff800`02b09197 fffff880`009e9180 00000000`00000002 00000000`00000001 : nt!KiPageFault+0x260
fffff880`0318d758 fffff800`02b09197 : fffff880`009e9180 00000000`00000002 00000000`00000001 fffff700`01080488 : nt!MiFindNodeOrParent
fffff880`0318d760 fffff800`02b0911d : 00000000`63416d4d 00000000`00000002 00000000`00000000 00000000`00001000 : nt!MiLocateAddressInTree+0x17
fffff880`0318d790 fffff800`02b09228 : 00000000`00000000 fffffa80`0232b000 fffffa80`0192cb28 fffffa80`03d2a1a8 : nt!MiGetSharedProtosAtDpcLevel+0xbd
fffff880`0318d7e0 fffff800`02a6119b : fffff800`02c39c18 fffff800`02ad6b90 fffff880`0318d8d8 fffff880`009e9180 : nt!MiGetSharedProtos+0x18
fffff880`0318d810 fffff800`02bc97d0 : e3700000`74974c46 fffffa80`03d2a130 fffff880`009e9180 fffff800`02ad1621 : nt! ?? ::FNODOBFM::`string'+0x927b
fffff880`0318d840 fffff800`02bc99b0 : fffffa80`030a6060 00000003`00000000 fffffa80`03d2a0f0 fffffa80`03d2a1a8 : nt!MiEmptyPageAccessLog+0x160
fffff880`0318d8b0 fffff800`02bc9bb6 : fffffa80`0192c000 00000000`0000089b fffff680`003afc28 00000000`00000000 : nt!MiAllocateAccessLog+0x80
fffff880`0318d8e0 fffff800`02b2b568 : 00000003`00000000 09b00000`7a742025 00000000`00000000 00000000`0000089b : nt!MiLogPageAccess+0x46
fffff880`0318d930 fffff800`02b4599e : fffffa80`030a63f8 fffff880`00000001 00000000`00000001 fffff880`0318dbb0 : nt! ?? ::FNODOBFM::`string'+0x21806
fffff880`0318dae0 fffff800`02ad7de2 : 00000000`00006ac1 00000000`00000000 fffffa80`00000000 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x49716
fffff880`0318db80 fffff800`02ad806f : 00000000`00000008 fffff880`0318dc10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`0318dbd0 fffff800`02d68a86 : fffffa80`01908b60 00000000`00000080 fffffa80`0184fb30 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`0318dd40 fffff800`02aa1b06 : fffff800`02c3de80 fffffa80`01908b60 fffff800`02c4bc40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0318dd80 00000000`00000000 : fffff880`0318e000 fffff880`03188000 fffff880`0318d830 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiFindNodeOrParent+0
fffff800`02b05410 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiFindNodeOrParent+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0

BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0

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

I find a couple drivers on your system that are slightly out of date.

L1E62x64.sys Thu Jun 11 02:45:22 2009 - Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (NDIS6.20) OEM - none at Atheros, Wireless LAN, WLAN, 2.4/5-GHz, 802.11a/b/g, 802.11b/g, 802.11n, Radio-on-a-Chip, Overview, Networking, Products and Technology

netr7364.sys Thu Mar 12 23:13:08 2009 - Ralink 802.11 USB Wireless Adapter Driver. Ralink corp.

See if you can update these two drivers. If not, you might want to consider upgrading LAN and wireless cards.

You mentioned that you have reinstalled Windows several times and still keep getting errors. This indicates a hardware problem rather than an OS problem.

You also said you have run Memtest and dropped down from 4 Megs to 2 Megs. I gather Memtest found some bad RAM? Did you test your RAM slots? Did you run Memtest 86+ which is the newest version? How many passes did you run? I suggest that you rerun it on the RAM you have on board and let it run for at least seven passes.

RAM - Test with Memtest86+

I also recommend that you run Prime95 to test your CPU.

https://www.sevenforums.com/tutorials...t-prime95.html

Post back with the results after you have completed these tests.

i just started memtest and have tried the first slot and stick so im not done with that yet. And yes i run memtest86+ 7-8 passes

The bsod came after every format and all devices installed.. i dont recall having a BSOD after clean install.. My thinking is that the USB wireless Dlink device is faling..
I hade som difficulties with it.. Sometimes when i pull out the usb ore change the place of the usb stick to another usb slot.. the device stops working..

I will do the memtest.. update the drivers.. and try to use a Cable from my router instead.. Then i will post back!

Thank you!

Hi!


I updated the Aeros driver the lastest from mars 2010.

ABout the ( netr7364.sys Thu Mar 12 23:13:08 2009 - Ralink 802.11 USB Wireless Adapter Driver) I didnt find the netr7364.sys driver in my system, or where to find it in the device maneger. but i downloaded the lastest update anyhow and installed it.

I also run memtest for 8 passes without problems detected.

Im now running prime95 and have been doing so for about 4hours without problems.

Temperature on CPU went up after a while to 54. (AMD phenom 8450 tripple core 2.1)
using speedfan for mesure.

I havent yet unpluged the D-link wireless adapter, i want to try the new driver.

When i think back.. it was always iexplorer or chrome.exe that stod for the most BSOD.. in otherwords. When i was getting internet traffic.. And the dlink adapter is
the lastest hardware that i have installed.