Blue screen of death

Tombstone_actual

Reputable
Jun 13, 2014
41
0
4,530
--------------------------------------------------------------------------------
Welcome to WhoCrashed (Professional Edition) v 4.01
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Click the Analyze Local button to analyze this computer or the Analyze Remote button for a computer on the network...



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: SOURAV-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 8551714816 total
VM: 2147352576, free: 2001195008




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 8/30/2014 6:54:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-14648-01.dmp
uptime: 01:20:28
This was probably caused by the following module: win32k.sys (win32k!memset+0x863)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000144283, 0xFFFFF8800959B060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 8/30/2014 6:54:13 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 01:20:28
This was probably caused by the following module: win32k.sys (win32k!HmgLockEx+0xA3)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000144283, 0xFFFFF8800959B060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 8/24/2014 7:24:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082414-18361-01.dmp
uptime: 03:49:54
This was probably caused by the following module: win32k.sys (win32k!memset+0x863)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000134283, 0xFFFFF8800D613060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



PLEASE WILL SOMEONE TELL ME THE MEANING OF THIS REPORT? THANKS IN ADVANCE
 
Solution
start by booting off a windows CD and delete the file located here:
c:\windows\system32\fntcache.dat

reason: microsoft released a update that caused a bugcheck in wind32k.sys if you have a corrupte font cache file.
(most often the bad file is located where I indicated)
the bugcheck does not occur until you actually reboot the system after a shutdown. (does not occur with waking from sleep)

there can be other causes (virus corruption of the win32k.sys file and certain hacks) but delete the .dat file and reboot and see if your machine is ok.
start by booting off a windows CD and delete the file located here:
c:\windows\system32\fntcache.dat

reason: microsoft released a update that caused a bugcheck in wind32k.sys if you have a corrupte font cache file.
(most often the bad file is located where I indicated)
the bugcheck does not occur until you actually reboot the system after a shutdown. (does not occur with waking from sleep)

there can be other causes (virus corruption of the win32k.sys file and certain hacks) but delete the .dat file and reboot and see if your machine is ok.
 
Solution