Windows 7: Random BSODs while playing WoW/TF2, browsing internet.

Tenack · 13 Jan 2012

:x i hope we can figure this out

Tenack · 14 Jan 2012

Alright so, here's an update.

Now, I have a BSOD every 10 minutes or so. PAGE FAULT IN NONPAGED AREA to PFN FILE CORRUPT are two messages I saw. I'm in safe mode with networking right now, and after about an hour in safe mode, I haven't had any problems. So none of the core drivers are the problem I guess.

If all this is is a driver issue, then WHY doesn't the Windows device manager update drivers efficiently? It says they're all up to date but when I download a third party driver scanner it says like 5 are out of date, but since I cannot pay for the program, I cannot automatically update my drivers. I hope they fix this problem in Windows 8.

I read somewhere that you have to uninstall a driver before you install a new one. How does that even work with a graphics and a network driver? I haven't been uninstalling the drivers before I install the new ones. Also does Windows Automatic Update **** with my new drivers because it doesn't recognize them as being up to date since Windows is SO far behind?

Tenack · 15 Jan 2012

Bros?

Lemur · 15 Jan 2012

Hi Tenack,

You don't have to uninstall a driver to install a new one.
Those programs that find missing drivers are often inaccurate at best, and harmful at worst.
Why don't you post another BSOD report for us to analyze.
But before that, please do the following:

In an elevated command prompt, run: sfc /scannow

This link explains the purpose:

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

Also, please run memtest86+. Please let it make at least 7 passes. It's bootable off a CD-Rom:

Memtest86+ - Advanced Memory Diagnostic Tool

Finally, run Windows Drive Verifier:

Driver Verifier - Enable and Disable

If you get a BSOD after running the verifier, immediately repost the bsod report according to the instructions per this forum.

Tenack · 17 Jan 2012

Alright I ran memtest. Passed 7 times. No errors. Ran System File Checker again. Says it fixed corrupted files...again. Ran Driver verifier using the directions provided. Restarted computer and it was working fine for a bit, but then I got a random BSOD again. In addition, my WoW frames seem to hiccup when I move my camera. Which is very odd considering this normally doesn't happen. My latency is also fine.

Here are the new files.

Tenack · 17 Jan 2012

Got another one on boot up. IRQL NOT LESS OR EQUAL

Tenack · 17 Jan 2012

I may resort to simply reinstalling Windows 7. Would this be the best course of action? Thanks

Tenack · 20 Jan 2012

bump

writhziden · 20 Jan 2012

We really ask that you not bump your thread. If you want to make a "bump" a good method is to supply information that might help us. Maybe tell us what steps you have taken since your last response.

Anyway, I will take a look at your .dmp files, see what steps Lemur has helped you with, and get back to you.

writhziden · 20 Jan 2012

Code:


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Tenack\Windows_NT6_BSOD_jcgriff2\011612-26098-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0344f000 PsLoadedModuleList = 0xfffff800`03694670
Debug session time: Mon Jan 16 18:55:28.657 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:46.233
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88008af6e48, fffff88008af66a0, fffff880012e1e3e}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+3458 )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88008af6e48
Arg3: fffff88008af66a0
Arg4: fffff880012e1e3e

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


EXCEPTION_RECORD:  fffff88008af6e48 -- (.exr 0xfffff88008af6e48)
ExceptionAddress: fffff880012e1e3e (Ntfs!NtfsCommonCleanup+0x0000000000003458)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88008af66a0 -- (.cxr 0xfffff88008af66a0)
rax=fffff8a002ffffe0 rbx=fffff8a0033e0010 rcx=fffff8a003000040
rdx=0030002d00300030 rsi=fffff8a0033e0140 rdi=0000000000000004
rip=fffff880012e1e3e rsp=fffff88008af7080 rbp=0000000000000002
 r8=fffff8a0033e03a8  r9=0000000000000008 r10=fffff88008af7670
r11=fffff88008af7488 r12=0000000000000703 r13=0000000000000000
r14=0000000000000000 r15=fffff8a0033e0330
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
Ntfs!NtfsCommonCleanup+0x3458:
fffff880`012e1e3e f6421806        test    byte ptr [rdx+18h],6 ds:002b:0030002d`00300048=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036fe100
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsCommonCleanup+3458
fffff880`012e1e3e f6421806        test    byte ptr [rdx+18h],6

FAULTING_IP: 
Ntfs!NtfsCommonCleanup+3458
fffff880`012e1e3e f6421806        test    byte ptr [rdx+18h],6

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff8800124ecc9 to fffff880012e1e3e

STACK_TEXT:  
fffff880`08af7080 fffff880`0124ecc9 : 0000007f`ffffff00 fffff880`08af76e0 fffff880`08af75d0 00000000`00006000 : Ntfs!NtfsCommonCleanup+0x3458
fffff880`08af7490 fffff800`034d8618 : fffff880`08af75d0 fffff880`00961000 00000000`00000008 fffff880`08af7540 : Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`08af74c0 fffff880`0124ed42 : fffff880`0124ecb0 fffff880`08af76e0 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`08af75a0 fffff880`012eda04 : fffff880`08af7670 fffff880`08af7670 fffff880`08af7670 fffff880`08af76e0 : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`08af7610 fffff800`03971c16 : fffff880`08af7670 fffff980`12640c10 fffff980`12640c10 fffffa80`039bb030 : Ntfs!NtfsFsdCleanup+0x144
fffff880`08af7880 fffff880`01050bcf : fffff980`12640fb0 fffff880`08af7920 fffffa80`06aaba20 fffffa80`06aa9c20 : nt!IovCallDriver+0x566
fffff880`08af78e0 fffff880`0104f6df : fffffa80`057e1b60 fffffa80`057e1b60 fffffa80`04be5d00 fffff980`12640c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`08af7970 fffff800`03971c16 : fffff980`12640c10 00000000`00000002 fffffa80`057e1b60 00000000`00000000 : fltmgr!FltpDispatch+0xcf
fffff880`08af79d0 fffff800`037d3a0f : fffff980`12640c10 fffffa80`0768fb30 00000000`00000000 fffffa80`0785aa30 : nt!IovCallDriver+0x566
fffff880`08af7a30 fffff800`037c3174 : 00000000`00000000 fffffa80`0768fb30 00000000`00000000 fffff800`034d5afc : nt!IopCloseFile+0x11f
fffff880`08af7ac0 fffff800`037c2f31 : fffffa80`0768fb30 fffffa80`00000001 fffff8a0`028742a0 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`08af7b40 fffff800`037c34f4 : 00000000`000007dc fffffa80`0768fb30 fffff8a0`028742a0 00000000`000007dc : nt!ObpCloseHandleTableEntry+0xb1
fffff880`08af7bd0 fffff800`034caed3 : fffffa80`07530060 fffff880`08af7ca0 00000000`028f16e0 00000000`063aba80 : nt!ObpCloseHandle+0x94
fffff880`08af7c20 00000000`7736140a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`063ad218 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7736140a


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsCommonCleanup+3458

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

STACK_COMMAND:  .cxr 0xfffff88008af66a0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_VRF_Ntfs!NtfsCommonCleanup+3458

BUCKET_ID:  X64_0x24_VRF_Ntfs!NtfsCommonCleanup+3458

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Tenack\Windows_NT6_BSOD_jcgriff2\011612-19047-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0340f000 PsLoadedModuleList = 0xfffff800`03654670
Debug session time: Sun Jan 15 23:32:33.759 2012 (UTC - 7:00)
System Uptime: 0 days 11:50:44.036
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880044add41, fffff88003cbd898, fffff88003cbd0f0}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DMMVIDPNPRESENTPATH::IsValidContentScaling+75 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880044add41, The address that the exception occurred at
Arg3: fffff88003cbd898, Exception Record Address
Arg4: fffff88003cbd0f0, Context Record Address

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


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

FAULTING_IP: 
dxgkrnl!DMMVIDPNPRESENTPATH::IsValidContentScaling+75
fffff880`044add41 837b7001        cmp     dword ptr [rbx+70h],1

EXCEPTION_RECORD:  fffff88003cbd898 -- (.exr 0xfffff88003cbd898)
ExceptionAddress: fffff880044add41 (dxgkrnl!DMMVIDPNPRESENTPATH::IsValidContentScaling+0x0000000000000075)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000747770
Attempt to read from address 0000000000747770

CONTEXT:  fffff88003cbd0f0 -- (.cxr 0xfffff88003cbd0f0)
rax=0000000000000000 rbx=0000000000747700 rcx=fffffa8005f32010
rdx=fffff880045a66d0 rsi=fffffa8005f32010 rdi=fffff800047c0080
rip=fffff880044add41 rsp=fffff88003cbdad8 rbp=fffffa8004af5010
 r8=0000000005e2f7f7  r9=000000000000000f r10=0000000000000000
r11=fffff88003cbdac0 r12=0000000000000000 r13=fffffa80064fd010
r14=0000000000000000 r15=fffffa8005f735b0
iopl=0         nv up ei pl zr ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010256
dxgkrnl!DMMVIDPNPRESENTPATH::IsValidContentScaling+0x75:
fffff880`044add41 837b7001        cmp     dword ptr [rbx+70h],1 ds:002b:00000000`00747770=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000747770

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036be100
 0000000000747770 

FOLLOWUP_IP: 
dxgkrnl!DMMVIDPNPRESENTPATH::IsValidContentScaling+75
fffff880`044add41 837b7001        cmp     dword ptr [rbx+70h],1

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 0000000000000460 to fffff880044add41

STACK_TEXT:  
fffff880`03cbdad8 00000000`00000460 : fffff880`03cbdce8 00000000`0000000d 00000000`00000026 fffff880`03cbdb44 : dxgkrnl!DMMVIDPNPRESENTPATH::IsValidContentScaling+0x75
fffff880`03cbdb08 fffff880`03cbdce8 : 00000000`0000000d 00000000`00000026 fffff880`03cbdb44 fffff880`03cbdb5c : 0x460
fffff880`03cbdb10 00000000`0000000d : 00000000`00000026 fffff880`03cbdb44 fffff880`03cbdb5c fffff880`03cbdb90 : 0xfffff880`03cbdce8
fffff880`03cbdb18 00000000`00000026 : fffff880`03cbdb44 fffff880`03cbdb5c fffff880`03cbdb90 fffff880`03cbdb80 : 0xd
fffff880`03cbdb20 fffff880`03cbdb44 : fffff880`03cbdb5c fffff880`03cbdb90 fffff880`03cbdb80 00000026`fffffac2 : 0x26
fffff880`03cbdb28 fffff880`03cbdb5c : fffff880`03cbdb90 fffff880`03cbdb80 00000026`fffffac2 00000000`0000000d : 0xfffff880`03cbdb44
fffff880`03cbdb30 fffff880`03cbdb90 : fffff880`03cbdb80 00000026`fffffac2 00000000`0000000d fffffa80`05002000 : 0xfffff880`03cbdb5c
fffff880`03cbdb38 fffff880`03cbdb80 : 00000026`fffffac2 00000000`0000000d fffffa80`05002000 00000003`00000a00 : 0xfffff880`03cbdb90
fffff880`03cbdb40 00000026`fffffac2 : 00000000`0000000d fffffa80`05002000 00000003`00000a00 00000026`00000460 : 0xfffff880`03cbdb80
fffff880`03cbdb48 00000000`0000000d : fffffa80`05002000 00000003`00000a00 00000026`00000460 fffffa80`07932010 : 0x26`fffffac2
fffff880`03cbdb50 fffffa80`05002000 : 00000003`00000a00 00000026`00000460 fffffa80`07932010 00000000`00000000 : 0xd
fffff880`03cbdb58 00000003`00000a00 : 00000026`00000460 fffffa80`07932010 00000000`00000000 fffff880`054c0000 : 0xfffffa80`05002000
fffff880`03cbdb60 00000026`00000460 : fffffa80`07932010 00000000`00000000 fffff880`054c0000 00000000`007477d3 : 0x3`00000a00
fffff880`03cbdb68 fffffa80`07932010 : 00000000`00000000 fffff880`054c0000 00000000`007477d3 00000000`00000026 : 0x26`00000460
fffff880`03cbdb70 00000000`00000000 : fffff880`054c0000 00000000`007477d3 00000000`00000026 00000000`12a65000 : 0xfffffa80`07932010


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgkrnl!DMMVIDPNPRESENTPATH::IsValidContentScaling+75

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa

STACK_COMMAND:  .cxr 0xfffff88003cbd0f0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgkrnl!DMMVIDPNPRESENTPATH::IsValidContentScaling+75

BUCKET_ID:  X64_0x7E_dxgkrnl!DMMVIDPNPRESENTPATH::IsValidContentScaling+75

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

If you are overclocking anything, please stop.

Your first crash was caused by the file system device driver. This usually indicates file system errors on the disk. It can also be due to Memory problems (appears to be ruled out, but one more test to run)... Drivers... corrupted SCSI or IDE Drivers... System file corruption...
- When you ran SFC, did you run it three times? It sometimes takes three times to fix all errors. If you continue to get errors when running a fourth time, let us know and we can follow further steps.
- Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log This will fix any file system errors in the NTFS file system, hopefully fixing the driver related crash.
- In case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. This you may want to run overnight since it takes a long time to complete (run an hour before bed tonight and check before going to sleep that it is still running).
- An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. Run Driver Verifier
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
Your second crash was related to DirectX and possibly your graphics card. Disable Driver Verifier before proceeding to the next steps.
- Follow the steps for Diagnosing basic problems with DirectX. Use the following method for re-installing the display card drivers.
  1. Download the latest drivers for your display card(s)
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Expand Display adapters
  7. Do the following for each adapter (in case you have multiple display cards)
    Right click the adapter
    
    Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    
    Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  8. Restart your computer after uninstalling drivers for all display cards
  9. Install the latest driver for the display cards once Windows starts
  Alternatively:
  1. Login as an adminstrative user
  2. Download the latest drivers for your display card(s)
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Expand Display adapters
  8. Do the following for each adapter (in case you have multiple display cards)
    Right click the adapter
    
    Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    
    Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  9. Restart your computer after uninstalling drivers for all display cards
  10. Install the latest driver for the display cards once Windows starts
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net and |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems.

Thanks to Dave76 for help understanding possible causes.