Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Windows 7


09 Feb 2011   #1

windows 7 professional 32 bit
 
 
BSOD Windows 7

Windows 7 Professional
- x86 (32-bit)
- the original installed OS on the system? original
- an OEM or full retail version? full
- What is the age of system (hardware)? 3-4 years
- What is the age of OS installation? 3 weeks
-Computer emachines T5082 all original except i have upgraded the memory from 512 GB to 2 GB

The problem i am having i keep getting the BSOD after running programs like itunes especially when i am trying to import songs off a cd, the usual reason it gives me is IQRL NOT LESS OR EQUAL or PFN LIST CORRUPT


My System SpecsSystem Spec
.

09 Feb 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by lilbigklick View Post
Windows 7 Professional
- x86 (32-bit)
- the original installed OS on the system? original
- an OEM or full retail version? full
- What is the age of system (hardware)? 3-4 years
- What is the age of OS installation? 3 weeks
-Computer emachines T5082 all original except i have upgraded the memory from 512 GB to 2 GB

The problem i am having i keep getting the BSOD after running programs like itunes especially when i am trying to import songs off a cd, the usual reason it gives me is IQRL NOT LESS OR EQUAL or PFN LIST CORRUPT
You have 4 different types od crashes. all point to hardware and I suspect that hardware is memory. It looks like the memory started giving your grief around Jan 21 and since then has been memory management and PFN.

I would
1- run memtest

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.


2-Remove AVG and replace with Microsoft security essentials. Seems like you have both installed


http://www.avg.com/us-en/download-tools

http://www.microsoft.com/security_essentials/

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\020811-36265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8283a000 PsLoadedModuleList = 0x82982810
Debug session time: Tue Feb  8 17:53:14.629 2011 (GMT-5)
System Uptime: 2 days 0:06:07.536
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {837fffe4, 2, 1, 828cdbee}

Probably caused by : memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+238 )

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: 837fffe4, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 828cdbee, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829a2718
Unable to read MiSystemVaType memory at 82982160
 837fffe4 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiInsertPageInFreeOrZeroedList+238
828cdbee 8901            mov     dword ptr [ecx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  MsMpEng.exe

TRAP_FRAME:  8e09b6f4 -- (.trap 0xffffffff8e09b6f4)
ErrCode = 00000002
eax=0000056c ebx=0000001c ecx=837fffe4 edx=00000000 esi=838097d0 edi=8451ec70
eip=828cdbee esp=8e09b768 ebp=8e09b790 iopl=0         nv up ei ng nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
nt!MiInsertPageInFreeOrZeroedList+0x238:
828cdbee 8901            mov     dword ptr [ecx],eax  ds:0023:837fffe4=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828cdbee to 8288082b

STACK_TEXT:  
8e09b6f4 828cdbee badb0d00 00000000 00000000 nt!KiTrap0E+0x2cf
8e09b790 828ca30e 00061031 838097d0 c0044ee0 nt!MiInsertPageInFreeOrZeroedList+0x238
8e09b7d0 82866a6d c0600228 c0045000 863a2730 nt!MiPfnShareCountIsZero+0x18c
8e09b81c 8286646e 85ecc2a8 00000200 00000000 nt!MiDeletePteList+0x23c
8e09bc84 828ee0ba c0045140 85ecc2a8 b6f3e220 nt!MiDecommitPages+0xef
8e09bd1c 8287d44a ffffffff 0166f09c 0166f0b0 nt!NtFreeVirtualMemory+0x882
8e09bd1c 777964f4 ffffffff 0166f09c 0166f0b0 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0166f070 00000000 00000000 00000000 00000000 0x777964f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiInsertPageInFreeOrZeroedList+238
828cdbee 8901            mov     dword ptr [ecx],eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiInsertPageInFreeOrZeroedList+238

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiInsertPageInFreeOrZeroedList+238

BUCKET_ID:  0xA_nt!MiInsertPageInFreeOrZeroedList+238

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: 837fffe4, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 828cdbee, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829a2718
Unable to read MiSystemVaType memory at 82982160
 837fffe4 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiInsertPageInFreeOrZeroedList+238
828cdbee 8901            mov     dword ptr [ecx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  MsMpEng.exe

TRAP_FRAME:  8e09b6f4 -- (.trap 0xffffffff8e09b6f4)
ErrCode = 00000002
eax=0000056c ebx=0000001c ecx=837fffe4 edx=00000000 esi=838097d0 edi=8451ec70
eip=828cdbee esp=8e09b768 ebp=8e09b790 iopl=0         nv up ei ng nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
nt!MiInsertPageInFreeOrZeroedList+0x238:
828cdbee 8901            mov     dword ptr [ecx],eax  ds:0023:837fffe4=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828cdbee to 8288082b

STACK_TEXT:  
8e09b6f4 828cdbee badb0d00 00000000 00000000 nt!KiTrap0E+0x2cf
8e09b790 828ca30e 00061031 838097d0 c0044ee0 nt!MiInsertPageInFreeOrZeroedList+0x238
8e09b7d0 82866a6d c0600228 c0045000 863a2730 nt!MiPfnShareCountIsZero+0x18c
8e09b81c 8286646e 85ecc2a8 00000200 00000000 nt!MiDeletePteList+0x23c
8e09bc84 828ee0ba c0045140 85ecc2a8 b6f3e220 nt!MiDecommitPages+0xef
8e09bd1c 8287d44a ffffffff 0166f09c 0166f0b0 nt!NtFreeVirtualMemory+0x882
8e09bd1c 777964f4 ffffffff 0166f09c 0166f0b0 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0166f070 00000000 00000000 00000000 00000000 0x777964f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiInsertPageInFreeOrZeroedList+238
828cdbee 8901            mov     dword ptr [ecx],eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiInsertPageInFreeOrZeroedList+238

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiInsertPageInFreeOrZeroedList+238

BUCKET_ID:  0xA_nt!MiInsertPageInFreeOrZeroedList+238

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: 837fffe4, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 828cdbee, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829a2718
Unable to read MiSystemVaType memory at 82982160
 837fffe4 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiInsertPageInFreeOrZeroedList+238
828cdbee 8901            mov     dword ptr [ecx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  MsMpEng.exe

TRAP_FRAME:  8e09b6f4 -- (.trap 0xffffffff8e09b6f4)
ErrCode = 00000002
eax=0000056c ebx=0000001c ecx=837fffe4 edx=00000000 esi=838097d0 edi=8451ec70
eip=828cdbee esp=8e09b768 ebp=8e09b790 iopl=0         nv up ei ng nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
nt!MiInsertPageInFreeOrZeroedList+0x238:
828cdbee 8901            mov     dword ptr [ecx],eax  ds:0023:837fffe4=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828cdbee to 8288082b

STACK_TEXT:  
8e09b6f4 828cdbee badb0d00 00000000 00000000 nt!KiTrap0E+0x2cf
8e09b790 828ca30e 00061031 838097d0 c0044ee0 nt!MiInsertPageInFreeOrZeroedList+0x238
8e09b7d0 82866a6d c0600228 c0045000 863a2730 nt!MiPfnShareCountIsZero+0x18c
8e09b81c 8286646e 85ecc2a8 00000200 00000000 nt!MiDeletePteList+0x23c
8e09bc84 828ee0ba c0045140 85ecc2a8 b6f3e220 nt!MiDecommitPages+0xef
8e09bd1c 8287d44a ffffffff 0166f09c 0166f0b0 nt!NtFreeVirtualMemory+0x882
8e09bd1c 777964f4 ffffffff 0166f09c 0166f0b0 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0166f070 00000000 00000000 00000000 00000000 0x777964f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiInsertPageInFreeOrZeroedList+238
828cdbee 8901            mov     dword ptr [ecx],eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiInsertPageInFreeOrZeroedList+238

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiInsertPageInFreeOrZeroedList+238

BUCKET_ID:  0xA_nt!MiInsertPageInFreeOrZeroedList+238

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: 837fffe4, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 828cdbee, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829a2718
Unable to read MiSystemVaType memory at 82982160
 837fffe4 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiInsertPageInFreeOrZeroedList+238
828cdbee 8901            mov     dword ptr [ecx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  MsMpEng.exe

TRAP_FRAME:  8e09b6f4 -- (.trap 0xffffffff8e09b6f4)
ErrCode = 00000002
eax=0000056c ebx=0000001c ecx=837fffe4 edx=00000000 esi=838097d0 edi=8451ec70
eip=828cdbee esp=8e09b768 ebp=8e09b790 iopl=0         nv up ei ng nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
nt!MiInsertPageInFreeOrZeroedList+0x238:
828cdbee 8901            mov     dword ptr [ecx],eax  ds:0023:837fffe4=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828cdbee to 8288082b

STACK_TEXT:  
8e09b6f4 828cdbee badb0d00 00000000 00000000 nt!KiTrap0E+0x2cf
8e09b790 828ca30e 00061031 838097d0 c0044ee0 nt!MiInsertPageInFreeOrZeroedList+0x238
8e09b7d0 82866a6d c0600228 c0045000 863a2730 nt!MiPfnShareCountIsZero+0x18c
8e09b81c 8286646e 85ecc2a8 00000200 00000000 nt!MiDeletePteList+0x23c
8e09bc84 828ee0ba c0045140 85ecc2a8 b6f3e220 nt!MiDecommitPages+0xef
8e09bd1c 8287d44a ffffffff 0166f09c 0166f0b0 nt!NtFreeVirtualMemory+0x882
8e09bd1c 777964f4 ffffffff 0166f09c 0166f0b0 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0166f070 00000000 00000000 00000000 00000000 0x777964f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiInsertPageInFreeOrZeroedList+238
828cdbee 8901            mov     dword ptr [ecx],eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiInsertPageInFreeOrZeroedList+238

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiInsertPageInFreeOrZeroedList+238

BUCKET_ID:  0xA_nt!MiInsertPageInFreeOrZeroedList+238

Followup: MachineOwner
---------
My System SpecsSystem Spec
Reply

 BSOD Windows 7




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 11:24 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33