Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Which Blue Screen Solution do I need?


  • Please log in to reply

#1
Phlegmbot

Phlegmbot

    Member

  • Member
  • PipPipPip
  • 365 posts
With this info, can someone tell me which Blue Screen solution (from this page [or any other]: http://www.geekstogo...des-t43519.html ) that I need?


Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini112909-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
Debug session time: Sun Nov 29 22:21:32.000 2009 (GMT-5)
System Uptime: 0 days 0:01:57.593
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
...................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {c39a06d0, 0, bf82edf6, 0}


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

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

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: c39a06d0, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf82edf6, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: c39a06d0

FAULTING_IP:
win32k!vDIBSolidBlt+12
bf82edf6 8b0c85b8069abf mov ecx,dword ptr win32k!aulShiftFormat (bf9a06b8)[eax*4]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

TRAP_FRAME: f780d114 -- (.trap 0xfffffffff780d114)
ErrCode = 00000000
eax=01000006 ebx=e2370618 ecx=00000000 edx=e234bde4 esi=00000000 edi=e2370618
eip=bf82edf6 esp=f780d188 ebp=f780d2e0 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
win32k!vDIBSolidBlt+0x12:
bf82edf6 8b0c85b8069abf mov ecx,dword ptr win32k!aulShiftFormat (bf9a06b8)[eax*4] ds:0023:c39a06d0=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8051cc4f to 804f8cb5

STACK_TEXT:
f780d09c 8051cc4f 00000050 c39a06d0 00000000 nt!KeBugCheckEx+0x1b
f780d0fc 8054051c 00000000 c39a06d0 00000000 nt!MmAccessFault+0x8e7
f780d0fc bf82edf6 00000000 c39a06d0 00000000 nt!KiTrap0E+0xcc
f780d2e0 bf82bd63 e2370618 f780d3d4 00000000 win32k!vDIBSolidBlt+0x12
f780d34c bf805233 e1ce1008 00000000 00000000 win32k!EngBitBlt+0xe1
f780d39c bf80c74c e234bde4 f780d3f0 f780d3d4 win32k!GrePatBltLockedDC+0x1ea
f780d434 bf82f320 f780d46c 0000f0f0 0013eef8 win32k!GrePolyPatBltInternal+0x17c
f780d488 8053d638 01010928 00f00021 0013eef8 win32k!NtGdiPolyPatBlt+0xb5
f780d488 7c90e4f4 01010928 00f00021 0013eef8 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013eed4 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!vDIBSolidBlt+12
bf82edf6 8b0c85b8069abf mov ecx,dword ptr win32k!aulShiftFormat (bf9a06b8)[eax*4]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32k!vDIBSolidBlt+12

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a

FAILURE_BUCKET_ID: 0x50_win32k!vDIBSolidBlt+12

BUCKET_ID: 0x50_win32k!vDIBSolidBlt+12

Followup: MachineOwner
---------
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#3
Phlegmbot

Phlegmbot

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 365 posts
I do have TWO ram sticks -- I just checked to see what it says my RAM is: it says 448, which means one stick is definitely not in right.

Thank you!...I will try to reseat the RAM, but that's what got me into this mess in the first place.

What do I do if I can't get it to reseat correctly?
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
448 is correct if you figure the video sgares 64 megs of ram memory.
448 + 64 = 512 megs total
The ram will only fit one way so if it isn't reseating correctly then turn it around and try it.
  • 0

#5
Phlegmbot

Phlegmbot

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 365 posts
My additional memory stick is 512mb.

When I was having some booting issues (which I posted elsewhere on this board a week or two ago), one suggestion was to reseat the RAM (can't recall if I got that advice here or elsewhere). I did that, but apparently not well. I got one RAM stick in right, the other apparently only looked like it was in right.

Sure, it only fits in one way, but it looked like it was in and connecting when in fact it was not. I removed it and remembered a rule a techie at my old company told me: you don't have to be as gentle as you think you have to be. So I shoved the RAM in a bit harder and felt it connect.

The RAM now correctly reads as 960mb. Everything seems to be ducky. THX!!
  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Congratulations. :) for a successful resolution for your issue.

You are very welcome. I'm glad we could help and please let us know how everything works out for you.
If there is anything else we can do to help please feel free to ask. I appreciate that you allowed me to assist you with your issue and for your patience.
Thank you for choosing GeeksToGo for help. :) :)
This issue now appears to be resolved.


If other members are reading this and have a similar problem please begin a New Topic and someone will assist you as soon as possible
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP