Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Blue screens and chrome crashes


  • Please log in to reply

#1
DeZiekeNon

DeZiekeNon

    Member

  • Member
  • PipPipPip
  • 134 posts
Dear Geeks,

I have been getting blue screens regularly. A little less than daily. After rebooting my PC didn't crash again. Also chrome often crashed. After refreshing chrome worked fine again.

Today after chrome and also Spotigy and Adblock crashed, I tried to reboot my PC but I got a blue screen multiple times before I was back in Windows.

I collected the blue screen messages I got over time:

- Memory Management
- Page fault in non paged area
- Bad pool header
- Kernell security check failure

Today I got the following BS messages when I tried rebooting my PC:

- DPC_wachtdog_violation
- Driver unloaded without cancelling operations
- 0xc000021a

Can any of you tell me what might cause these crashes/errors?

I'm not sure if this belongs in the Windows 8 subforum or hardware. But since the error messages are Windows 8 messages I put it here.

PC specs:
Motherboard: Asus M4a79T Deluxe (AM3, 790FX)
Processor: AMD Phenom II x4 965 Black Edition (3,4Ghz) (quad-core)
Memory: GeIl 2x2Gb 1600MHz DDR3 Dual Channel kit (4Gb total)
Graphics Card: XFX Radeon HD 6950 2GB DDR5 Dual fan
Harddisk: Western Digital Velociraptor 150Gb (10.000RPM SATAII) + Western Digital Raptor 150Gb (10.000RPM SATA)
DVD Drive: Aopen DVD+RWDVD-RW
Power: Zalman ZM850-HP (850watt)
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Lets see if we can get a little more info on these BSOD's.

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program





Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads
  • 0

#3
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
BlueScreenView report:

==================================================
Dump File : 111513-19000-01.dmp
Crash Time : 15-11-2013 17:58:27
Bug Check String :
Bug Check Code : 0xc000021a
Parameter 1 : fffff8a0`01589580
Parameter 2 : 00000000`00000000
Parameter 3 : ffffffff`c0000428
Parameter 4 : 0000004a`cbcd0530
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16581 (win8_gdr.130410-1505)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\111513-19000-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 275.888
Dump File Time : 15-11-2013 18:01:44
==================================================

==================================================
Dump File : 111513-37143-01.dmp
Crash Time : 15-11-2013 17:50:02
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`0771b520
Parameter 3 : fffff880`0aebc150
Parameter 4 : 00000000`00000000
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+a6520
File Description : DirectX Graphics Kernel
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16583 (win8_gdr.130412-1706)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\111513-37143-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 279.992
Dump File Time : 15-11-2013 17:51:26
==================================================

==================================================
Dump File : 111513-39171-01.dmp
Crash Time : 15-11-2013 17:42:36
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffe8a0`0101c282
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`32ce2d4f
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16581 (win8_gdr.130410-1505)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\111513-39171-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 280.216
Dump File Time : 15-11-2013 17:44:01
==================================================

==================================================
Dump File : 110513-19952-01.dmp
Crash Time : 5-11-2013 22:57:07
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005003
Parameter 2 : fffff700`01080000
Parameter 3 : 00000000`00003eed
Parameter 4 : 00003f0a`00007dfa
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16581 (win8_gdr.130410-1505)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\110513-19952-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 280.272
Dump File Time : 5-11-2013 22:58:19
==================================================

==================================================
Dump File : 110513-30576-01.dmp
Crash Time : 5-11-2013 19:43:02
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`0000000d
Parameter 2 : fffff8a0`0d419090
Parameter 3 : f94fe016`1defc903
Parameter 4 : f94fe006`1defc903
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+12e9
File Description : Microsoft Filesystem Filter Manager
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16384 (win8_rtm.120725-1247)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\110513-30576-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 280.272
Dump File Time : 5-11-2013 19:44:20
==================================================

==================================================
Dump File : 110113-19734-01.dmp
Crash Time : 1-11-2013 9:22:04
Bug Check String :
Bug Check Code : 0x00000139
Parameter 1 : 00000000`00000003
Parameter 2 : fffff801`fd020b60
Parameter 3 : fffff801`fd020ab8
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16581 (win8_gdr.130410-1505)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\110113-19734-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 262.160
Dump File Time : 1-11-2013 9:23:09
==================================================

==================================================
Dump File : 102813-18142-01.dmp
Crash Time : 28-10-2013 20:10:45
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000003
Parameter 2 : fffff8a0`22f2c6f0
Parameter 3 : fffff8b0`22f2c6f0
Parameter 4 : fffff8a0`22f2c6f0
Caused By Driver : tm.sys
Caused By Address : tm.sys+222456f0
File Description : Kernel Transaction Manager Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16384 (win8_rtm.120725-1247)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\102813-18142-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 280.272
Dump File Time : 28-10-2013 20:11:56
==================================================

==================================================
Dump File : 102813-31777-01.dmp
Crash Time : 28-10-2013 19:56:41
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`0000000e
Parameter 2 : fffff8a0`0dd98c50
Parameter 3 : 1787a0fc`c75ea46e
Parameter 4 : 1787a0ec`c75ea46e
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16581 (win8_gdr.130410-1505)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\102813-31777-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 280.272
Dump File Time : 28-10-2013 19:58:01
==================================================

==================================================
Dump File : 102113-24460-01.dmp
Crash Time : 21-10-2013 12:30:43
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffe8a0`0411a998
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`0170cd20
Parameter 4 : 00000000`00000002
Caused By Driver : netbios.sys
Caused By Address : netbios.sys+17a1508
File Description : NetBIOS interface driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16384 (win8_rtm.120725-1247)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\102113-24460-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 280.272
Dump File Time : 21-10-2013 12:32:01
==================================================

==================================================
Dump File : 100413-27892-01.dmp
Crash Time : 4-10-2013 17:42:38
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffea80`0529a3b0
Parameter 2 : 00000000`00000000
Parameter 3 : fffff803`d709e729
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16581 (win8_gdr.130410-1505)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\100413-27892-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 280.104
Dump File Time : 4-10-2013 17:47:52
==================================================

==================================================
Dump File : 100413-28813-01.dmp
Crash Time : 4-10-2013 17:41:01
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffea80`052d9a40
Parameter 2 : 00000000`00000000
Parameter 3 : fffff803`104ad729
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16581 (win8_gdr.130410-1505)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\100413-28813-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 280.104
Dump File Time : 4-10-2013 17:42:21
==================================================

==================================================
Dump File : 100413-27861-01.dmp
Crash Time : 4-10-2013 17:39:23
Bug Check String :
Bug Check Code : 0x00000139
Parameter 1 : 00000000`00000003
Parameter 2 : fffff880`1ec7b290
Parameter 3 : fffff880`1ec7b1e8
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16581 (win8_gdr.130410-1505)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\100413-27861-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 280.272
Dump File Time : 4-10-2013 17:40:43
==================================================

==================================================
Dump File : 100413-30170-01.dmp
Crash Time : 4-10-2013 17:03:52
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffe8a0`13d7f010
Parameter 2 : 00000000`00000000
Parameter 3 : fffff801`eb67ecf0
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16581 (win8_gdr.130410-1505)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\100413-30170-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 280.272
Dump File Time : 4-10-2013 17:05:10
==================================================

==================================================
Dump File : 100413-21964-01.dmp
Crash Time : 4-10-2013 16:55:42
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffea80`039a4248
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`0174fd27
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.2.9200.16581 (win8_gdr.130410-1505)
Processor : x64
Crash Address : ntoskrnl.exe+5a440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\100413-21964-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9200
Dump File Size : 324.800
Dump File Time : 4-10-2013 16:56:51
==================================================
  • 0

#4
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 15-11-2013 16:58:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111513-19000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xC000021A (0xFFFFF8A001589580, 0x0, 0xFFFFFFFFC0000428, 0x4ACBCD0530)
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 Fri 15-11-2013 16:50:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111513-37143-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0xA6520)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800771B520, 0xFFFFF8800AEBC150, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Fri 15-11-2013 16:42:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111513-39171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFE8A00101C282, 0x0, 0xFFFFF80032CE2D4F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 5-11-2013 21:57:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110513-19952-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x3EED, 0x3F0A00007DFA)
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 5-11-2013 18:43:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110513-30576-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x19 (0xD, 0xFFFFF8A00D419090, 0xF94FE0161DEFC903, 0xF94FE0061DEFC903)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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.



On Fri 1-11-2013 8:22:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110113-19734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF801FD020B60, 0xFFFFF801FD020AB8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 28-10-2013 19:10:45 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102813-18142-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A022F2C6F0, 0xFFFFF8B022F2C6F0, 0xFFFFF8A022F2C6F0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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.



On Mon 28-10-2013 18:56:41 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102813-31777-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x19 (0xE, 0xFFFFF8A00DD98C50, 0x1787A0FCC75EA46E, 0x1787A0ECC75EA46E)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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.



On Mon 21-10-2013 11:30:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102113-24460-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8800170CD20)
Bugcheck code: 0x50 (0xFFFFE8A00411A998, 0x0, 0xFFFFF8800170CD20, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 Fri 4-10-2013 16:42:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100413-27892-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFEA800529A3B0, 0x0, 0xFFFFF803D709E729, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




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

14 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Consider 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 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.
  • 0

#5
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK first error is described HERE


Second error Microsoft has a hotfix for located HERE


Before I keep going I want to check a few things.

Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (chose "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, try the Hitachi DFT CD Image version of the software

Thanks to Broni for the instructions






A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#6
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
The first error seems to be caused by third party software. But I don't have a clue which software that would be.

My harddrives passed the test. I used the Western Digital Lifeguard software.

I get an error trying to apply the hotfix:

Posted Image

I have run a Memtest before. I'll do that overnight. Any info on the other errors?
  • 0

#7
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
The first one seems to be a user mode issue as explained below.

The STOP 0xC000021A error occurs when either Winlogon.exe or Csrss.exe fails. When the Windows NT kernel detects that either of these processes has stopped, it stops the system and raises the STOP 0xC000021A error. This error may have several causes. Among them are the following:

Mismatched system files have been installed.
A Service Pack installation has failed.
A backup program that is used to restore a hard disk did not correctly restore files that may have been in use.
An incompatible third-party program has been installed.



The next one has to do with your video and your DX driver which may be out of date or faulty. Try this below and post the screenshots for please.

Download DriverMax and have it scan your system. It will open their website with all the out of date drivers you can update. With the free version you can update only 2 drivers per day so if you have a lot of them it will take a few days to get everything updated. I have been using it for about 4 months now and like it better then any other utility out there for keeping my drivers up to date.
If you want you can post screenshots of all the drivers in the list that need to be updated and I will suggest in what order to get them.
  • 0

#8
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
Posted Image

When I click running without help I get the same message again.

Edited by DeZiekeNon, 15 November 2013 - 01:21 PM.

  • 0

#9
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Right click on the exe file and then click on run as administrator. :confused:
  • 0

#10
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
I got the same message running as administrator but then running without help did work.

Posted Image

Posted Image

Posted Image
  • 0

Advertisements


#11
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK lets see if we can fix things now.
First one to download and install is the smbus controller which is the third one in the list.
Once that is installed then get the video card one which is the first one. Once that is installed make sure you reboot so that the changes will be sure to take affect. BTW it will ask if you want a restore point created and always click yes as this will give you a point to return to if the driver doesn't work. ;)

You will only be able to get 2 a day so we will get more tomorrow. Let me know if a BSOD happens after the reboot.
  • 1

#12
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
I'll go and have some dinner now. I will update the first two updates later tonight and post again. I'll just look up the updates myself so I'm not limited to the maximum of two I get with DriverMax.

Thanks very much for helping so far.

Edited by DeZiekeNon, 15 November 2013 - 01:47 PM.

  • 0

#13
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
No problem and enjoy your dinner. I will wait for your results. Just make sure that the smbus is the first one you do because that is the main chipset that allows everything to identify and work correctly on the motherboard.
  • 1

#14
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
SMBus and graphics drivers installed. What's next?
  • 0

#15
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Now just a matter of using the system and see what happens till we can get all the drivers updated. Those two are the most important at this point and hopefully will help a lot.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP