also @ TechSpot: Apple iOS 'Absinthe' jailbreak: 1 million downloads and counting

TechSpot

Minidump Logs

Discussion in 'Windows BSOD, Freezing, Restarting Help' started by Heaney, Sep 3, 2006.

Thread Status:
Not open for further replies.
  1. Heaney Newcomer, in training

    Please review my minidumps.
  2. N3051M Newcomer, in training

    mini081706-01.dmp:
    Code:
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    ...
    
    mini082706-01.dmp
    Code:
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    ...
    
    mini090206-01.dmp
    Code:
    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    ...
    mini090206-02.dmp
    Code:
    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    ...
    
    mini090206-03.dmp
    Code:
    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.
    Attatched is the log files. Suggest checking your drivers are up to date and correct for each device, or changing the slot on the mobo/changing bios settings etc.

    Can someone double check my logs to see if its correct? (think they should be..)
Thread Status:
Not open for further replies.