also @ TechSpot: HP TouchPad running Android 4.0 Ice Cream Sandwich
Welcome to the TechSpot OpenBoards. Please read the FAQ if you have any questions. Sign up or Login to participate.

Go Back   TechSpot OpenBoards > Tech Support > Windows BSOD, Freezing, Restarting Help

Begin your free trial now Pay-as-you-go options starting at $10/user/month

Minidump Logs

Thread Tools Search this Thread
  #1  
Old 09-03-2006
Newcomer, in training
 
Member since: Sep 2006, 1 posts
Minidump Logs

Please review my minidumps.
Attached Files
File Type: dmp Mini090206-03.dmp (100.0 KB, 3 views)
File Type: dmp Mini090206-02.dmp (100.0 KB, 2 views)
File Type: dmp Mini090206-01.dmp (92.0 KB, 3 views)
File Type: dmp Mini082706-01.dmp (92.0 KB, 2 views)
File Type: dmp Mini081706-01.dmp (92.0 KB, 2 views)
  #2  
Old 09-04-2006
N3051M's Avatar
TechSpot Evangelist
 
Location: Sydney, Australia
Member since: Jan 2006, 2,800 posts
System specs
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..)
Attached Files
File Type: txt mini081706-01.txt (20.3 KB, 2 views)
File Type: txt mini082706-01.txt (14.8 KB, 2 views)
File Type: txt mini090206-01.txt (23.2 KB, 1 views)
File Type: txt mini090206-02.txt (23.9 KB, 1 views)
File Type: txt mini090206-03.txt (16.1 KB, 1 views)
Closed Thread

Similar Topics
Topic Replies Forum
Minidump Help Please 3 Windows BSOD, Freezing, Restarting Help
Minidump 1 Windows BSOD, Freezing, Restarting Help
Minidump help please 5 Windows BSOD, Freezing, Restarting Help
HJT logs, of HJT, AVG anti spyware, combo fix logs as Mr Howards 4 Virus and Malware Removal
serious hardlock problems (minidump logs included) 2 Device Drivers

Thread Tools Search this Thread
Search this Thread:

Advanced Search
All times are GMT -4. The time now is 09:42 PM.