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

help please


  • Please log in to reply
3 replies to this topic

#1 youngster

youngster

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:22 AM

Posted 12 December 2008 - 12:25 AM

Looking for some advice, bt not the most knowledgeable person about this stuff. Have a newly built computer

intel pentium d 3.2
2 gig ram
have vista ultimate 64 bit

anyways it is crashing to the blue screen constantly. I follwed the debugging section from this site and this is what i got


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


Loading Dump File [C:\Windows\Minidump\Mini121108-06.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 Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0xfffff800`0185f000 PsLoadedModuleList = 0xfffff800`01a24db0
Debug session time: Thu Dec 11 23:42:48.690 2008 (GMT-5)
System Uptime: 0 days 0:02:17.253
Loading Kernel Symbols
...............................................................
................................................................

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80001b36c84, fffffa6003484200, 0}

Probably caused by : hardware ( nt!AlpcpReceiveMessage+750 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80001b36c84, Address of the exception record for the exception that caused the bugcheck
Arg3: fffffa6003484200, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!AlpcpReceiveMessage+750
fffff800`01b36c84 3033 xor byte ptr [rbx],dh

CONTEXT: fffffa6003484200 -- (.cxr 0xfffffa6003484200)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000040
rdx=fffff88007343720 rsi=00000000018dfc88 rdi=fffff88007343720
rip=fffff80001b36c84 rsp=fffffa6003484a60 rbp=0000000000000000
r8=fffffa8004ea0920 r9=00000000018dfc8c r10=0038004300310043
r11=0000000000484298 r12=0000000000484298 r13=0000000000000000
r14=fffffa8004ea0920 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!AlpcpReceiveMessage+0x750:
fffff800`01b36c84 3033 xor byte ptr [rbx],dh ds:002b:00000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 6

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

MISALIGNED_IP:
nt!AlpcpReceiveMessage+750
fffff800`01b36c84 3033 xor byte ptr [rbx],dh

LAST_CONTROL_TRANSFER: from fffff80001b3737a to fffff80001b36c84

STACK_TEXT:
fffffa60`03484a60 fffff800`01b3737a : fffffa80`04ea0920 fffffa60`00000000 00000000`00000000 fffffa80`04ea0920 : nt!AlpcpReceiveMessage+0x750
fffffa60`03484b00 fffff800`018b3df3 : fffffa80`04eb25d0 fffffa60`03484ca0 00000000`018dfc18 fffff800`01b30ec4 : nt!NtAlpcSendWaitReceivePort+0x1da
fffffa60`03484bb0 00000000`776462ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`018dfbf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776462ca


FOLLOWUP_IP:
nt!AlpcpReceiveMessage+750
fffff800`01b36c84 3033 xor byte ptr [rbx],dh

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!AlpcpReceiveMessage+750

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xfffffa6003484200 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

BUCKET_ID: X64_IP_MISALIGNED

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

if there is anyhting i can do to stop the crashing I would love to know cuz it unusable at this point

BC AdBot (Login to Remove)

 


#2 youngster

youngster
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:22 AM

Posted 12 December 2008 - 12:27 AM

here are some more of the minidumps, thanks for any advice!!!


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


Loading Dump File [C:\Windows\Minidump\Mini121108-05.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 Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0xfffff800`0181e000 PsLoadedModuleList = 0xfffff800`019e3db0
Debug session time: Thu Dec 11 23:39:38.377 2008 (GMT-5)
System Uptime: 0 days 0:10:29.940
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffb900c0616784, 0, fffff960000e0c9e, 7}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!EngTextOut+192 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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.
Arguments:
Arg1: ffffb900c0616784, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960000e0c9e, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001a47080
ffffb900c0616784

FAULTING_IP:
win32k!EngTextOut+192
fffff960`000e0c9e 440301 add r8d,dword ptr [rcx]

MM_INTERNAL_CODE: 7

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: iexplore.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffffa60083e5200 -- (.trap 0xfffffa60083e5200)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c0601f00 rbx=fffff900c3bc1510 rcx=ffffb900c0616784
rdx=fffff900c0844588 rsi=00000000ffffffff rdi=0000000000000185
rip=fffff960000e0c9e rsp=fffffa60083e5390 rbp=fffffa60083e5f20
r8=00000000000001f8 r9=0000000000000000 r10=0000000000000000
r11=fffff900c0844580 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
win32k!EngTextOut+0x192:
fffff960`000e0c9e 440301 add r8d,dword ptr [rcx] ds:ffffb900`c0616784=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000188149f to fffff80001873350

STACK_TEXT:
fffffa60`083e5108 fffff800`0188149f : 00000000`00000050 ffffb900`c0616784 00000000`00000000 fffffa60`083e5200 : nt!KeBugCheckEx
fffffa60`083e5110 fffff800`01871ed9 : 00000000`00000000 fffff960`000c5836 00000000`01b7b900 00000000`00000000 : nt!MmAccessFault+0x4af
fffffa60`083e5200 fffff960`000e0c9e : 00000000`00000000 00000000`00000000 fffffa60`083e5f20 fffffa60`083e5710 : nt!KiPageFault+0x119
fffffa60`083e5390 fffff960`000e05fb : fffffa60`083e5c00 fffff900`00000000 00000000`00000080 fffff900`00000e50 : win32k!EngTextOut+0x192
fffffa60`083e5b70 fffff960`000e0aba : 00000000`00000001 fffff900`c062e790 00000000`00000001 00000000`00000001 : win32k!OffTextOut+0xdf
fffffa60`083e5bf0 fffff960`000ccc8a : fffff900`c06b8b88 fffff900`c323e5d0 00000000`02e88e3a fffffa60`083e5e60 : win32k!SpTextOut+0x16a
fffffa60`083e5cf0 fffff960`0026b38e : fffff900`c323e6f8 00000000`000001f8 fffff900`00000266 00000000`00011500 : win32k!GreExtTextOutWLocked+0x1d2a
fffffa60`083e60c0 fffff960`00120c3f : 00000000`77305af4 fffff960`00115f9c fffff960`02e88e3a fffff900`00ffffff : win32k!GreBatchTextOut+0x26a
fffffa60`083e6160 fffff800`01872cfc : 00000000`77305af4 fffffa60`083e6410 fffff960`00000000 00000000`00000000 : win32k!NtGdiFlushUserBatch+0x343
fffffa60`083e6390 00000000`75d83d09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceGdiTebAccess+0x25
00000000`089bde48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75d83d09


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!EngTextOut+192
fffff960`000e0c9e 440301 add r8d,dword ptr [rcx]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32k!EngTextOut+192

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1bca9

FAILURE_BUCKET_ID: X64_0x50_win32k!EngTextOut+192

BUCKET_ID: X64_0x50_win32k!EngTextOut+192

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

#3 youngster

youngster
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:22 AM

Posted 12 December 2008 - 12:28 AM

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


Loading Dump File [C:\Windows\Minidump\Mini121108-04.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 Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0xfffff800`0184d000 PsLoadedModuleList = 0xfffff800`01a12db0
Debug session time: Thu Dec 11 23:13:48.455 2008 (GMT-5)
System Uptime: 0 days 0:01:10.034
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff800018b1641, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29317 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800018b1641, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!MmAccessFault+1651
fffff800`018b1641 004889 add byte ptr [rax-77h],cl

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001a76080
ffffffffffffffff

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000187be47 to fffff800018a2350

STACK_TEXT:
fffffa60`06f0ba48 fffff800`0187be47 : 00000000`0000001e ffffffff`c0000005 fffff800`018b1641 00000000`00000000 : nt!KeBugCheckEx
fffffa60`06f0ba50 fffff800`018a21a9 : fffffa60`06f0c188 00000000`03420c03 fffffa60`06f0c230 fffff6fb`400000d0 : nt! ?? ::FNODOBFM::`string'+0x29317
fffffa60`06f0c050 fffff800`018a0d8d : fffff900`00000000 fffffa60`00ffffff fffff900`c092a950 00000000`00000000 : nt!KiExceptionDispatch+0xa9
fffffa60`06f0c230 fffff800`018b1641 : fffffa60`06f0c448 fffff960`001b8456 fffff900`c08c7010 fffff960`001b6886 : nt!KiGeneralProtectionFault+0xcd
fffffa60`06f0c3c0 fffff800`018a0ed9 : 00000000`00000000 fffffa60`06f0c530 00000000`01850001 00000000`04271930 : nt!MmAccessFault+0x1651
fffffa60`06f0c4b0 000007fe`fc1ccb95 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119
00000000`036ceed0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fc1ccb95


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+29317
fffff800`0187be47 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+29317

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

FAILURE_BUCKET_ID: X64_0x1E_nt!_??_::FNODOBFM::_string_+29317

BUCKET_ID: X64_0x1E_nt!_??_::FNODOBFM::_string_+29317

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

#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:22 AM

Posted 13 December 2008 - 07:12 AM

I'm thinking this might be a problem with your memory. So, for starters, run the Windows Memory diagnostic for several passes to see if it gives you errors. Here's a link to the "how-to": http://www.bleepingcomputer.com/tutorials/using-vista-windows-memory-diagnostics-tool/
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users