help figuring out a mini dump

undisclosed · Jul 9, 2010

my pc has been crashing non stop with 0x0000001e errors and it has no

string attached just plain 0x000. i updated the bios tonight but im

trying to make heads and tails of this mini dump to see if that will

resolve the issue. any help will be appreciated.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\070910-26847-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: Invalid

Symbol loading may be unreliable without a symbol search path.

Use .symfix to have the debugger choose a symbol path.

After setting your symbol path, use .reload to refresh symbol

locations.

Executable search path is:

Symbols can not be loaded because symbol path is not initialized.

The Symbol Path can be set by:

using the _NT_SYMBOL_PATH environment variable.

using the -y <symbol_path> argument when starting the debugger.

using .sympath and .sympath+

Unable to load image ntoskrnl.exe, Win32 error 0n2

ERROR: Module load completed but symbols could not be loaded for

ntoskrnl.exe

Windows 7 Kernel Version 7600 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909

Machine Name:

Kernel base = 0xfffff800`02c10000 PsLoadedModuleList =

0xfffff800`02e4de50

Debug session time: Fri Jul 9 03:07:03.466 2010 (UTC - 4:00)

System Uptime: 0 days 0:12:31.544

Symbols can not be loaded because symbol path is not initialized.

The Symbol Path can be set by:

using the _NT_SYMBOL_PATH environment variable.

using the -y <symbol_path> argument when starting the debugger.

using .sympath and .sympath+

Unable to load image ntoskrnl.exe, Win32 error 0n2

ERROR: Module load completed but symbols could not be loaded for

ntoskrnl.exe

Loading Kernel Symbols

..............................................Unable to load image

Unknown_Module_00000000`00000000, Win32 error 0n2

WARNING: Unable to verify timestamp for

Unknown_Module_00000000`00000000

Unable to add module at 00000000`00000000

Loading User Symbols

Bugcheck Analysis

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 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

Probably caused by : ntoskrnl.exe ( nt+705d0 )

Followup: MachineOwner

---------

--

Darkankh

Dave-UK · Jul 9, 2010

"undisclosed" wrote in message news:17a7857b66221c7d0d30647fb834feef@nntp-gateway.com...

>

> my pc has been crashing non stop with 0x0000001e errors and it has no

> string attached just plain 0x000. i updated the bios tonight but im

> trying to make heads and tails of this mini dump to see if that will

> resolve the issue. any help will be appreciated.

>

>

Haven't got a clue regarding the debugger output but have you tried BlueScreenView?

http://www.nirsoft.net/utils/blue_screen_view.html

It will load any dump files it finds and then list and highlight

any files it thinks may be causing problems.

undisclosed · Jul 9, 2010

it listed ntoskrnl.exe as problem.. for all but 3 and those were

tcpip.sys so I know the two files now.. but from what I read you dont

replace ntoskrnl.exe and i tried repair disk.. it found no problems. I

really do not wanna do a fresh install.

--

Darkankh

Dave-UK · Jul 9, 2010

"undisclosed" wrote in message news:99f9c6a204c4dbc8c8310ccc76624d5f@nntp-gateway.com...

>

> it listed ntoskrnl.exe as problem.. for all but 3 and those were

> tcpip.sys so I know the two files now.. but from what I read you dont

> replace ntoskrnl.exe and i tried repair disk.. it found no problems. I

> really do not wanna do a fresh install.

>

>

> --

> Darkankh

I don't know what to suggest really, except basic things which you have

probably already checked.

Does it crash in Safe Mode?

Can you boot and run a live linux disk or a boot disk like Hirens\UBCD4Win without

crashing to rule out hardware ?

Justin · Jul 10, 2010

In article <17a7857b66221c7d0d30647fb834feef@nntp-gateway.com>,

undisclosed wrote:

> my pc has been crashing non stop with 0x0000001e errors and it has nostring

> attached just plain 0x000. i updated the bios tonight but imtrying to make

> heads and tails of this mini dump to see if that willresolve the issue. any

> help will be appreciated.Microsoft (R) Windows Debugger Version 6.12.0002.633

> AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump

> File [C:\Windows\Minidump\070910-26847-01.dmp]Mini Kernel Dump File: Only

It could be a bad hard drive or bad RAM.

First let's check the RAM.

Go here

http://www.memtest.org/#downiso

Download the USB version and make a memory checker USB boot drive. Then

you have to set your PC's bios to boot from the USB which I can't guide

you through.

Basically you have to look for something called "boot priority" and put

USB as number one.

Once it boots off the USB stick

http://www.youtube.com/watch?v=Sz3x8FAABQg

If you see red - that's bad and your memory has errors/defects.

Peter Foldes · Jul 10, 2010

Does the following show up at any point

//

// NTOSKRNL main

//

int __cdecl main(IN PLOADER_PARAMETER_BLOCK LoaderBlock)

{

//

// Fire up NT!

//

KiSystemStartup(LoaderBlock);

return 0;

}

--

Peter

Please Reply to Newsgroup for the benefit of others

Requests for assistance by email can not and will not be acknowledged.

http://www.microsoft.com/protect

<undisclosed> wrote in message

news:17a7857b66221c7d0d30647fb834feef@nntp-gateway.com...

>

> my pc has been crashing non stop with 0x0000001e errors and it has no

> string attached just plain 0x000. i updated the bios tonight but im

> trying to make heads and tails of this mini dump to see if that will

> resolve the issue. any help will be appreciated.

>

>

> Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

> Copyright (c) Microsoft Corporation. All rights reserved.

>

>

> Loading Dump File [C:\Windows\Minidump\070910-26847-01.dmp]

> Mini Kernel Dump File: Only registers and stack trace are available

>

> Symbol search path is: Invalid

>

> Symbol loading may be unreliable without a symbol search path.

>

> Use .symfix to have the debugger choose a symbol path.

>

> After setting your symbol path, use .reload to refresh symbol

> locations.

>

> Executable search path is:

>

> Symbols can not be loaded because symbol path is not initialized.

>

> The Symbol Path can be set by:

> using the _NT_SYMBOL_PATH environment variable.

> using the -y <symbol_path> argument when starting the debugger.

> using .sympath and .sympath+

>

> Unable to load image ntoskrnl.exe, Win32 error 0n2

> ERROR: Module load completed but symbols could not be loaded for

> ntoskrnl.exe

> Windows 7 Kernel Version 7600 MP (8 procs) Free x64

> Product: WinNt, suite: TerminalServer SingleUserTS

> Built by: 7600.16539.amd64fre.win7_gdr.100226-1909

> Machine Name:

> Kernel base = 0xfffff800`02c10000 PsLoadedModuleList =

> 0xfffff800`02e4de50

> Debug session time: Fri Jul 9 03:07:03.466 2010 (UTC - 4:00)

> System Uptime: 0 days 0:12:31.544

>

> Symbols can not be loaded because symbol path is not initialized.

>

> The Symbol Path can be set by:

> using the _NT_SYMBOL_PATH environment variable.

> using the -y <symbol_path> argument when starting the debugger.

> using .sympath and .sympath+

>

> Unable to load image ntoskrnl.exe, Win32 error 0n2

> ERROR: Module load completed but symbols could not be loaded for

> ntoskrnl.exe

> Loading Kernel Symbols

> .............................................Unable to load image

> Unknown_Module_00000000`00000000, Win32 error 0n2

> WARNING: Unable to verify timestamp for

> Unknown_Module_00000000`00000000

> Unable to add module at 00000000`00000000

>

> Loading User Symbols

>

>

>

> Bugcheck Analysis

>

>

>

>

>

> Use !analyze -v to get detailed debugging information.

>

> BugCheck 1E, {0, 0, 0, 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

>

>

>

>

> Probably caused by : ntoskrnl.exe ( nt+705d0 )

>

> Followup: MachineOwner

> ---------

>

>

> --

> Darkankh

Andrew · Jul 10, 2010

"undisclosed" wrote in message

news:17a7857b66221c7d0d30647fb834feef@nntp-gateway.com...

>

>

http://download.microsoft.com/downl...in7.7600.16385.090713-1255.X64FRE.Symbols.msi

unzip these; put them somewhere like C:\symbols.

Run the following commands in the debugger.

!sympath=C:\symbols

..Reload

then you can run your !analyze -v command.

If you've never worked with symbols before, it will still look foreign to

you.

More than likely 1e is a device driver issue.

You should be able to get it down to a particular .sys file if it's a kernel

mode driver.

--

Andrew

undisclosed · Jul 13, 2010

ok so I flashed the bios.. updated video graphics.. then used the

program to check all drivers.. updated those.. since then no bsod in

last 4 days.. so it looks like im in the clear thanks guys

--

Darkankh

help figuring out a mini dump

undisclosed

Guest

Dave-UK

Guest

undisclosed

Guest

Dave-UK

Guest

Justin

Guest

Peter Foldes

Guest

Andrew

Guest

undisclosed

Guest

Similar threads