windows minidump

tokinGLX · 06-25-2008, 11:25 PM

ive never fugged with this before and it seems that im having some issues getting the debugger to work right¿ im using the correct path for the symbols(far as im aware of) but its acting like it doesnt have the right one.
this is what i get when i open the crash dump in windbg.
im just trying to get my computer to be able to run a program without blue screening on me...anybody have any help to offer¿

----------------------------------------------------------------------------------------

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

Loading Dump File [C:\1\Minidump\Mini062508-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information

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 XP Kernel Version 2600 (Service Pack 3.3244) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Jun 25 16:10:37.687 2008 (GMT-6)
System Uptime: 0 days 0:43:14.410
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 1000000A, {0, ff, 0, 806e4ea0}

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

Unable to load image AmdK8.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AmdK8.sys
*** ERROR: Module load completed but symbols could not be loaded for AmdK8.sys
************************************************** ***********************
*** ***
*** ***
*** 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 : hardware ( AmdK8+3552 )

Followup: MachineOwne

Osprey · 06-25-2008, 11:59 PM

What you wanna' do here is : Clench your asscheeks really tight, then bear down for all you're worth. Once you start seeing stars, this part is important now, providing you didn't shit yourself, mash the keyboard with your forehead while singing the infamous "hell bent for leather" at the top of your lungs. If all goes according to Hoyle, you'll soon be unconscious and not worried in the least about the "blue screen". . . Oh, you're welcome.

tokinGLX · 06-26-2008, 12:03 AM

Quote:

Originally Posted by Osprey

What you wanna' do here is : Clench your asscheeks really tight, then bear down for all you're worth. Once you start seeing stars, this part is important now, providing you didn't shit yourself, mash the keyboard with your forehead while singing the infamous "hell bent for leather" at the top of your lungs. If all goes according to Hoyle, you'll soon be unconscious and not worried in the least about the "blue screen". . . Oh, you're welcome.

uh oh...i tried following your directions, but i think i messed up.
(':

JohnDoeRadio · 06-26-2008, 12:11 AM

i fuckin laughed pretty damn hard at that osprey. works like a charm.

Osprey · 06-26-2008, 12:19 AM

I'm a computer master. No question. You can only imagine how well my PC works. I do however, have to buy fresh boxers fairly often. . .

halffoot · 06-26-2008, 05:37 PM

I believe the root of the problem here... is that your running a windows operating system. Its time to wipe that baby and reinstall(or install linux).

khyberkitsune · 06-26-2008, 09:53 PM

Your error message hints at processor failure, or OS corruption. I first suggest a reinstall of Windows. If that doesn't work, you have a hardware issue.

Just FYI - I do this for a living, and taught laptop repair at Solectron Global. You can trust me.

also, which program are you trying to run that gives you a bluescreen?

tokinGLX · 06-26-2008, 10:40 PM

Quote:

Originally Posted by khyberkitsune

also, which program are you trying to run that gives you a bluescreen?

it *usually* occurs when playing games or when rendering video, it also randomly does it while watching movie files or flash videos on the interwebs.

do you have any idea why im getting that error about the symbols in windbg¿

hal, i would have been using linux for a few years now, but it just isnt compatible with everything that i need a computer for.

halffoot · 06-29-2008, 03:10 AM

Then get wine(a windows emulator).

Also, the bsod's associated with videos and games suggest something is wrong with your video card. Try a windows reinstall and if the problem persists you should get a new card.

khyberkitsune · 06-29-2008, 04:06 AM

Yea, that sounds far more like a video card issue. If you have anything overclocked, return it back to factory settings. If you don't, well, I hope you're not stuck using an onboard solution for games.

tokinGLX · 06-29-2008, 10:54 AM

Quote:

Originally Posted by halffoot

Then get wine(a windows emulator).

not all of the programs that i use are compatible with it. trust me, i have looked into it, on a near constant basis for the past 8 years. there is a reason i am stuck with windows.
(':

khyberkitsune · 06-30-2008, 07:44 AM

Quote:

Originally Posted by halffoot

Then get wine(a windows emulator).

Also, the bsod's associated with videos and games suggest something is wrong with your video card. Try a windows reinstall and if the problem persists you should get a new card.

I'm sorry. WINE stands for WINDOWS IS *NOT EMULATED*

You emulate HARDWARE. You don't emulate software - you re-write it for the hardware architecture you are using. To emulate software is a waste of time and resources and money.

Hate to rain on the parade, but since I DO PROGRAMING FOR THE WINE TEAM I feel it's my duty to say *WRONG!* and *BACK TO CLASS!*

khyberkitsune · 06-30-2008, 07:46 AM

Also - many games will BSOD due to bad memory addresses, so run memtest86+ on your RAM, as games and only a few other programs ever need to access such high memory addresses that aren't commonly tested and so can possibly lead to failure.

Your general signs of video card failure are artifacting and sudden framerate drops.

windows minidump

General Discussion