Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

New Laptop BSOD


  • Please log in to reply
3 replies to this topic

#1 n1nj4

n1nj4

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:07:19 AM

Posted 24 December 2010 - 07:54 AM

Hi there,

Got a bsod on my new acer 4820tg laptop running win7 x64.
It happened while i was using logmein through google chrome to remote control my desktop.
ran windows debugging tool on the 2 .dmp files.
Any info would be greatly appreciated... :D

Analysis for MEMORY.DMP ----->


Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a01000 PsLoadedModuleList = 0xfffff800`02c3ee50
Debug session time: Thu Dec 23 21:26:12.132 2010 (UTC - 5:00)
System Uptime: 0 days 0:39:15.272
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols

Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {100befbf0, 2, 1, fffff80002a7b3d3}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2b3 )

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: 0000000100befbf0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002a7b3d3, address which referenced memory

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


WRITE_ADDRESS: 0000000100befbf0

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiTimerWaitTest+2b3
fffff800`02a7b3d3 48894108 mov qword ptr [rcx+8],rax

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff800041f43d0 -- (.trap 0xfffff800041f43d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80002befb68 rbx=0000000000000000 rcx=0000000100befbe8
rdx=fffff80002befb68 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a7b3d3 rsp=fffff800041f4560 rbp=0000000100befbe8
r8=fffff80002bee001 r9=0000000000000004 r10=00000000000000c2
r11=fffff88002a1d010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!KiTimerWaitTest+0x2b3:
fffff800`02a7b3d3 48894108 mov qword ptr [rcx+8],rax ds:f3c0:fbf0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a70ca9 to fffff80002a71740

STACK_TEXT:
fffff800`041f4288 fffff800`02a70ca9 : 00000000`0000000a 00000001`00befbf0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`041f4290 fffff800`02a6f920 : 00000000`0000000a fffff800`02befb70 fffff800`40c40088 fffff800`02a7dde0 : nt!KiBugCheckDispatch+0x69
fffff800`041f43d0 fffff800`02a7b3d3 : 00000000`00000000 fffff800`02a7d29e fffff800`041f4618 00000000`00000001 : nt!KiPageFault+0x260
fffff800`041f4560 fffff800`02a7cd7d : fffff800`02befb68 00000000`00024dc1 00000000`00000000 00000000`00000000 : nt!KiTimerWaitTest+0x2b3
fffff800`041f45e0 fffff800`02a7d4be : 00000005`7bda12f6 fffff800`041f4c58 00000000`00024dc2 fffff800`02befac8 : nt!KiProcessExpiredTimerList+0x6d
fffff800`041f4c30 fffff800`02a7ccb7 : 00000001`6cc942c3 00000001`00024dc2 00000001`6cc942da 00000000`000000c2 : nt!KiTimerExpiration+0x1be
fffff800`041f4cd0 fffff800`02a79eea : fffff800`02bebe80 fffff800`02bf9c40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`041f4d80 00000000`00000000 : fffff800`041f5000 fffff800`041ef000 fffff800`041f4d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTimerWaitTest+2b3
fffff800`02a7b3d3 48894108 mov qword ptr [rcx+8],rax

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiTimerWaitTest+2b3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

FAILURE_BUCKET_ID: X64_0xA_nt!KiTimerWaitTest+2b3

BUCKET_ID: X64_0xA_nt!KiTimerWaitTest+2b3

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




Analysis for 122310-5850-01.dmp -------->



Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_07fe5ca0\122310-5850-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a01000 PsLoadedModuleList = 0xfffff800`02c3ee50
Debug session time: Thu Dec 23 21:26:12.132 2010 (UTC - 5:00)
System Uptime: 0 days 0:39:15.272
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {100befbf0, 2, 1, fffff80002a7b3d3}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2b3 )

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: 0000000100befbf0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002a7b3d3, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ca90e0
0000000100befbf0

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiTimerWaitTest+2b3
fffff800`02a7b3d3 48894108 mov qword ptr [rcx+8],rax

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff800041f43d0 -- (.trap 0xfffff800041f43d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80002befb68 rbx=0000000000000000 rcx=0000000100befbe8
rdx=fffff80002befb68 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a7b3d3 rsp=fffff800041f4560 rbp=0000000100befbe8
r8=fffff80002bee001 r9=0000000000000004 r10=00000000000000c2
r11=fffff88002a1d010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!KiTimerWaitTest+0x2b3:
fffff800`02a7b3d3 48894108 mov qword ptr [rcx+8],rax ds:f3c0:00000001`00befbf0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a70ca9 to fffff80002a71740

STACK_TEXT:
fffff800`041f4288 fffff800`02a70ca9 : 00000000`0000000a 00000001`00befbf0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`041f4290 fffff800`02a6f920 : 00000000`0000000a fffff800`02befb70 fffff800`40c40088 fffff800`02a7dde0 : nt!KiBugCheckDispatch+0x69
fffff800`041f43d0 fffff800`02a7b3d3 : 00000000`00000000 fffff800`02a7d29e fffff800`041f4618 00000000`00000001 : nt!KiPageFault+0x260
fffff800`041f4560 fffff800`02a7cd7d : fffff800`02befb68 00000000`00024dc1 00000000`00000000 00000000`00000000 : nt!KiTimerWaitTest+0x2b3
fffff800`041f45e0 fffff800`02a7d4be : 00000005`7bda12f6 fffff800`041f4c58 00000000`00024dc2 fffff800`02befac8 : nt!KiProcessExpiredTimerList+0x6d
fffff800`041f4c30 fffff800`02a7ccb7 : 00000001`6cc942c3 00000001`00024dc2 00000001`6cc942da 00000000`000000c2 : nt!KiTimerExpiration+0x1be
fffff800`041f4cd0 fffff800`02a79eea : fffff800`02bebe80 fffff800`02bf9c40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`041f4d80 00000000`00000000 : fffff800`041f5000 fffff800`041ef000 fffff800`041f4d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTimerWaitTest+2b3
fffff800`02a7b3d3 48894108 mov qword ptr [rcx+8],rax

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiTimerWaitTest+2b3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

FAILURE_BUCKET_ID: X64_0xA_nt!KiTimerWaitTest+2b3

BUCKET_ID: X64_0xA_nt!KiTimerWaitTest+2b3

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

Edited by n1nj4, 24 December 2010 - 08:42 AM.


BC AdBot (Login to Remove)

 


#2 keyboardNinja

keyboardNinja

    Bleepin' Ninja


  • BC Advisor
  • 4,815 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh interwebz
  • Local time:06:19 AM

Posted 24 December 2010 - 11:48 AM

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
PICNIC - Problem In Chair, Not In Computer

Posted Image Posted Image

20 Things I Learned About Browsers and the Web

#3 n1nj4

n1nj4
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:07:19 AM

Posted 24 December 2010 - 02:21 PM

==================================================
Dump File : 122310-5850-01.dmp
Crash Time : 12/23/2010 9:26:58 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000001`00befbf0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`02a7b3d3
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122310-5850-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 279,312

#4 keyboardNinja

keyboardNinja

    Bleepin' Ninja


  • BC Advisor
  • 4,815 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh interwebz
  • Local time:06:19 AM

Posted 24 December 2010 - 03:04 PM

Did it only happen once?

It was probably just a fluke, if that is the case.

Try doing the same thing again (logmein session), and see if the BSOD recurs.
PICNIC - Problem In Chair, Not In Computer

Posted Image Posted Image

20 Things I Learned About Browsers and the Web




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users