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

Constant Blue Screen Problem! (windows Report Posted)


  • Please log in to reply
32 replies to this topic

#1 ghady

ghady

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:22 AM

Posted 19 August 2008 - 05:11 AM

Hey all,

My vista's been doing all sorts of weirdness lately. The blue screen of death's been popping up several times a day, and randomly, it seems. Usually i'd be typing something on word and listening to music (windows media player), the sound'd suddenly get stuck and do a "bambambambambambambam" kind of thing, till the blue screen comes on, says something about dumping physical memory, and restarts. They keep asking me if i want to start in safe mode, but i wouldn't know what to do even if i did.

Here's the report microsoft keeps showing me, in case it helps:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FD3657DC
BCP2: 00000001
BCP3: 93CE26B7
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini081908-02.dmp
C:\Users\Ghady\AppData\Local\Temp\WER-42541-0.sysdata.xml
C:\Users\Ghady\AppData\Local\Temp\WERD7C7.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=501...mp;clcid=0x0409


anyone got any ideas?
thanks,
-g
"Did you know that before Kevin was a novelist, he worked at a recycling center?" - J. Maroney

BC AdBot (Login to Remove)

 


m

#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 19 August 2008 - 08:01 AM

Information about the error is here: http://aumha.org/a/stop.php#0x50

You can locate the C:\Windows\Minidump\Mini081908-02.dmp file and then use this link to perform an analysis: http://forums.majorgeeks.com/showthread.php?t=35246

Then copy and paste the results here for us to have a look at.
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.

#3 ghady

ghady
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:22 AM

Posted 20 August 2008 - 01:39 AM

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


Loading Dump File [C:\Windows\Minidump\Mini081908-02.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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Tue Aug 19 13:00:53.851 2008 (GMT+3)
System Uptime: 0 days 10:42:22.244
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
..................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fd3657dc, 1, 93ce26b7, 0}

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





this sounds wrong, i didnt get what the site you sent me said i should get. what's up with that? i followed the instructions exactly as he had written them. should i do it again?
"Did you know that before Kevin was a novelist, he worked at a recycling center?" - J. Maroney

#4 ghady

ghady
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:22 AM

Posted 20 August 2008 - 01:42 AM

oh wait, it just did something else


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


Loading Dump File [C:\Windows\Minidump\Mini081908-02.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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Tue Aug 19 13:00:53.851 2008 (GMT+3)
System Uptime: 0 days 10:42:22.244
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
..................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fd3657dc, 1, 93ce26b7, 0}

***** 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 ***
*** ***
*************************************************************************
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\471EA39C3a1000\ntkrnlpa.exe
The system cannot find the file specified.

*************************************************************************
*** ***
*** ***
*** 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 : win32k.sys ( win32k!HmgShareLock+50 )

Followup: MachineOwner
---------
"Did you know that before Kevin was a novelist, he worked at a recycling center?" - J. Maroney

#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 20 August 2008 - 05:24 AM

It's likely that you don't have the symbols file loaded correctly. I'd follow the instructions exactly, step by step, in order to produce a readable analysis of the dump file.
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.

#6 ghady

ghady
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:22 AM

Posted 21 August 2008 - 01:17 PM

(sorry, my bad, see below)

Edited by ghady, 21 August 2008 - 01:30 PM.


#7 ghady

ghady
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:22 AM

Posted 21 August 2008 - 01:29 PM

i tried it again, exactly as he said, with both the newest version of the dubugger AND an old version, and i got this:


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


Loading Dump File [C:\Windows\Minidump\Mini081908-02.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:
Map \SystemRoot\system32\ntkrnlpa.exe:
Image region 800:e4a00 does not fit in mapping
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Tue Aug 19 13:00:53.851 2008 (GMT+3)
System Uptime: 0 days 10:42:22.244
Map \SystemRoot\system32\ntkrnlpa.exe:
Image region 800:e4a00 does not fit in mapping
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
..................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fd3657dc, 1, 93ce26b7, 0}

***** 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 : win32k.sys ( win32k!HmgShareLock+50 )

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

what should i do??
sorry this is taking so long,
-g
"Did you know that before Kevin was a novelist, he worked at a recycling center?" - J. Maroney

#8 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 21 August 2008 - 03:30 PM

Not a problem. Try this:
Ensure that you're connected to the internet.
Copy the dump file to your desktop
Open up WinDbg
Ensure that the Symbols are loaded (check to be sure)
Drag the .dmp file onto the WinDbg window and let go.

If this doesn't work, we'll try another way.
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.

#9 ghady

ghady
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:22 AM

Posted 21 August 2008 - 08:49 PM

no, still didn't work. it keeps giving me "debugee not connected" tho even though i AM connected to the interent :s
"Did you know that before Kevin was a novelist, he worked at a recycling center?" - J. Maroney

#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 22 August 2008 - 03:09 PM

Look for a PM from me....
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.

#11 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 23 August 2008 - 08:35 AM

I analyzed the dump file that was submitted to me via email and got this:

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


Loading Dump File [C:\Users\FUBAR\Desktop\Mini082208-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 Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Thu Aug 21 20:30:24.380 2008 (GMT-4)
System Uptime: 1 days 11:12:42.831
Loading Kernel Symbols
..................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 113d, 0, b6139008}

GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
*** WARNING: Unable to verify timestamp for PxHelp20.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
*** WARNING: Unable to verify timestamp for iastor.sys
*** ERROR: Module load completed but symbols could not be loaded for iastor.sys
*** WARNING: Unable to verify timestamp for iastorv.sys
*** ERROR: Module load completed but symbols could not be loaded for iastorv.sys
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
*** WARNING: Unable to verify timestamp for msrpc.sys
*** ERROR: Module load completed but symbols could not be loaded for msrpc.sys
*** WARNING: Unable to verify timestamp for OEM02Vfx.sys
*** ERROR: Module load completed but symbols could not be loaded for OEM02Vfx.sys
*** WARNING: Unable to verify timestamp for bcm4sbxp.sys
*** ERROR: Module load completed but symbols could not be loaded for bcm4sbxp.sys
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
*** WARNING: Unable to verify timestamp for btwrchid.sys
*** ERROR: Module load completed but symbols could not be loaded for btwrchid.sys
*** WARNING: Unable to verify timestamp for Fs_Rec.SYS
*** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.SYS
*** WARNING: Unable to verify timestamp for avgmfx86.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx86.sys
*** WARNING: Unable to verify timestamp for rimmptsk.sys
*** ERROR: Module load completed but symbols could not be loaded for rimmptsk.sys
*** WARNING: Unable to verify timestamp for rimsptsk.sys
*** ERROR: Module load completed but symbols could not be loaded for rimsptsk.sys
*** WARNING: Unable to verify timestamp for Msfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Msfs.SYS
*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
*** WARNING: Unable to verify timestamp for rixdptsk.sys
*** ERROR: Module load completed but symbols could not be loaded for rixdptsk.sys
*** WARNING: Unable to verify timestamp for HSXHWAZL.sys
*** ERROR: Module load completed but symbols could not be loaded for HSXHWAZL.sys
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for stwrt.sys
*** ERROR: Module load completed but symbols could not be loaded for stwrt.sys
*** WARNING: Unable to verify timestamp for NETw4v32.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw4v32.sys
*** WARNING: Unable to verify timestamp for Null.SYS
*** ERROR: Module load completed but symbols could not be loaded for Null.SYS
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
*** WARNING: Unable to verify timestamp for HSX_CNXT.sys
*** ERROR: Module load completed but symbols could not be loaded for HSX_CNXT.sys
*** WARNING: Unable to verify timestamp for HSX_DPV.sys
*** ERROR: Module load completed but symbols could not be loaded for HSX_DPV.sys
*** WARNING: Unable to verify timestamp for OEM02Dev.sys
*** ERROR: Module load completed but symbols could not be loaded for OEM02Dev.sys
*** WARNING: Unable to verify timestamp for avgldx86.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx86.sys
*** WARNING: Unable to verify timestamp for btwavdt.sys
*** ERROR: Module load completed but symbols could not be loaded for btwavdt.sys
*** WARNING: Unable to verify timestamp for secdrv.SYS
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
*** WARNING: Unable to verify timestamp for btwaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for btwaudio.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*** WARNING: Unable to verify timestamp for TSDDD.dll
*** ERROR: Module load completed but symbols could not be loaded for TSDDD.dll
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
*** WARNING: Unable to verify timestamp for avgwfpx.sys
*** ERROR: Module load completed but symbols could not be loaded for avgwfpx.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for spsys.sys -
*** WARNING: Unable to verify timestamp for mdmxsdk.sys
*** ERROR: Module load completed but symbols could not be loaded for mdmxsdk.sys
*** WARNING: Unable to verify timestamp for xaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for xaudio.sys
GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0


Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+17f )

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

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000113d, (reserved)
Arg3: 00000000, Memory contents of the pool block
Arg4: b6139008, Address of the block of pool being deallocated

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

GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0



POOL_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
b6139008

BUGCHECK_STR: 0xc2_7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 81ce7ce8 to 81cd8681

STACK_TEXT:
8866bb2c 81ce7ce8 000000c2 00000007 0000113d nt!KeBugCheckEx+0x1e
8866bba0 81dd37bc b6139008 00000000 00000000 nt!ExFreePoolWithTag+0x17f
8866bbd4 81cb077e 848f0118 b68c38d8 00000000 nt!MiSegmentDelete+0x135
8866bbf8 81cb3c3b 848f0118 b68c3800 b68c38c0 nt!MiCheckControlArea+0x8f
8866bc10 81dd392c 848f0118 00000000 00000000 nt!MiDereferenceControlAreaBySection+0x2d
8866bc34 81ded505 848f0118 81fa7104 b68c38c0 nt!MiSectionDelete+0x101
8866bc50 81c478c8 b68c38d8 00000000 a7b50238 nt!ObpRemoveObjectRoutine+0x100
8866bc78 81cc4613 00010000 a7b5027c a7b50238 nt!ObfDereferenceObject+0xa1
8866bca0 81c24777 00000001 846f7618 a9591e60 nt!CcDeleteSharedCacheMap+0x192
8866bcec 81cbc2f3 a7b50238 8866bd10 00000000 nt!CcWriteBehind+0x40f
8866bd44 81c78fa0 83a75ff0 00000000 83a6cd78 nt!CcWorkerThread+0x1bd
8866bd7c 81e254e0 83a75ff0 88660680 00000000 nt!ExpWorkerThread+0xfd
8866bdc0 81c9159e 81c78ea3 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExFreePoolWithTag+17f
81ce7ce8 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ExFreePoolWithTag+17f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c

FAILURE_BUCKET_ID: 0xc2_7_nt!ExFreePoolWithTag+17f

BUCKET_ID: 0xc2_7_nt!ExFreePoolWithTag+17f

Followup: MachineOwner


The debugger wasn't able to verify the timestamps for a whole bunch of drivers (could the time be set wrong on the system?) so that may cause some loss of information. Dunno how to fix it for future dumps - that's gonna take some research on my part.

The error was generated when something tried to free memory - and it seems that the memory was already freed - and that caused the crash.

So, IMO, the first step would be to use Driver Verifier to see what it'll report. Here's a link on how to use it: http://www.microsoft.com/whdc/DevTools/too...taverifier.mspx
Here's a link for XP (which is similar and easier to use): http://support.microsoft.com/kb/244617

Essentially, you'll open Driver Verifier by going to start and typing "verifier" (without the quotes) and pressing Enter.
In the first screen you'll want to "Create standard settings" and then press the "Next" button
In the next screen you'll want to "Automatically select unsigned drivers" and then press the "Next" button.
In the next screen you'll just press the "Finish" button (this verifies which unsigned drivers have been selected)

Then reboot the system. In some cases this'll generate a crash immediately (this is a good thing), and in other cases it won't crash immediately (not so good). IME, the immediate crashes will give us the best info about what's crashing, while the delayed crashes may require some more research.

Also, Driver Verifier loads stuff on the system to monitor the drivers - so some minor slowdown is to be expected (and is why we don't verify all the drivers - it'll slow the system to a crawl). Once you're finished with Driver Verifier, it's essential that you go back into the program and "Delete existing settings" to free up the resources.

As it's a memory error, I'd suggest running this free, bootable utility: http://www.memtest86.com/

There's plenty of other things that this could be - but this'll give us a start. And the dump file from the next BSOD will likely be more helpful.
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.

#12 ghady

ghady
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:22 AM

Posted 23 August 2008 - 09:31 AM

ok, i did everything like you said...but there was no BSoD. so the minidump file'll have to wait till it happens again. i also went back and "deleted settings" like you said.

about the memory diagnostic thing, i downloaded it, but it keeps telling me i have to boot from some disk or something (which i clearly do not have). what's up with that?

thanks a lot! ill post the .dmp as soon as i get it.
-g
"Did you know that before Kevin was a novelist, he worked at a recycling center?" - J. Maroney

#13 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 23 August 2008 - 12:32 PM

You'll need to leave Driver Verifier enabled until you get a crash. Once you get the dump file, then it'll be OK to delete the existing settings.

You'll need to burn the diagnostic to a CD using an ISO burner in order for it to be bootable.
This is a direct link to the download you need: http://www.memtest86.com/memtest86-3.4a.iso.zip
Then unzip it to a folder on your desktop.

Next, download this free powertoy for Vista: http://isorecorder.alexfeinman.com/downloa...derV3RC1x86.zip
Then unzip it and double click on the setup.exe file to install it.

Once that's done, right click on the ISO file (the one in the second paragraph of this post) and select "Copy image to CD" - you'll need to have a blank CD in the drive at this point.

Then, when it's done, put the CD in the drive and boot from it. The test will automatically launch and run. If you start getting errors, stop the test and post back. Let the test run for a minimum of 3 passes - but overnight is better.
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.

#14 ghady

ghady
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:22 AM

Posted 25 August 2008 - 10:42 AM

hey, so my laptop just crashed, and im sending you the .dmp as we speak. im gonna restore my settings on that "verifier" program thing and run the diagnostic tool tonight.
thanks,
-g
"Did you know that before Kevin was a novelist, he worked at a recycling center?" - J. Maroney

#15 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 26 August 2008 - 05:50 AM

The Driver Verifier must be running when the crash happens. If it's not, the crash won't record the additional information from Driver Verifier.
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