Outline ·
[ Standard ] ·
Linear+
[FAQ] PC auto restart/Blue Screen (BSOD), All questions go here please.
|
spikeee
|
 May 26 2008, 12:19 AM
|
|
QUOTE(derick0525 @ May 24 2008, 12:09 PM) i have the blue screen problem too when i playing warcraft ( dota ) .. half game will appear blue screen then restart then i mute inside the warcraft sound it wont happen the blue screen again how to solve this ? then it sounds like a driver issue. please collect your minidump file and send it to my email. QUOTE(serenayap @ May 24 2008, 04:40 PM) hi can anyone please help me with this problem.. my computer like to go into sleep mode( i think so only no so sure also) one in a while when i leave it there for few hours. after that the whole computer just hang no matter how i try to wake it. even i press the restart button it wont work.. and i hav to switch off the main power to restart it.. i am using vista currently.. can anyone help me please,. can you check your power settings to see whether you have it set to go into sleep mode after a certain amount of idle time? how long since u last formatted your computer? QUOTE(ijulkusa @ May 25 2008, 09:05 PM) my notebook compaq. i have problem when windows standby.after standby i log on, blue screen appear and then restart... help me.. this my minidumb  haha bro, it's miniDUMP  hehe anyway please send it to my email joel@genesis-solutions.org |
|
|
|
|
|
spikeee
|
May 28 2008, 11:26 AM
|
|
|
I'm thinking that she might need a seperate thread. No BSOD issues
|
|
|
|
|
|
spikeee
|
May 31 2008, 12:25 PM
|
|
|
Stop error 0x0000000A (Stop 0x0A) indicates that there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL). Typically, this error occurs when a driver uses an incorrect memory address. Other possible causes of this error are an incompatible device driver, a general hardware problem, and incompatible software
We will need to know what driver is involved in this incorrect use of memory address.
|
|
|
|
|
|
spikeee
|
Jun 16 2008, 10:21 AM
|
|
|
Thanks Eccletice. I try to help out whenever i can, but times are short/bad |
|
|
|
|
|
spikeee
|
Jun 17 2008, 08:01 PM
|
|
|
a minidump (as replied by pm) is generally a log of the cause of the BSOD
|
|
|
|
|
|
spikeee
|
Jun 19 2008, 04:16 PM
|
|
|
QUOTE(Grand Inquisitor @ Jun 17 2008, 10:21 PM) Latest version of K-Lite Codec Pack. You need to post your minidump before we can analyze QUOTE(-vip3rleon9- @ Jun 18 2008, 11:44 PM) Help required, sifu's. I simply cannot go online. In my Network Connections, it says that I am connected to my LAN network and my router has already provided my PC with the required details (IP address etc). However, my BSOD only appears whenever I try to launch/access anything that is related to the internet. When I lauch IE, it will launch and I will be able to surf as usual. However, after a few minutes, the BSOD happens and my PC will automatically restart, even after I have unchecked the "Automatically Restart" checkbox in the "System Failure" under "Startup and Recovery". Same goes for Windows Live Messenger. As such, I am unable to find out what the cause of my BSOD is, and I am also thus unable to pinpoint my stop error "code".  As I am only encountering this problem after I bought my new hardware, I suspect it's the driver's that's faulty. However, would anyone be kind enough to help me go through my minidump files and let me know what exactly is casuing this BSOD? Help of any sort would be deeply appreciated. Unchecking 'Automatically Restart' is to prevent you from seeing a BSOD. With that unchecked your BSOD will happen in a flash and thus you will not be able to see the error code etc As per usual, the attachments in this thread seem to be corrupted. Please send your minidump to my email joelwong@patimas.com please tell me ur name and ur nickname |
|
|
|
|
|
spikeee
|
Jun 20 2008, 06:43 PM
|
|
|
QUOTE(vobboblogs @ Jun 19 2008, 07:04 PM) help please....suddenly happen... [attachmentid=502687] I wish less people would come in here just wanting answers and not bothering to read at least some threads before urs. you would notice i have asked for the minidumps to be sent to my email until the issue in the forum is fixed QUOTE(Grand Inquisitor @ Jun 19 2008, 08:21 PM) How to make minidump? no one reply me? You get it at c:\windows\minidump take the latest one and please don't expect people to reply you as though we're working here full time. thank you. QUOTE(dattebayo @ Jun 20 2008, 01:23 AM) hi everyone, can you help me to analyze the Windows Debugger dump analysis? It's very long, try my best in copying all of them here summary: 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. » Click to show Spoiler - click again to hide... « CODE
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\SCW\Desktop\Mini062008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Kernel base = 0x8204e000 PsLoadedModuleList = 0x82165c70
Debug session time: Fri Jun 20 00:40:45.930 2008 (GMT+8)
System Uptime: 0 days 5:53:12.345
Loading Kernel Symbols
..............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 1b, 0, 82101cba}
Probably caused by : ntkrpamp.exe ( nt!KiUnwaitThread+14 )
Followup: MachineOwner
---------
0: kd> .reload
Loading Kernel Symbols
..............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
0: kd> .reload
Loading Kernel Symbols
..............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
0: 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: 00000000, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000000, 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: 82101cba, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82185868
Unable to read MiSystemVaType memory at 82165420
00000000
CURRENT_IRQL: 1b
FAULTING_IP:
nt!KiUnwaitThread+14
82101cba 8b08 mov ecx,dword ptr [eax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: explorer.exe
TRAP_FRAME: 8039dd8c -- (.trap 0xffffffff8039dd8c)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=85fcbc78 edx=85fcbc78 esi=86119b70 edi=861c8f70
eip=82101cba esp=8039de00 ebp=8039de14 iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213
nt!KiUnwaitThread+0x14:
82101cba 8b08 mov ecx,dword ptr [eax] ds:0023:00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 82101cba to 820a8d84
STACK_TEXT:
8039dd8c 82101cba badb0d00 85fcbc78 0000000f nt!KiTrap0E+0x2ac
8039de14 82104a0b 00000000 8214ace0 00000016 nt!KiUnwaitThread+0x14
8039df28 821048c0 8039df70 82146902 8039df78 nt!KiTimerListExpire+0x76
8039df88 82104483 00000000 00000000 0014b216 nt!KiTimerExpiration+0x22a
8039dff4 821029f5 959614b8 00000000 00000000 nt!KiRetireDpcList+0xba
8039dff8 959614b8 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
WARNING: Frame IP not in any known module. Following frames may be wrong.
821029f5 00000000 0000001b 00c7850f bb830000 0x959614b8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiUnwaitThread+14
82101cba 8b08 mov ecx,dword ptr [eax]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiUnwaitThread+14
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12
FAILURE_BUCKET_ID: 0xA_nt!KiUnwaitThread+14
BUCKET_ID: 0xA_nt!KiUnwaitThread+14
Followup: MachineOwner
---------
0: 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: 00000000, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000000, 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: 82101cba, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82185868
Unable to read MiSystemVaType memory at 82165420
00000000
CURRENT_IRQL: 1b
FAULTING_IP:
nt!KiUnwaitThread+14
82101cba 8b08 mov ecx,dword ptr [eax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: explorer.exe
TRAP_FRAME: 8039dd8c -- (.trap 0xffffffff8039dd8c)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=85fcbc78 edx=85fcbc78 esi=86119b70 edi=861c8f70
eip=82101cba esp=8039de00 ebp=8039de14 iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213
nt!KiUnwaitThread+0x14:
82101cba 8b08 mov ecx,dword ptr [eax] ds:0023:00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 82101cba to 820a8d84
STACK_TEXT:
8039dd8c 82101cba badb0d00 85fcbc78 0000000f nt!KiTrap0E+0x2ac
8039de14 82104a0b 00000000 8214ace0 00000016 nt!KiUnwaitThread+0x14
8039df28 821048c0 8039df70 82146902 8039df78 nt!KiTimerListExpire+0x76
8039df88 82104483 00000000 00000000 0014b216 nt!KiTimerExpiration+0x22a
8039dff4 821029f5 959614b8 00000000 00000000 nt!KiRetireDpcList+0xba
8039dff8 959614b8 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
WARNING: Frame IP not in any known module. Following frames may be wrong.
821029f5 00000000 0000001b 00c7850f bb830000 0x959614b8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiUnwaitThread+14
82101cba 8b08 mov ecx,dword ptr [eax]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiUnwaitThread+14
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12
FAILURE_BUCKET_ID: 0xA_nt!KiUnwaitThread+14
BUCKET_ID: 0xA_nt!KiUnwaitThread+14
Followup: MachineOwner
---------
0: 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: 00000000, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000000, 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: 82101cba, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82185868
Unable to read MiSystemVaType memory at 82165420
00000000
CURRENT_IRQL: 1b
FAULTING_IP:
nt!KiUnwaitThread+14
82101cba 8b08 mov ecx,dword ptr [eax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: explorer.exe
TRAP_FRAME: 8039dd8c -- (.trap 0xffffffff8039dd8c)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=85fcbc78 edx=85fcbc78 esi=86119b70 edi=861c8f70
eip=82101cba esp=8039de00 ebp=8039de14 iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213
nt!KiUnwaitThread+0x14:
82101cba 8b08 mov ecx,dword ptr [eax] ds:0023:00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 82101cba to 820a8d84
STACK_TEXT:
8039dd8c 82101cba badb0d00 85fcbc78 0000000f nt!KiTrap0E+0x2ac
8039de14 82104a0b 00000000 8214ace0 00000016 nt!KiUnwaitThread+0x14
8039df28 821048c0 8039df70 82146902 8039df78 nt!KiTimerListExpire+0x76
8039df88 82104483 00000000 00000000 0014b216 nt!KiTimerExpiration+0x22a
8039dff4 821029f5 959614b8 00000000 00000000 nt!KiRetireDpcList+0xba
8039dff8 959614b8 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
WARNING: Frame IP not in any known module. Following frames may be wrong.
821029f5 00000000 0000001b 00c7850f bb830000 0x959614b8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiUnwaitThread+14
82101cba 8b08 mov ecx,dword ptr [eax]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiUnwaitThread+14
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12
FAILURE_BUCKET_ID: 0xA_nt!KiUnwaitThread+14
BUCKET_ID: 0xA_nt!KiUnwaitThread+14
Followup: MachineOwner
---------
 Hi there, your issue is with the kernel exectubale ntkrpamp and as a result it could be almost ANYTHING from your OS patches to an antivirus lacking the latest updates. Let's see what we can make of this! Can you download memtest86 (google it) and run the ram memory tester to see if your ram has issues |
|
|
|
|
Quote
0.3313sec
0.48
7 queries
GZIP Disabled