Windows 7: BSODs even when im on solitaire

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\031611-26098-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82e09000 PsLoadedModuleList = 0x82f51810
Debug session time: Wed Mar 16 19:07:10.468 2011 (GMT-4)
System Uptime: 0 days 0:11:56.450
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8e7044f9, a0983bc0, 0}

Probably caused by : Npfs.SYS ( Npfs!NpCommonSetInformation+d )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8e7044f9, The address that the exception occurred at
Arg3: a0983bc0, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
Npfs!NpCommonSetInformation+d
8e7044f9 8b4a18          mov     ecx,dword ptr [edx+18h]

TRAP_FRAME:  a0983bc0 -- (.trap 0xffffffffa0983bc0)
ErrCode = 00000000
eax=a0983c5c ebx=85ee78f8 ecx=00000006 edx=00000006 esi=85d82030 edi=85ee78f8
eip=8e7044f9 esp=a0983c34 ebp=a0983c3c iopl=0         nv up ei ng nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010297
Npfs!NpCommonSetInformation+0xd:
8e7044f9 8b4a18          mov     ecx,dword ptr [edx+18h] ds:0023:0000001e=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  WG111v2.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8e7045c7 to 8e7044f9

STACK_TEXT:  
a0983c3c 8e7045c7 85d82030 85ee78f8 a0983c5c Npfs!NpCommonSetInformation+0xd
a0983c64 82e454ac 85d82030 85ee78f8 85ee7968 Npfs!NpFsdSetInformation+0x29
a0983c7c 83059dcf 82b09d2c 00000378 03afec04 nt!IofCallDriver+0x63
a0983d18 82e4c43a 00000378 03afec08 03afec18 nt!NtSetInformationFile+0xa3f
a0983d18 77b76344 00000378 03afec08 03afec18 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
03afec20 00000000 00000000 00000000 00000000 0x77b76344


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Npfs!NpCommonSetInformation+d
8e7044f9 8b4a18          mov     ecx,dword ptr [edx+18h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Npfs!NpCommonSetInformation+d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Npfs

IMAGE_NAME:  Npfs.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf23

FAILURE_BUCKET_ID:  0x8E_Npfs!NpCommonSetInformation+d

BUCKET_ID:  0x8E_Npfs!NpCommonSetInformation+d

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

0: kd> lmvm Npfs
start    end        module name
8e6fd000 8e70b000   Npfs       (pdb symbols)          c:\symbols\npfs.pdb\6DCB723DA8DE413BA38C2221A1816ED11\npfs.pdb
    Loaded symbol image file: Npfs.SYS
    Mapped memory image file: C:\Symbols\Npfs.SYS\4A5BBF23e000\Npfs.SYS
    Image path: \SystemRoot\System32\Drivers\Npfs.SYS
    Image name: Npfs.SYS
    Timestamp:        Mon Jul 13 19:11:31 2009 (4A5BBF23)
    CheckSum:         00008C57
    ImageSize:        0000E000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     npfs.sys
    OriginalFilename: npfs.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  NPFS Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.