[rainforest123]

Which test will not run?

Which test will run?

No test detects all problem.

No test that identifies a problem is correct every time.

Go through these.
http://support.microsoft.com/search/...d=11922&range=


Have you read this one?
http://support.microsoft.com/kb/909444

I wish I could be more specific with a solution, sfm .. , but there doesn't seem to be a quick answer. Also, you did not provide the web sites you visited in your research.

If this were my computer, which it is not, I'd put in new memory.
www.crucial.com

HTH

RF123

[rainforest123]

joeten:
What are the parameters of the dmp file's 0x1A error?

http://msdn.microsoft.com/en-gb/library/ms793604.aspx

RF123

[joeten]

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

Loading Dump File [C:\Users\joe\Desktop\Mini110909-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 \SystemRoot\system32\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 x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`01a62000 PsLoadedModuleList = 0xfffff800`01c26dd0
Debug session time: Tue Nov 10 07:26:51.778 2009 (GMT+0)
System Uptime: 0 days 0:27:11.547
*********************************************************************
* 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 \SystemRoot\system32\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 1A, {41790, fffffa8003ed42f0, ffff, 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+5a450 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8003ed42f0
Arg3: 000000000000ffff
Arg4: 0000000000000000
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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
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: fffff80001a62000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a7801eb
BUGCHECK_STR: 0x1a_41790
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001a71bc8 to fffff80001abc450
STACK_TEXT:
fffffa60`0a682868 fffff800`01a71bc8 : 00000000`0000001a 00000000`00041790 fffffa80`03ed42f0 00000000`0000ffff : nt+0x5a450
fffffa60`0a682870 00000000`0000001a : 00000000`00041790 fffffa80`03ed42f0 00000000`0000ffff 00000000`00000000 : nt+0xfbc8
fffffa60`0a682878 00000000`00041790 : fffffa80`03ed42f0 00000000`0000ffff 00000000`00000000 fffff800`01aabecd : 0x1a
fffffa60`0a682880 fffffa80`03ed42f0 : 00000000`0000ffff 00000000`00000000 fffff800`01aabecd fffffa80`07e20040 : 0x41790
fffffa60`0a682888 00000000`0000ffff : 00000000`00000000 fffff800`01aabecd fffffa80`07e20040 fffff6fb`41ffbf20 : 0xfffffa80`03ed42f0
fffffa60`0a682890 00000000`00000000 : fffff800`01aabecd fffffa80`07e20040 fffff6fb`41ffbf20 00000000`00000000 : 0xffff

STACK_COMMAND: kb
FOLLOWUP_IP:
nt+5a450
fffff800`01abc450 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+5a450
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
this is just a quick check the problem could be the pagefile but this is just thinking out loud

[rainforest123]

This thread reports a similar mini dump.
http://www.techspot.com/vb/topic110471.html

Per Woody1191

Memory Corruption is normally cited when Incompatible Software or Faulty Device Drivers are found by the syste

sfmc . . .:
If the new your nVidia driver is the latest & greatest, try an older driver. I have had success using older drivers, on occasion.
Try Woody's advice, post #9 at http://www.techspot.com/vb/topic110471.html

I have not used Drive Clean Pro. I have used Driver Sweeper.

What brand is your Video card?

On a system w/ Vista Ultimate 32 bit, I had initially used an XFX GeForce 7600GS

I upgraded to an 8600GTS, but couldn't install the 8600 drivers. XFX tech support told me:
Uninstall nVidia drivers from the control panel's programs & features, in normal mode.
Boot to safe mode. In safe mode, run Driver Sweeper. Then, still in safe mode, install the 8600 drivers. THEN, boot to normal mode. I have used this protocol on multiple computers. I have been successful every time.

Why did you re-format & re-install?

It would help to know which motherboard & chipset you have, sf, as well knowing if the video & network devices are integrated or add in cards.

You noted:
so this is whats wierd..

i uninstalled the video driver.. restarted.. let it do its thing and i havent had a problem since..

Plan A:
Uninstall nVidia drivers as outlined, in this post.
Do NOT install the latest drivers.
Turn off computer.
connect monitor to onboard video port, if there is one. I haven't found your answer to that question I posed, on page 1.
Use the computer.

Plan B:
Uninstall nVidia drivers as outlined, in this post.
Turn off computer.
connect monitor to your 9800 card, using generic or older drivers.
Use the computer.

Plan C:
Reformat
Re-install
Install drivers in this order:
Chipset
network
audio
Do NOT install drivers specific to your 9800 card, unless they are installed by Vista.
Use the computer.

After you have experienced no BSODs, install the oldest 9800 compatible drivers you can find.

And again, why did you re-format / re-install?

RF123

[rainforest123]

Link to Driver Sweeper
http://downloads.guru3d.com/Guru3D--...up)_d1655.html

[sfmccarthyjr]

great info here guys. thank you so much .. i really jsut needed a step forward in the right direction. i was hoping it wasnt my RAM i took out 2 gigs to see if that would help..and its probly the driver for Nvidia so in suggetion to that im going to uninstall it and plug it back in and do it like that

[rainforest123]

Let us know the steps you take.

Keep us posted as to the outcome.

Best of success.

RF123

[joeten]

HI the error code shows as bug check 0x1a this is a memory management issue however it may also point to gpu memory if your driver has been out of date for the system it is possible that this got thrown up as memory it may have tried to access a area which it is not allowed,but keep a eye on your graphics card and test it if you can just to rule it out

[rainforest123]

There is a program that will test CPUs & GPUs.
http://www.ocbase.com/perestroika_en/

I have used it for CPU testing.

I have no reservations to recommend its use. Usual disclaimers apply.

RF123

[mandris]

hi there the name is brett im having the same error bsod C:\Windows\MEMORY.DMP ive tried reformatting and creating a new partition and everything but still i cant fix this its been going on for almost two years now i desperately need help.lits seems to crash when i have multiple files and apps open.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 3081
Additional information about the problem:
BCCode: 7f
BCP1: 0000000D
BCP2: 00000000
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\Mini111109-01.dmp
C:\Users\Brett Colins\AppData\Local\Temp\WER-39359-0.sysdata.xml
C:\Users\Brett Colins\AppData\Local\Temp\WERFFC1.tmp.version.txt
Read our privacy statement:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0409
Files that help describe the problem:
C:\Windows\MEMORY.DMP

[rainforest123]

Dear Mandris, aka Brett Colins [ see your post ].
You might want to edit your post.
Up to you.

Please start your own thread. Doing so will allow us to provide you with personalized advice.

Best of success.

RF123