BSOD's lately just doing normal tasks

[Direwolf12]

Hello everyone! I ran across the site hoping that I could maybe get some help with the BSOD I've been getting lately. I just reinstalled my whole computer and updated all my drivers etc.

I have Windows 7 64 bit Professional, 16 gigs of vengeance ram ddr3, i5 2500k 3.30ghz not oc'd, Gigabyte Radeon 7870 2gb gpu, Corsair 850 watt power supply, and a Gigabyte X68XP-UD4 Motherboard. If you need further description I have it all posted in my profile. Also once my wishlist on newegg goes public i'll post that link.

All of the hardware is brand new from Newegg and I just reinstalled Windows 7 yesterday and updated all my drivers. The only thing that is not up to date would be my BIOS which is a version behind. The Blue screens happen just out of the blue I could be gaming or just doing normal tasks like watching videos in youtube. They seem to mainly happen when I'm alt tabbed out of a game looking at website.

This BSOD I'll be posting is where I was watching a live stream of a game and it just popped up. I don't have the other Blue screen logs.

I've uploaded the perf check and the BSOD that occurred. Thanks for your help

 

[Direwolf12]

If you need anymore info just let me know! I want to solve this ASAP gets old not knowing what causes these BSOD's

 

[Direwolf12]

I did the memory diagnostic built in Windows over night and it didn't come up with any problems. I'll probably try Memtest tonight, but I'm not sure where to begin with that I'll have to look around the forums. Just wanted to update everyone. Thanks.


Also ran scandisk for any HD errors and nothing showed up.

 

[Direwolf12]

Running a memtest now on one stick of ram and will be doing the other whenever 7 or 8 passes are done. Anyone have any thoughts?

 

[event3horizon]

well this is the analysis:

BugCheck C5, {fffffaa1110261f8, 2, 1, fffff800031ac617}

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2
Probably caused by : Npfs.SYS ( Npfs!NpAddDataQueueEntry+184 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: fffffaa1110261f8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff800031ac617, address which referenced memory

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2

BUGCHECK_STR:  0xC5_2

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExAllocatePoolWithTag+537
fffff800`031ac617 48895808        mov     qword ptr [rax+8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

DEVICE_OBJECT: fffffa800d084508

TRAP_FRAME:  fffff880092ac4d0 -- (.trap 0xfffff880092ac4d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffaa1110261f0 rbx=0000000000000000 rcx=fffffa80104e0230
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031ac617 rsp=fffff880092ac660 rbp=0000000000001000
 r8=0000000000000000  r9=fffff80003208710 r10=fffff80003208588
r11=fffff880092ac7f8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExAllocatePoolWithTag+0x537:
fffff800`031ac617 48895808        mov     qword ptr [rax+8],rbx ds:fffffaa1`110261f8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003080769 to fffff800030811c0

STACK_TEXT:  
fffff880`092ac388 fffff800`03080769 : 00000000`0000000a fffffaa1`110261f8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`092ac390 fffff800`0307f3e0 : 00000000`0000000f fffffa80`0c95d000 fffff880`00800000 fffff800`03208710 : nt!KiBugCheckDispatch+0x69
fffff880`092ac4d0 fffff800`031ac617 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00040001 : nt!KiPageFault+0x260
fffff880`092ac660 fffff800`03094516 : 00000000`00000000 00000000`00000108 fffff8a0`0ed90af0 00000000`00000000 : nt!ExAllocatePoolWithTag+0x537
fffff880`092ac750 fffff880`02c2dd1c : 00000000`00000020 00000000`00000000 fffffa80`0d0843f0 000f0007`00000000 : nt!ExAllocatePoolWithQuotaTag+0x56
fffff880`092ac7a0 fffff880`02c3248d : fffff880`092ac8e0 fffff8a0`0ecad7c8 00000000`073fcb00 fffff800`00000001 : Npfs!NpAddDataQueueEntry+0x184
fffff880`092ac800 fffff880`02c32151 : fffffa80`0d0844c0 00000000`073fcb00 fffffa80`0cf66500 fffffa80`0d776b50 : Npfs!NpCommonWrite+0x225
fffff880`092ac890 fffff800`03384eab : 00000000`00000001 fffff800`03092141 fffffa80`0e81fd00 00000000`00000020 : Npfs!NpFsdWrite+0x5d
fffff880`092ac900 fffff800`0338f913 : fffffa80`0d084508 00000000`00000000 fffffa80`0db09070 fffff800`031f3e80 : nt!IopSynchronousServiceTail+0xfb
fffff880`092ac970 fffff800`03080453 : fffffa80`0d776b01 00000000`00000000 00000000`00000001 00000000`072c5120 : nt!NtWriteFile+0x7e2
fffff880`092aca70 00000000`74d12e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02ceeae8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74d12e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Npfs!NpAddDataQueueEntry+184
fffff880`02c2dd1c 488bf8          mov     rdi,rax

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  Npfs!NpAddDataQueueEntry+184

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Npfs

IMAGE_NAME:  Npfs.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc114

FAILURE_BUCKET_ID:  X64_0xC5_2_Npfs!NpAddDataQueueEntry+184

BUCKET_ID:  X64_0xC5_2_Npfs!NpAddDataQueueEntry+184

Followup: MachineOwner
---------

Chrome.exe crashed the driver npfs.sys which is some generic windows driver I'm guessing. Now in chrome you usually use audio/video drivers so uninstall and reinstall those and if you've already put newest versions in, get a slightly older version of video driver to see if they are more stable. For example instead of catalyst 12.4, try 12.3 or 12.1.

 

[Direwolf12]

I appreciate the response and I'll try that as well, but I just finished getting the results back from the memtest I just did one 1 stick. It just showed an error which I wrote down and I will post later, but I'm also running the other stick of ram at this time. If I get an error on this stick what do I need to do? Change the slot or what's the best method? I don't think I have any spare ram that's compatiable.


Thanks.

 

[event3horizon]

Well You can reseat them in the same slots, or try to put them in the other slots.

If both turn out with errors, then You'll need to exchange them with good ones (but this is obvious)

 

[Direwolf12]

Thanks for the reply. Yeah I figured that for the most part, but I'm just wanting to know how I can tell if my motherboard or the ram is bad. For example like if all the slots are bad on the motherboard and the sticks of ram are good... I mean is there another way to test the motherboard other than buying new RAM when possibly the ram is good? Like is there an error on memtest that refers that the Motherboard is the culprit?

I don't have any other computers to really test those particular sticks of RAM on so that's the problem.

Thanks again and I'll update everyone on the other stick of ram tonight.

 

[event3horizon]

Bad ram slots on a brand new motherboard is VERY rare but bad RAM sticks is much more common.

 

[Direwolf12]

Okay the 2nd stick of ram ran for 13 hours with no errors while the other came back with 1 error. So I'm guessing I'll try a few more things to make sure and send back the one stick.