TechSpot

Constant Blue Screens and Lockups

By Wildtechdog
Jan 15, 2010
  1. Hello, I'm having difficulty reading the minidump i ran through the windows debug tools. I've been getting lock ups and blue screen crashes as well as random restarts. I've tested the memory with +86 Memtest and even used WinMem test to run windows instructions on the memory, all come back good. PSU is a 600w supply so its not under powered. Here is the converted dump.


    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: d0860020, 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: 80513ad4, address which referenced memory

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


    WRITE_ADDRESS: d0860020

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!MiAddViewsForSection+2c
    80513ad4 897a04 mov dword ptr [edx+4],edi

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from 80518784 to 80513ad4

    STACK_TEXT:
    f7a53b74 80518784 86001c79 0001a3c0 3ed07800 nt!MiAddViewsForSection+0x2c
    f7a53bb0 804e75e1 e1127608 86db7d10 0001a380 nt!MmMapViewInSystemCache+0x12e
    f7a53c3c 804e7864 8604e578 2b390000 00000000 nt!CcGetVacbMiss+0x283
    f7a53c74 804e0f7a 0004e578 2b390000 00000000 nt!CcGetVirtualAddress+0x94
    f7a53d2c 804e61eb 86dc4288 8055a440 86dc58b8 nt!CcPerformReadAhead+0x194
    f7a53d74 80534006 86dc4288 00000000 86dc58b8 nt!CcWorkerThread+0x147
    f7a53dac 805c4d5c 86dc4288 00000000 00000000 nt!ExpWorkerThread+0x100
    f7a53ddc 805411e2 80533f06 00000000 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiAddViewsForSection+2c
    80513ad4 897a04 mov dword ptr [edx+4],edi

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!MiAddViewsForSection+2c

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a7833f0

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0xA_nt!MiAddViewsForSection+2c

    BUCKET_ID: 0xA_nt!MiAddViewsForSection+2c

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

    eax=f7a53b00 ebx=86001c79 ecx=00000000 edx=d086001c esi=86001c79 edi=0086001c
    eip=80513ad4 esp=f7a53b68 ebp=f7a53b74 iopl=0 nv up ei ng nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
    nt!MiAddViewsForSection+0x2c:
    80513ad4 897a04 mov dword ptr [edx+4],edi ds:0023:d0860020=????????
    ChildEBP RetAddr Args to Child
    f7a53b74 80518784 86001c79 0001a3c0 3ed07800 nt!MiAddViewsForSection+0x2c (FPO: [4,0,4])
    f7a53bb0 804e75e1 e1127608 86db7d10 0001a380 nt!MmMapViewInSystemCache+0x12e (FPO: [4,6,0])
    f7a53c3c 804e7864 8604e578 2b390000 00000000 nt!CcGetVacbMiss+0x283 (FPO: [Non-Fpo])
    f7a53c74 804e0f7a 0004e578 2b390000 00000000 nt!CcGetVirtualAddress+0x94 (FPO: [5,5,4])
    f7a53d2c 804e61eb 86dc4288 8055a440 86dc58b8 nt!CcPerformReadAhead+0x194 (FPO: [Non-Fpo])
    f7a53d74 80534006 86dc4288 00000000 86dc58b8 nt!CcWorkerThread+0x147 (FPO: [Non-Fpo])
    f7a53dac 805c4d5c 86dc4288 00000000 00000000 nt!ExpWorkerThread+0x100 (FPO: [1,8,0])
    f7a53ddc 805411e2 80533f06 00000000 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo])
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

    Unloaded modules:
    f7c94000 f7c95000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ac2ae000 ac2d1000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ac4c6000 ac4d3000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ac4d6000 ac4e4000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7bb6000 f7bb8000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f77ec000 f77f5000 processr.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7aac000 f7ab0000 kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f778c000 f7799000 i8042prt.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7934000 f7939000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7300000 f7303000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ^ Syntax error in '.reload;!analyze -v;r;kv;lmnt;logclose;q'
     

    Attached Files:

  2. raybay

    raybay TS Evangelist Posts: 10,716   +6

    With all that information, you still did not tell us the brand and model, age, configuration including memory, hard drive, cables, and other input devices.
     
  3. Route44

    Route44 TechSpot Ambassador Posts: 12,166   +37

    Your first error is 0x50: PAGE_FAULT_IN_NONPAGED_AREA
    Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).

    Though it did not give a specific cause it did mention hardware.


    The second error is 0xA and the definition they gave you as to the cause is certainly correct. But 0xA errors can also result due to hardware issues and this minidump specifically cited memory corruption as the cause of your problems. Notice that in the 0x50 definition that defective memory is part of the equation.

    In fact, in what you posted this is contrained in the file read-out: IMAGE_NAME: memory_corruption

    Memtest needs to run a minimumu of 7 Passes (there are 8 individual tests per Pass) and the more the better. It may look like that once it cycles through it just repeats itself but it isn't all. it is throwing different patterns at your memory.

    How many passes did you run Memtest? Also, check the voltag setting of your memory in your BIOS and see if it matches the parameters that your memory manufacturer designed it for.

    *** Plus what raybay wrote. This information is important.
     
  4. Wildtechdog

    Wildtechdog TS Rookie Topic Starter

    Its running with 6 full passes, i'll run it at a full 9 passes just to be sure
    Both sticks are 1GB Kingston DDR2, running on a Asus board (don't remember model) with a AMD Athlon 64 3200+ with XP Pro SP2 (would rather shoot my foot than use SP3. Plus a Radeon X800 PCI-E card
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.