Windows vista crashes but not always followed by Blue Screen.

Anonymous777
Anonymous777 Member Posts: 4 New User

Hi everyone, I play games such as World of Warcraft, Guild Wars 2, and Starcraft 2. About 2 months ago, I started having problems when every time I'd get on ANY games like I just mentioned, it would completely shut down my computer. No shut down screen and very rarely a blue screen. Sometimes I would turn the computer back on and it would be a blue screen and I would be asked to run start up repair. Most of the time there was no blue screen or start up repair, it started normally. I searched the web for a long time and got 3 answers. It was either overheating, not getting enough power, or the display driver was outdated. I have checked all 3 and they are not the problem. I found a program called "WhoCrashed" which Analyzes my Crash Dumps. Below is what it told me after 2 crashes playing World of Warcraft for about 4 minutes each time.

 

 

 

 

 

 

 

 

Crash dump directory:  C:\Windows\Minidump Crash dumps are enabled on your  computer. On  Wed 7/17/2013 6:15:39 PM GMT your computer crashed crash dump file:  C:\Windows\Minidump\Mini071713-01.dmp This was probably caused by the  following module: ntoskrnl.exe (nt+0xAD07B) Bugcheck code: 0xC000021A  (0xFFFFFFFF8C83EE48, 0x0, 0xFFFFFFFFC0000001, 0x10037C) 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.
On Wed 7/17/2013 6:15:39 PM GMT your computer  crashed crash dump file: C:\Windows\memory.dmp This was probably  caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x1E) Bugcheck code:  0xC000021A (0xFFFFFFFF8C83EE48, 0x0, 0xFFFFFFFFC0000001, 0x10037C) Error: STATUS_SYSTEM_PROCESS_TERMINATED 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.
On  Wed 7/17/2013 2:58:50 AM GMT your computer crashed crash dump file:  C:\Windows\Minidump\Mini071613-01.dmp This was probably caused by the  following module: ntoskrnl.exe (nt+0xAD07B) Bugcheck code: 0xC000021A  (0xFFFFFFFF8AF54980, 0x0, 0xFFFFFFFFC0000001, 0x10037C) 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.


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

Answers

This discussion has been closed.