Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Annoying: Blue Screen of Death! How to solve?


  • Please log in to reply
13 replies to this topic

#1 danieltbl

danieltbl

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:04:14 PM

Posted 06 December 2014 - 08:14 PM

Hello Bleeping Computer,

 

 

I occasionally get hit by the Blue Screen of Death and it's getting absolutely frustrating.

 

Any kind people there willing to give me a hand with this? 



Thanks in advance ! :)


Edited by hamluis, 07 December 2014 - 12:36 PM.
Moved from Win 7 to Internal Hardware - Hamluis.


BC AdBot (Login to Remove)

 


#2 splico

splico

  • Members
  • 157 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Croatia
  • Local time:09:14 AM

Posted 06 December 2014 - 08:37 PM

Download and install software WhoCrashed and post the logs here.


 "Helpdesk: There is an icon on your computer labeled "My Computer". Double click on it.
User: What's your computer doing on mine?"


#3 danieltbl

danieltbl
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:04:14 PM

Posted 06 December 2014 - 08:42 PM

I'm not too sure which exactly is the log. Is this the right one?

 

System Information (local)

computer name: DANIEL-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: K43SJ, ASUSTeK Computer Inc.
CPU: GenuineIntel Intel® Core™ i3-2330M CPU @ 2.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6418100224 total


 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 12/7/2014 12:26:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120714-33477-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x109 (0xA3A039D8A03645CA, 0xB3B7465EF2B481C4, 0xFFFFF880031705C0, 0x2)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 12/7/2014 12:26:24 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA3A039D8A03645CA, 0xB3B7465EF2B481C4, 0xFFFFF880031705C0, 0x2)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 11/22/2014 5:35:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112314-17097-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000244980, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 11/21/2014 11:25:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112214-16348-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000244980, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 11/21/2014 12:22:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112114-16894-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000244980, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 10/20/2014 11:24:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102014-32916-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41284, 0x1B237001, 0x1B850, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 9/30/2014 5:08:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100114-21855-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x99, 0xA6AA5, 0x2, 0xAA224)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


 

Conclusion

7 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


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 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.



 



#4 splico

splico

  • Members
  • 157 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Croatia
  • Local time:09:14 AM

Posted 06 December 2014 - 08:55 PM

I would first exclude the HDD and memory problems. First try with checkdisk to make sure your HDD is ok and post the result.

 

1 ) Open an elevated command prompt (Run as Administrator )

 

       1218d1239716938t-elevated-command-prompt

 

2 ) In the command console Window, enter CHKDSK C: /R . System will ask permission to schedule a disk scan on next reboot. Press Y and Enter to confirm.

 

3 ) Restart the system and you will see check disk running in a black screen. Wait until it finishes and automatically restarts.

 

To see the Chkdsk log follow these steps:

 

Open The Event Log...
Control Panel (Classic View) -> Administrative Tools -> Event Viewer (3rd choice)

The ChkDsk Log is found in....
Windows Logs (2nd choice on left) -> Application (1st sub-choice)

< NOTE >
This will display a number of information logs in the center pane, many of them from the most recent Windows startup. You will notice the 1-2 hour time difference in events if you rebooted to scan (time spend running chkdsk). 

About half way down the list of logs, look for the item Wininit in the source column. This will contain the log data for the ChkDsk scan prior to the boot. You can use right click to Application then Find option: 
Wininit  and copy paste the result here.

 

Probable couse of this BSOD's is memory corruption. I would suggest after checkdsk you do memtest86+ with single piece of RAM in PC if you have multiple pieces on motherboard and test the memory. After you excluded HDD or memory problem the solution will be quite easy to find.


Edited by splico, 06 December 2014 - 08:56 PM.

 "Helpdesk: There is an icon on your computer labeled "My Computer". Double click on it.
User: What's your computer doing on mine?"


#5 1PW

1PW

  • Members
  • 316 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North of the 38th parallel.
  • Local time:01:14 AM

Posted 06 December 2014 - 08:58 PM

Run:
 
Disk Check (Full Five Stage - not just the lesser three stage): http://www.sevenforums.com/tutorials/433-disk-check.html
 
HDD S.M.A.R.T. Download/Unzip/Run Portable - Standard Edition: http://crystalmark.info/download/index-e.html

Interpret: https://en.wikipedia.org/wiki/S.M.A.R.T.

 

 
Memory Diagnostics (Easier/Good): http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

or

Memory Diagnostics (Harder/Better): http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

 
System File Checker: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

 

Optional - CPUID/HWMonitor: http://www.cpuid.com/softwares/hwmonitor.html

 

The above will take a long time to complete.
 
Please get back to us with the results when you are able.


Edited by 1PW, 07 December 2014 - 12:27 AM.

All viruses are malware but not all malware are viruses and if the malware doesn't self replicate it just isn't a virus.


#6 danieltbl

danieltbl
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:04:14 PM

Posted 06 December 2014 - 09:36 PM

Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          12/7/2014 10:29:20 AM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Daniel-PC
Description:
 
 
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.
 
 
A disk check has been scheduled.
Windows will now check the disk.                         
 
CHKDSK is verifying files (stage 1 of 3)...
  259072 file records processed.                                         
 
File verification completed.
  665 large file records processed.                                   
 
  0 bad file records processed.                                     
 
  0 EA records processed.                                           
 
  59 reparse records processed.                                      
 
CHKDSK is verifying indexes (stage 2 of 3)...
  327188 index entries processed.                                        
 
Index verification completed.
  0 unindexed files scanned.                                        
 
  0 unindexed files recovered.                                      
 
CHKDSK is verifying security descriptors (stage 3 of 3)...
  259072 file SDs/SIDs processed.                                        
 
Cleaning up 597 unused index entries from index $SII of file 0x9.
Cleaning up 597 unused index entries from index $SDH of file 0x9.
Cleaning up 597 unused security descriptors.
Security descriptor verification completed.
  34059 data files processed.                                           
 
CHKDSK is verifying Usn Journal...
  34597304 USN bytes processed.                                            
 
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
 
 307263487 KB total disk space.
 138976444 KB in 142127 files.
    138540 KB in 34060 indexes.
         0 KB in bad sectors.
    369719 KB in use by the system.
     65536 KB occupied by the log file.
 167778784 KB available on disk.
 
      4096 bytes in each allocation unit.
  76815871 total allocation units on disk.
  41944696 allocation units available on disk.
 
Internal Info:
00 f4 03 00 47 b0 02 00 3f fe 04 00 00 00 00 00  ....G...?.......
17 0d 00 00 3b 00 00 00 00 00 00 00 00 00 00 00  ....;...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
 
Windows has finished checking your disk.
Please wait while your computer restarts.
 
Event Xml:
  <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-07T02:29:20.000000000Z" />
    <EventRecordID>18989</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Daniel-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
 
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.
 
 
A disk check has been scheduled.
Windows will now check the disk.                         
 
CHKDSK is verifying files (stage 1 of 3)...
  259072 file records processed.                                         
 
File verification completed.
  665 large file records processed.                                   
 
  0 bad file records processed.                                     
 
  0 EA records processed.                                           
 
  59 reparse records processed.                                      
 
CHKDSK is verifying indexes (stage 2 of 3)...
  327188 index entries processed.                                        
 
Index verification completed.
  0 unindexed files scanned.                                        
 
  0 unindexed files recovered.                                      
 
CHKDSK is verifying security descriptors (stage 3 of 3)...
  259072 file SDs/SIDs processed.                                        
 
Cleaning up 597 unused index entries from index $SII of file 0x9.
Cleaning up 597 unused index entries from index $SDH of file 0x9.
Cleaning up 597 unused security descriptors.
Security descriptor verification completed.
  34059 data files processed.                                           
 
CHKDSK is verifying Usn Journal...
  34597304 USN bytes processed.                                            
 
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
 
 307263487 KB total disk space.
 138976444 KB in 142127 files.
    138540 KB in 34060 indexes.
         0 KB in bad sectors.
    369719 KB in use by the system.
     65536 KB occupied by the log file.
 167778784 KB available on disk.
 
      4096 bytes in each allocation unit.
  76815871 total allocation units on disk.
  41944696 allocation units available on disk.
 
Internal Info:
00 f4 03 00 47 b0 02 00 3f fe 04 00 00 00 00 00  ....G...?.......
17 0d 00 00 3b 00 00 00 00 00 00 00 00 00 00 00  ....;...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
 
Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
  </EventData>
</Event>


#7 danieltbl

danieltbl
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:04:14 PM

Posted 06 December 2014 - 09:38 PM

@1PW 

Is it okay to run those 3 things while following this guy's instructions as well? 



#8 splico

splico

  • Members
  • 157 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Croatia
  • Local time:09:14 AM

Posted 06 December 2014 - 09:46 PM

Memtest86 would be my choice as best, those are good directions how to do it and detect errors. If you have errors follow that procedure with taking out RAM modules and trying to figure which one is defective and throw that one through the window ;). 

System file check could solve your problem if the problem is coused by corrupted Windows files and can't do no harm executing the procedure if memory is not failing.


Edited by splico, 06 December 2014 - 09:54 PM.

 "Helpdesk: There is an icon on your computer labeled "My Computer". Double click on it.
User: What's your computer doing on mine?"


#9 1PW

1PW

  • Members
  • 316 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North of the 38th parallel.
  • Local time:01:14 AM

Posted 06 December 2014 - 09:46 PM

Since @splico posted first let's see how it goes with what was posted first.

 

I am fairly sure we are all working towards the same ends.

 

I'll keep watching this thread as a lurker till later.

 

Everyone: Please have a super good day.


Edited by 1PW, 06 December 2014 - 09:49 PM.

All viruses are malware but not all malware are viruses and if the malware doesn't self replicate it just isn't a virus.


#10 danieltbl

danieltbl
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:04:14 PM

Posted 06 December 2014 - 09:53 PM

 Memory test use only one them and keep it running for some longer time. System file check could solve your problem if the problem is coused by corrupted Windows files and can't do no harm executing the procedure.

 

I'm sorry. I don't quite understand sir :(



#11 splico

splico

  • Members
  • 157 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Croatia
  • Local time:09:14 AM

Posted 06 December 2014 - 09:56 PM

Use this Memtest and guide to find out is your memory problem: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html 


 "Helpdesk: There is an icon on your computer labeled "My Computer". Double click on it.
User: What's your computer doing on mine?"


#12 hamluis

hamluis

    Moderator


  • Moderator
  • 56,106 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:14 AM

Posted 07 December 2014 - 09:20 AM

Just a note...OP only ran 3-stage chkdsk, rather than 5-stage process resulting from chkdsk /r command.

 

Chkdsk From Command Prompt, Win 7 - http://www.bleepingcomputer.com/forums/t/496613/contextmenu-is-causing-explorerexe-to-crash/?p=3067880

 

Louis



#13 danieltbl

danieltbl
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:04:14 PM

Posted 07 December 2014 - 12:07 PM

Tons of errors came up. About 2000+ , Am I suppose to post logs?

P.S: I couldn't test each ram one by one like it says in the 'sevenforums' because I am using a laptop.

 

Sorry for the late reply, just got done with the memtest and the PASS was only at 5 I think. I had to stop it due to emails I need to attend to.



#14 1PW

1PW

  • Members
  • 316 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North of the 38th parallel.
  • Local time:01:14 AM

Posted 08 December 2014 - 10:48 PM

Perhaps splico is getting some well needed rest.

I couldn't test each ram one by one like it says in the 'sevenforums' because I am using a laptop.

To the contrary, your notebook is quite likely to have 8GB total DRAM, on two each similar/identical 4GB SO-DIMMs, installed in two co-located sockets.

Though you may wish to begin by reseating the SO-DIMMs, in their respective sockets, and rerunning the memory diagnostic you chose.

Is this task similar to something you have seen or done before, and feel quite comfortable with?

If not, some useful videos can probably be watched on YouTube if this is something you'd like to see and learn from.

Edited by 1PW, 09 December 2014 - 01:39 AM.

All viruses are malware but not all malware are viruses and if the malware doesn't self replicate it just isn't a virus.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users