[Kicktar]

Quick bits: Windows 7 64 Bit, AMD Radeon HD 4850 graphics, AMD Phenom II x4 955 3.2 Ghz processor.

Hi, lately I have been experiencing crashes and BSODs, usually while playing intensive games, though lately the crashes have occurred during less intensive tasks such as Evernote. A way I can prevent the crashes from happening usually is to shut down for a few seconds before restarting, but even that isn't guaranteed to fix it. The BSODs don't tend to point to anything consistently, sometimes it's memory_management, othertimes IRQL_not_less_or_equal, and sometimes others.

Here is what I assume is the correct dump file, but I could be wrong: http://www.mediafire...7xl7/MEMORY.zip

Edited by Kicktar, 01 August 2013 - 10:23 PM.

[Advertisements]

Hello Kicktar.... Welcome to
GeeksToGo,


I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.

• Please understand we are all volunteers and we are not here all the time.
• Sometimes it may be a extended amount of time to get back to you. If it has been
  more then 3 days please shoot me a PM and I will try to get back to you quickly
  then.
• Please do the following and supply the requested information as needed. If you
  don't understand my instructions please ask and I will try to explain them
  clearer for you.
• Do not attempt any steps unless instructed or ask before to
  make sure they will not cause any further issues.
• If you are receiving assistance in any other forum site please let us know as there may be conflicting advice given.

Before we can help you need to provide the following so I can start you in the right direction.
Laptop or Desktop?

• If a name brand system then what brand, make and model is the system?
• If custom built then what brand, make and model is the motherboard
• Total memory installed
• Total hard drive capacity and free space
• What steps have you taken so far to resolve the issue

The first thing is a explanation of the bug check code your log shows.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

Since you also mentioned a memory management error then I am going to start with the memory as being the possible culprit of the issue.


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:



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



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:




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.



The following image is the test results area:



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

[rshaffer61]

Hello Kicktar.... Welcome to
GeeksToGo,


I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.

• Please understand we are all volunteers and we are not here all the time.
• Sometimes it may be a extended amount of time to get back to you. If it has been
  more then 3 days please shoot me a PM and I will try to get back to you quickly
  then.
• Please do the following and supply the requested information as needed. If you
  don't understand my instructions please ask and I will try to explain them
  clearer for you.
• Do not attempt any steps unless instructed or ask before to
  make sure they will not cause any further issues.
• If you are receiving assistance in any other forum site please let us know as there may be conflicting advice given.

Before we can help you need to provide the following so I can start you in the right direction.
Laptop or Desktop?

• If a name brand system then what brand, make and model is the system?
• If custom built then what brand, make and model is the motherboard
• Total memory installed
• Total hard drive capacity and free space
• What steps have you taken so far to resolve the issue

The first thing is a explanation of the bug check code your log shows.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

Since you also mentioned a memory management error then I am going to start with the memory as being the possible culprit of the issue.


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:



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



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:




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.



The following image is the test results area:



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

[Kicktar]

My computer is a custom built desktop with an ASUS M4A79XTD EVO motherboard.
I have one stick of memory, 2 Gb, with an SSD for virtual memory.
My boot drive is an SSD with a total 59.5 Gb, 34.6 is free. One of my secondary hard drives is SATA with a total 298 Gb which is basically full with only 707 Mb free. My second secondary hard drive is a total 465 Gb with 134 Gb free.

Though not with the aim to solve the issue, when I got the SSD I installed Windows onto that and have been booting from that ever since. I believe I have tried Memtest before, but I will try that again. I've reinstalled my graphics drivers, since I have had issues with the graphics card before. I believe that's all I've done.

Since I've only got one stick, I'll run Memtest and get back to you after the five to six passes.

Also, just to let you know, the computer seems to have crashed last night while it was asleep.

[rshaffer61]

OK I would like to see that crash notice from last night. Please dothe following and attach the requested logs.


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





Please follow the steps below to enter the Event Viewer program in Vista\Win7. 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.

[Kicktar]

On Fri 8/2/2013 7:00:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080213-13852-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x2017F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88002A4F17F, 0xFFFFF880037783C8, 0xFFFFF88003777C20)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: AVAST Software SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Fri 8/2/2013 7:00:19 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x2017F)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF88002A4F17F, 0xFFFFF880037783C8, 0xFFFFF88003777C20)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: AVAST Software SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Fri 8/2/2013 3:39:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080113-14570-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x8AAAA)
Bugcheck code: 0xD1 (0xFFFFFA7FFFFFFFC8, 0x2, 0x1, 0xFFFFF88001E8AAAA)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 8/2/2013 2:03:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080113-13088-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0xFFFFFA7FD02FFFE0, 0x2, 0x1, 0xFFFFF80002AE67FE)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Wed 7/31/2013 4:02:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-14851-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0xFFFFFA7FD02FFFE0, 0x2, 0x1, 0xFFFFF80002AE67FE)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Wed 7/31/2013 2:18:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-20311-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007A012B8, 0xFFFFF88007A00B10, 0xFFFFFA8003284A70)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Tue 7/30/2013 4:42:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-12136-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0xFFFFFA7FD02FFFE0, 0x2, 0x1, 0xFFFFF80002AA27FE)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 7/30/2013 4:28:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-13338-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D8CEC9, 0xFFFFF88002D00030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 7/30/2013 1:48:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-13837-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20E2F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800554CE2F, 0xFFFFF880034ED6A8, 0xFFFFF880034ECF00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 Tue 7/30/2013 1:41:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-15412-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0xFFFFFA7FD02FFFE0, 0x2, 0x1, 0xFFFFF80002B017FE)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 7/29/2013 4:41:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072913-14461-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002ACFC2A)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 7/27/2013 9:03:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072713-11949-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x3D60C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800554B60C, 0xFFFFF88008409710, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Thu 7/25/2013 4:16:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072513-13634-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000008F58, 0x3030000061198025, 0xFFFFFA8005A001C0)
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 Wed 7/24/2013 4:09:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072413-15054-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFF80044AE1046, 0x0, 0xFFFFF80002AE1840, 0x5)
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 7/23/2013 3:05:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072213-18564-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0xFFFFFA7FD02FFFE0, 0x2, 0x1, 0xFFFFF80002AFB7FE)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

Certainly didn't expect AVAST to be causing issues.


There are the two most recent crashes on Event Viewer.

[rshaffer61]

OK your last two crashes were due to Avast. Is it up to date and are you attached to it?

[Kicktar]

It should be up to date, but I'll switch to Comodo and see if that makes a difference.

Memtest found nothing, so I'll wait and see if the crashes stop now that I'm on Comodo, unless you have anything else for me.

[rshaffer61]

Make sure Avast is disabled if you are switching.

[Kicktar]

Yep, it is.

[Kicktar]

Alright, that didn't work, I've had a couple more crashes since.

On Sun 8/4/2013 12:04:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080313-13696-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC40067488, 0x8000000018004BE2, 0xFFFFF68000096BC9)
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 Sun 8/4/2013 12:04:47 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: 0x1A (0x411, 0xFFFFF6FC40067488, 0x8000000018004BE2, 0xFFFFF68000096BC9)
Error: MEMORY_MANAGEMENT
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.

[rshaffer61]

OK those errors show a possible memory issue so I need you to test the memory using the memtest86 program I linked to as it should be the newest. Follow the instructions completely and let the required passes run. It will take awhile.

[Kicktar]

I did try that when you first asked, but I can try it again. Also, another crash report:

On Mon 8/5/2013 2:15:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-10873-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002AD8BD0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 8/5/2013 2:15:34 PM 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: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002AD8BD0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[rshaffer61]

This is the same as a 7E:

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.

Tell you what I would like you to boot into Safe Mode With Networking and see if the error happens again. Is there something specific you are doing when the error occurs or is it just random?

[Kicktar]

I'm almost always playing some video game, so using safe mode probably won't cause a crash. I have noticed that some mornings it's crashed in the night while it was asleep, so I could put it in safe mode and set it to sleep overnight.

Also, today has been exceptionally good for crashes:

On Mon 8/5/2013 3:19:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-12760-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C00452, 0xFFFFF880029E5E00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 8/5/2013 3:19:27 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: npfs.sys (Npfs+0xB175)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C00452, 0xFFFFF880029E5E00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS 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.

Edited by Kicktar, 05 August 2013 - 09:32 AM.

[rshaffer61]

OK first Microsoft's explanation of this error:

The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
Important Info If You Have Received a STOP Code

If you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact info for Microsoft or your computer manufacturer, Contact Support.

If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.

These actions might prevent an error like this from happening again:

Download and install updates and device drivers for your computer from Windows Update.
Scan your computer for computer viruses.
Check your hard disk for errors.

So lets check the drivers first and then the hard drive.


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.