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

#16
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
I can do one more driver right now. I got de graphics driver from the AMD website.
  • 0

Advertisements


#17
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
I had a blue screen crash again. The "Page fault in non paged area" one. Also my antivirus software crashed:
Posted Image

It's Dutch. Translation: "Virusscanner initialization failed. Virusprotection is not working correctly".

What now? Install more driver updates?

Also. I don't think the problem has anything to do with my graphics card, but I will replace my HD 6950 with a HD 7970 today. Just FYI.

Edited by DeZiekeNon, 23 November 2013 - 03:46 AM.

  • 0

#18
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

Also. I don't think the problem has anything to do with my graphics card, but I will replace my HD 6950 with a HD 7970 today. Just FYI.


Good that will take the video part out of the equation for sure.

Your latest crash pertains to your AV program. What Av are you using and is it a paid version or a free version?
  • 0

#19
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
It is the paid version of ESET NOD32 Antivirus 7 (latest version and up to date). One of the better AV's out there IMO. I think however that some other problem caused my AV to crash, rather than that my AV itself is the problem.
  • 0

#20
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Can you post a new BlueScreenView and WhoCrashed report please. Also can you do the following.

Please follow the steps below to enter the Event Viewer program in Vista\Win7\Win8. This will give me more information into what is causing your issue. You can get to Event viewer two ways and I will post both for you.


" Go to
" Start
" In the Search box type in Event Viewer in the search box and press Enter
" From this point you can follow from step four from the below method as they will be the same.
Method Two
" Go to Start
" Right click on the Computer Icon and select Manage
" Navigate to the Event Viewer, You will be prompted to accept the action you are going to perform. Click continue
" On the left window pane click on Local and then expand the Windows entry. This will allow you to see every error for the past 24 hours as well as the last 7 days in the right window pane.
" Look for the ones that correspond to the times that your issue occurred.
" If any are found please double click and expand the error. This will open and give you more information on the error.
" Please include that in your next reply.

  • 0

#21
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 22-11-2013 20:28:50 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112213-17752-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF6800803C8B0, 0x0, 0xFFFFF803956903BC, 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 Thu 21-11-2013 19:31:40 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112113-33914-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x75AD, 0x75BF0000EB7A)
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 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.




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

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

BlueScreenView

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

Edited by DeZiekeNon, 23 November 2013 - 09:22 AM.

  • 0

#22
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Ok we have gone slightly off course here so I'm going to ask you to do the memtest86 now.
Next then we will be continuing to update the drivers since the video is what keeps showing up.
  • 0

#23
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
I'll do the memtest later today, since it can take a while.
  • 0

#24
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I agree and if you want you can wait till this evening and let it run over night. That way you will have multiple passes done. Of course if it finds errors then we will know what at least part of the problem is then.
  • 0

#25
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
Agreed
  • 0

Advertisements


#26
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
Update: I have had no BSOD's for a long time now. Hope this will stay this way.
  • 0

#27
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
According to the last logs you posted it has been a month since the last BSOD. That is a pretty good time frame and I would say it looks to be resolved at this point.
  • 0

#28
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

Hi there,

It is technical issue that requires technical expert because who knows what issue it reacts as you told.

Thank You.

:huh: :wacko: :blink: :confused: I thought that is what we have been doing?
  • 0

#29
DeZiekeNon

DeZiekeNon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 134 posts
@ Rshaffer61: I am just as confused..
  • 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