What's new

PLEASE HELP | BSOD

Status
Not open for further replies.

Tiger

Donator
Joined
Jan 25, 2011
Messages
5,283
Location
UK
Hello,
As I'm in a place for around a month where there is no WiFi but only a mobile modem device I have to connect using that. However when connect to it using the software or without after 5 seconds I get the Blue Screen of Death with either the error "BAD_POOL_CALLER" or "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED".
This is the modem make:
HUAWEI Mobile Connect E173

I also tired it with two different dongles of the same make and different SIM cards.
I need help ASAP or I won't be able to play. Posting this from an old, slow PC>
 

LemonPower

Retired Admin
Joined
Jul 27, 2011
Messages
3,360
Tiger said:
Thomasplaysgames123 said:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff560185(v=vs.85).aspx
What?


Bug Check 0xC2: BAD_POOL_CALLER

The BAD_POOL_CALLER bug check has a value of 0x000000C2. This indicates that the current thread is making a bad pool request.



If you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss.

For information about how to recover from this error, see Resolving Blue Screen errors in Windows.

[th]Parameter 1[/th]
[th]Parameter 2[/th]
[th]Parameter 3[/th]
[th]Parameter 4[/th]
[th]Cause of Error[/th]













































































































0x00 0x00 0x00 Pool tag The current thread requested a zero-byte pool allocation.
0x01,
0x02,
0x04
Pointer to pool header First part of pool header contents 0 The pool header has been corrupted.
0x06 Reserved Pointer to pool header Pool header contents The current thread attempted to free the pool, which was already freed.
0x07 Reserved Pool header contents Address of the block of pool being freed The current thread attempted to free the pool, which was already freed.
0x08 Current IRQL Pool type Size of allocation, in bytes The current thread attempted to allocate the pool at an invalid IRQL.
0x09 Current IRQL Pool type Address of pool The current thread attempted to free the pool at an invalid IRQL.
0x0A Address of pool Allocator's tag Tag being used in the attempted free The current thread attempted to free pool memory by using the wrong tag.
(The memory might belong to another component.)
0x0B,
0x0C,
or 0x0D
Address of pool Pool allocation's tag Bad quota process pointer The current thread attempted to release a quota on a corrupted pool allocation.
0x40 Starting address Start of system address space 0 Start of system address space
0x41 Starting address Physical page frame Highest physical page frame The current thread attempted to free a non-allocated nonpaged pool address.
0x42
or 0x43
Address being freed 0 0 The current thread attempted to free a virtual address that was never in any pool.
0x44 Starting address Reserved 0 The current threat attempted to free a non-allocated nonpaged pool address
0x47 Starting address Physical page frame highest physical page frame The current threat attempted to free a non-allocated nonpaged pool address
0x48 Starting address Reserved Reserved The current threat attempted to free a non-allocated nonpaged pool address
0x50 Starting address Start offset, in pages, from beginning of paged pool Size of paged pool, in bytes The current threat attempted to free a non-allocated nonpaged pool address
0x60 Starting address 0 0 The current thread attempted to free an invalid contiguous memory address.
(The caller of MmFreeContiguousMemory is passing a bad pointer.)
0x99 Address that is being freed 0 0 The current thread attempted to free pool with an invalid address.
(This code can also indicate corruption in the pool header.)
0x9A Pool type Number of bytes requested Pool tag The current thread marked an allocation request MUST_SUCCEED.
(This pool type is no longer supported.)
0x9B Pool type Number of bytes requested Caller's address The current thread attempted to allocate a pool with a tag of 0
(This would be untrackable, and possibly corrupt the existing tag tables.)
0x9C Pool type Number of bytes requested Caller's address The current thread attempted to allocate a pool with a tag of "BIG".
(This would be untrackable and could possibly corrupt the existing tag tables.)
0x9D Incorrect pool tag used Pool type Caller's address The current thread attempted to allocate a pool with a tag that does not contain any letters or digits. Using such tags makes tracking pool issues difficult.
0x41286 Reserved Reserved Start offset from the beginning of the paged pool, in pages The current thread attempted to free a paged pool address in the middle of an allocation.





The _POOL_TYPE codes are enumerated in Ntddk.h. In particular, 0 indicates nonpaged pool and 1 indicates paged pool.


Cause
An invalid pool request has been made by the current thread.


Resolution
Activate Driver Verifier to obtain more information about these errors. For details, see the Driver Verifier section of the Windows Driver Kit (WDK).
 

Tiger

Donator
Joined
Jan 25, 2011
Messages
5,283
Location
UK
Just fucked my lapop up using verifier.exe. Getting BSOD evert start up and error "irq_not_les_or_equal" or something like that, but currently using some emergency repair thing and if that doesn't work I will try a fix I found on the net, :bangin:\

EDIT: PHEWWWW it worked. Now lets see if it fixed the old BSOD.
 
Status
Not open for further replies.
Top