Main Forum > General Computer Support

No, not again

<< < (4/11) > >>

neroilo:

--- Quote from: G-hot on October 26, 2012, 09:41:13 am ---Microsoft stupid tool takes more than 7 hours analyzing memory!!
And We do not marvel if Microsoft Company has removed this stupid tool from its website.

--- End quote ---

Probably you didn't read the relative documentation here:


--- Quote from: Spotlight --- After those 6 tests complete, the tool runs another pass using the same tests and will continue running pass after pass until you exit the software. Typically, though, one pass should be enough to tell whether or not the memory is faulty.
--- End quote ---


--- Quote from: Spotlight ---After each test completes, the tool displays a Succeeded or Failed message.
--- End quote ---

Shane:
Did you have any failed messages from the tester or did you not look? If not you may want to do the memory test one more time, this time just let it do it once :wink:

Shane

Gamezertruth:
no  failed messages and what next?

Shane:
Ok good so we know memory is good.

Now we need to track down what is bad.

Use this program, it will look at the last blue screen dump file and point to what caused it this time
http://www.resplendence.com/whocrashed

Lets go from there :-)

Shane

Gamezertruth:
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 10/24/2012 4:15:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102412-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21925)
Bugcheck code: 0xC000021A (0xFFFFFFFFE2AB1B38, 0xFFFFFFFFC0000005, 0x7C9106C3, 0x11AF36C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This means that an error has occurred in a crucial user-mode subsystem.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Navigation

[0] Message Index

[#] Next page

[*] Previous page