What this error?

[panais]

A blue screen,restart and this...

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1032

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000099
BCP2: 000000000003F5C2
BCP3: 0000000000000002
BCP4: 0000000000040932
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini010909-09.dmp
C:\Users\x\AppData\Local\Temp\WER-25287-0.sysdata.xml
C:\Users\x\AppData\Local\Temp\WER81AD.tmp.version.txt

Read our privacy statement:
Microsoft Online Crash Analysis
---------
Plus second error ...
Superfetch has stopped working

 

[SCSIraidGURU]

4e could be overclocking issue or other memory issues. Do you get it alot?

 

[panais]

4e could be overclocking issue or other memory issues. Do you get it alot?

Yes.
I dont have any hardware overclocking

 

[panais]

And today this error happened again...

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1032

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80001E8DD25
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini011009-03.dmp
C:\Users\x\AppData\Local\Temp\WER-23368-0.sysdata.xml
C:\Users\x\AppData\Local\Temp\WER79EF.tmp.version.txt

Read our privacy statement:
Microsoft Online Crash Analysis

 

[acdcfan]

And today this error happened again...

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1032

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80001E8DD25
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini011009-03.dmp
C:\Users\x\AppData\Local\Temp\WER-23368-0.sysdata.xml
C:\Users\x\AppData\Local\Temp\WER79EF.tmp.version.txt

Read our privacy statement:
Microsoft Online Crash Analysis

Please zip mini dumps and attached here

how to find them


My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files. It is these files that we need you to attach to your next posting,
Next time the Blue Screen occurs write down the error code that begins 0x followed by several zeroes and then a number followed by a letter or sometimes it just a number or two letters.

Like this: 0x0000007F

please post you computer details if you can

 

[acdcfan]

And today this error happened again...

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1032

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80001E8DD25
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini011009-03.dmp
C:\Users\x\AppData\Local\Temp\WER-23368-0.sysdata.xml
C:\Users\x\AppData\Local\Temp\WER79EF.tmp.version.txt

Read our privacy statement:
Microsoft Online Crash Analysis

That is almost always caused by a bad hardware driver. When you turn the
computer on start pressing the F8 key. On the Safe mode menu pick Last known
good configuration. Uninstall the driver for whatever the last hardware you
installed was. Perform a System Restore to a time before this.

 

[panais]

And today this error happened again...

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1032

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80001E8DD25
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini011009-03.dmp
C:\Users\x\AppData\Local\Temp\WER-23368-0.sysdata.xml
C:\Users\x\AppData\Local\Temp\WER79EF.tmp.version.txt

Read our privacy statement:
Microsoft Online Crash Analysis

That is almost always caused by a bad hardware driver. When you turn the
computer on start pressing the F8 key. On the Safe mode menu pick Last known
good configuration. Uninstall the driver for whatever the last hardware you
installed was. Perform a System Restore to a time before this.

ok i attached 3 mini dump files (zipped)
ps: how do you open and read dump files?
Thanks
--------
I open dmp file with WinDbg and i get the following:
Microsoft (R) Windows Debugger Version 6.10.0003.233 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\x\Desktop\Mini011009-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 SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`01e53000 PsLoadedModuleList = 0xfffff800`02018db0
Debug session time: Sat Jan 10 02:23:52.177 2009 (GMT+2)
System Uptime: 0 days 1:39:44.000
*********************************************************************
* 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 D1, {fffffa6405cfc10c, 2, 0, fffffa6005cf959f}

Unable to load image \??\C:\Windows\system32\drivers\CrucialSMBusScan.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for CrucialSMBusScan.sys
*** ERROR: Module load completed but symbols could not be loaded for CrucialSMBusScan.sys
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
***** 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 : CrucialSMBusScan.sys ( CrucialSMBusScan+159f )

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

 

[acdcfan]

Please give me time to analyse this...
My vista is 64 bit Ultimate and it seems that I don't have debugging tool.

use this link to learn how to read minimdupm files.
http://forums.majorgeeks.com/showthread.php?t=35246

I am currently using it.

First mini dump error has been caused by CrucialSMBusScan.sys Please scan you computer for spyware, malware using http://www.malwarebytes.org/mbam.php and http://www.freedrweb.com/ also http://hijackthis.de/en and viruses too. First do your memtest
Second minim dump has same file causing the error....

Uninstal Crucials System Scanner and post results

Third mini dump has returned this error

BugCheck A, {0, 2, 1, fffff80001e8dd25}

Probably caused by : Unknown_Image ( PAGE_NOT_ZERO_VISTA )

*** Memory manager detected 1 instance(s) of page corruption, target is likely to have memory corruption.
Process name Utorrent.exe.

Uninstall it and post results

I do hope this will help you