Question

Locked

Vista BSOD

By nigelconst ·
I keep getting a BSOD every day & not at any particular time and often when I am not actually writing anything.

I tried installing the Microsoft fix, but it said this wasn't applicable to my system so I was unable to download it.

I created the following report and wonder if anyone can help me

Regards Nigel

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

0x00000c1 (oxbeffcf20,0xb3ffc9dc,0x007100dc,0x00000032)

Product
Windows

Problem
Shut down unexpectedly

Date
06/09/2009 09:39

Status
Not Reported

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale I 2057

Files that help describe the problem
Mini090609-01.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: c1
BCP1: B3FFCF20
BCP2: B3FFC9DC
BCP3: 007100DC
BCP4: 00000032
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Test Your Computer's Memory Using Windows Vista Memory Diagnostic Tool

by Jacky Howe In reply to Vista BSOD

Using this tool will require a reboot, so keep that in mind before you launch it.

Type memory into the Run box or press the Windows Key+r, and you should see the first option will say Memory Diagnostics Tool.

A dialog will pop up asking if you want to reboot and check for problems now, or check for problems the next time you restart.

If you choose to restart now, Vista will reboot into the memory diagnostic utility:

Or it can be acheived this way.

You'll have to hold down F8 on startup to get into Safe Mode, press Esc to get to the memory checker page and press TAB and then press Enter.

when you are on the screen press F1 and select Extended. Then press F10. Let it run through and let us know how you get on.


Minidump Files can be found here. C:\WINDOWS\Minidump\Mini122707-02.dmp

How to read the small memory dump files that Windows creates for debugging

http://support.microsoft.com/kb/315263

To download and install the Windows debugging tools, visit the following Microsoft Web site:

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

Instructions on using Windbg.

Open Windbg and select file, Symbol file path and browse to the Symbol folder that you have downloaded and installed Symbols to, select OK.
Close the workpage and save the Workspace information. This should lock in the Symbol path.
Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
Ctrl + a will let you copy the information and paste it into notepad.

Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.
FAULTING_THREA 864f6a98

DEFAULT_BUCKET_I GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: logon.scr

LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea

STACK_TEXT:
f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585


STACK_COMMAN .thread 0xffffffff864f6a98 ; kb

FOLLOWUP_IP:
sgiul50!DrvBitBlt+585
bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: sgiul50!DrvBitBlt+585

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: sgiul50

IMAGE_NAME: sgiul50.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7

FAILURE_BUCKET_I 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

BUCKET_I 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

Collapse -

BSOD

by nigelconst In reply to Test Your Computer's Memo ...

Hi Jacky,

I ran the memory diagnostic utility, but when went to the minidump file it hasnt saved anything from that diagnostic?

Any ideas please

Kind Regards Nigel

Collapse -

Yep try this

by Jacky Howe In reply to BSOD

Press the WinKey + Pause
Click Advanced and under Startup and Recovery select Settings.
Uncheck Automatically restart.
Click on the dropdown arrow under Write debugging information.
Select Small memory dump (64 KB) and the output is %SystemRoot%\Minidump.
Restart the PC normally as this will allow the System to Blue Screen and create the Minidump.

Collapse -

BSOD

by nigelconst In reply to Yep try this

Hi Jacky, thanks for your help, I had another BSOD this morning and managed to recover the following information, which hopefully may give us you a clue to what is going on.

Regards Nigel


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini090909-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:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x8221e000 PsLoadedModuleList = 0x82335c70
Debug session time: Wed Sep 9 09:46:51.440 2009 (GMT+1)
System Uptime: 0 days 1:52:51.603
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C1, {b563af00, b563a9dc, 5b0100, 32}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+cdb0d )

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

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

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: b563af00, address trying to free
Arg2: b563a9dc, address where one bit is corrupted
Arg3: 005b0100, (reserved)
Arg4: 00000032, caller is freeing an address where nearby bytes within the same page have a single bit error

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: 8221e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 49e0199e

BUGCHECK_STR: 0xC1_32

SPECIAL_POOL_CORRUPTION_TYPE: 32

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_I VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 822a8ce7 to 822ebb0d

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a6b0aa14 822a8ce7 000000c1 b563af00 b563a9dc nt+0xcdb0d
a6b0ab0c 8230b0f0 b563af00 00000000 b563af00 nt+0x8ace7
a6b0ab70 822d05e6 b563af00 00000000 a6b0abac nt+0xed0f0
a6b0ab8c 825001cd b563af00 00000000 b563af00 nt+0xb25e6
a6b0aba4 822d15e3 00000000 f6781474 b563af40 nt+0x2e21cd
a6b0abec 822d1e6c 00000000 a6b0ac18 a6b0ac24 nt+0xb35e3
a6b0ac44 822ca355 00000000 00000000 00000000 nt+0xb3e6c
a6b0ac94 82265f38 a390e350 00000000 a3913478 nt+0xac355
a6b0ace8 82450302 a3913478 00000006 82429d01 nt+0x47f38
a6b0ad50 82268c7a 000003d0 00000001 a6b0ad14 nt+0x232302
a6b0ad64 77b45e74 badb0d00 01dcfc10 00000000 nt+0x4ac7a
a6b0ad68 badb0d00 01dcfc10 00000000 00000000 0x77b45e74
a6b0ad6c 01dcfc10 00000000 00000000 00000000 0xbadb0d00
a6b0ad70 00000000 00000000 00000000 00000000 0x1dcfc10


STACK_COMMAN kb

FOLLOWUP_IP:
nt+cdb0d
822ebb0d 8be5 mov esp,ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+cdb0d

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_I WRONG_SYMBOLS

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

Collapse -

What was the result of the memory test

by Jacky Howe In reply to BSOD

can you PM me so that I can give you an address to send me the minidumps.

Also try this.

click Start, Run type verifier /log drvchk.txt and press Enter.

This will open a blank window while it is doing the check. Let it run for 3 minutes, then close the window, you may get an error message, but you can ignore it. Navigate to c:\documents and settings\your user name and double click to open drvchk.txt. Look for any errors.

Collapse -

Try booting with the Vista OS CD and do a repair using the following proced

by Jacky Howe In reply to What was the result of th ...

Insert your Windows Vista DVD and then restart your computer.
Press any key or the appropriate function key (depends on your computer) to boot to the DVD.
When your computer has booted to the DVD select your language and then press Next.
Click Repair your computer on the next screen.
Select the operating system your want to repair. There is usually only one here unless you?re dual booting.
Click Startup Repair on the next screen.
The Startup Repair tool will attempt to fix your computer and get it booting up again.

Follow the prompts.

Collapse -

Thank you for that, Jacky.

by boxfiddler Moderator In reply to Test Your Computer's Memo ...

I'd give you a thumb if I could. :)

Collapse -

Your welcome

by Jacky Howe In reply to Thank you for that, Jacky ...

and it saves a lot of hassle downloading an ISO and burning it. A great Vista/W7 feature.

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums