BSOD once every two days, error 0x0000001E

[kevawo]

Processor: AMD Fx-8120 Eight-Core Processor 3.10GHz
RAM: 16.0 GB
System type: Windows 7 Ultimate x64bit
GPU: Nvidia GeForce GTX 670

The PC is about two weeks old. I have attached the .dmp files attached.
The error I am receiving is titled 0x0000001E.

Please help. Thank you in advance.

 

[kevawo]

Also, here is some more information along with a attached .xml file.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80004478C0D
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

 

[DMHolt57]

Check this thread...
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[kevawo]

Thanks for your response, I have done a sfc /scannow in Windows 7 cmd.exe.

It says: Windows Resource Protection did not find any integrity violations.

 

[kevawo]

I have also ran a chkdsk and uploaded the file here. Not sure what the F parameter missing means but overall there has been no problems found.

 

[kevawo]

Hey there, after a whole week, I haven't gotten a BSOD 1E until just now. But this time, it's not the 1E, it's 7F along with a bunch of others. I have attached files below using the SF diag tool. Please help me find out what's wrong with my comp! Thanks in in advance!

 

[kevawo]

I have just received my second BSOD within a few hours. This time it's an D1 error. I have attached the minidump below please help!!

 

[kevawo]

Since I haven't a response from anyone else other than DMHolt57, I have found a tool called WhoCrashed to help read BSOD minidump files. It turns out that most of my BSOD's come from the following:

[FONT=Segoe UI, Arial]On Tue 7/31/2012 1:06:09 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]nvlddmkm.sys[/FONT] (nvlddmkm+0xF3BB7)
Bugcheck code: 0xD1 (0x225500001FBB, 0x2, 0x1, 0xFFFFF88013D9ABB7)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: [FONT=Segoe UI, Arial]NVIDIA Windows Kernel Mode Driver, Version 304.79 [/FONT]
company: [FONT=Segoe UI, Arial]NVIDIA Corporation[/FONT]
description: NVIDIA Windows Kernel Mode Driver, Version 304.79
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 304.79 , NVIDIA Corporation).
Google query: [FONT=Segoe UI, Arial]nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT][/FONT]

and

[FONT=Segoe UI, Arial]On Mon 7/30/2012 2:13:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073012-23649-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF8000476F09B)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft? Windows? Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 which cannot be identified at this time[/FONT]

I have checked my Nvidia driver for an update using a program called Driver Genius and it says I have the most updated Nvidia driver, so I would like assistance on that.

As for the [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT], I have no clue as to where I should go from there.

Please advice, thank you in advance.

 

[kevawo]

I have downgraded the Nvidia driver to a more stable version because there seemed to have been a miss match between the actual most updated driver and the one stated above. The one stated above seemed to be in beta testing.

This morning, I came across two different BSOD's each relating to a different driver

[FONT=Segoe UI, Arial]On Thu 8/2/2012 1:48:27 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]sptd.sys[/FONT] (sptd+0x4B5FC)
Bugcheck code: 0xD1 (0xFFFFFA7F9ED222E0, 0x2, 0x1, 0xFFFFF88000F08C75)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\sptd.sys
product: [FONT=Segoe UI, Arial]SCSI Pass Through Direct[/FONT]
company: [FONT=Segoe UI, Arial]Duplex Secure Ltd.[/FONT]
description: SCSI Pass Through Direct Host
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.
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: sptd.sys (SCSI Pass Through Direct Host, Duplex Secure Ltd.).
Google query: [FONT=Segoe UI, Arial]sptd.sys Duplex Secure Ltd. DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT][/FONT]

and

[FONT=Segoe UI, Arial]On Thu 8/2/2012 1:48:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-21060-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]volmgr.sys[/FONT] (volmgr+0x2C75)
Bugcheck code: 0xD1 (0xFFFFFA7F9ED222E0, 0x2, 0x1, 0xFFFFF88000F08C75)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\volmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft? Windows? Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Volume Manager 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 which cannot be identified at this time. [/FONT]

Please advice as to how I should proceed, thank you very much.