BSOD randomly from Full Screen Games or Youtube Videos.

[blazeo]

Hey, my computer has been blue screening for quite sometime now, if I were to estimate I would say around 8 months and I get 1-2 blue screen every month I would have to say. I have formatted my computer and re-installed windows around 1-2 months ago to check if it would fix the problem but to no avail. I would generally get these blue screens when I would be playing a full screen game but also it sometimes happens when I would play video games in windowed mode as well. Also, sometimes it would occur when I would full screen or escape a full screen YouTube video.

I have tried updating my video driver as well as explained before formatting my hard drive and re-installing Windows 7 Ultimate x64 but it has still not resolved the issue. I'll attach the dump files and would thank you in advance for any help given.

 

[koolkat77]

Welcome

Following drivers need to be updated to their latest but first uninstall via control panel.

Click on the Start rb: ► Control Panel ► Programs ► Uninstall a program ► Uninstall the Realtek & ATI related stuff.

Delete remnants of their drivers using Driver Sweeper

Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC ► Source: Driver Reference Table

2: kd> lmvm Rt64win7
start             end                 module name
fffff880`04200000 fffff880`04232000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Thu Feb 26 15:04:13 2009 (49A65B0D)
    CheckSum:         0002EB30
    ImageSize:        00032000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

ATI Video driver (remove the Catalyst Control Center and only install the Display Driver) Source ► Driver Reference Table

2: kd> lmvm atikmpag
start             end                 module name
fffff880`02c00000 fffff880`02c5f000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Jul 04 11:10:55 2012 (4FF3D05F)
    CheckSum:         0006086F
    ImageSize:        0005F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Uninstall msi afterburner. The graphics crash is being caused by that program.

Keep us posted

 

[blazeo]

I have now done a clean format of Windows 7 as I had wanted to of my own accord and installed the latest ATI Display Driver without it's Catalyst Control Center, I have not yet installed MSI Afterburner and do not plan to after you have told me it causes Graphical Crashes but although I had done all this I had blue screen recently, here's the latest dump.

Also I have not yet updated the Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC so I'm not sure if that was the problem or not but I'll still give these dump files out just in case. Thank you very much for your help.

 

[koolkat77]

Dump shows lot of NTFS errors. Are you having an SSD by any chance? Did you update to it's latest firmware? How old is it?

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88007fff478, fffff88007ffecd0, fffff880012a8cf9}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCheckExistingFile+f9 )

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

0: 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: fffff88007fff478
Arg3: fffff88007ffecd0
Arg4: fffff880012a8cf9

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


EXCEPTION_RECORD:  fffff88007fff478 -- (.exr 0xfffff88007fff478)
ExceptionAddress: fffff880012a8cf9 (Ntfs!NtfsCheckExistingFile+0x00000000000000f9)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88007ffecd0 -- (.cxr 0xfffff88007ffecd0)
rax=fffff8a00ac06040 rbx=f7fff8a00ac06140 rcx=0000000000000000
rdx=fffffa80085aa060 rsi=0000000000000000 rdi=fffff8a00ac06010
rip=fffff880012a8cf9 rsp=fffff88007fff6b0 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=fffff8800792afa8
r11=fffffa80085aa060 r12=fffffa8009c28010 r13=fffffa800a483010
r14=fffff8800792abe0 r15=fffffa8009ebdd18
iopl=0         nv up ei ng nz na pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010283
Ntfs!NtfsCheckExistingFile+0xf9:
fffff880`012a8cf9 8b8bac000000    mov     ecx,dword ptr [rbx+0ACh] ds:002b:f7fff8a0`0ac061ec=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.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 fffff80002abd0e8
GetUlongFromAddress: unable to read from fffff80002abd198
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsCheckExistingFile+f9
fffff880`012a8cf9 8b8bac000000    mov     ecx,dword ptr [rbx+0ACh]

FAULTING_IP: 
Ntfs!NtfsCheckExistingFile+f9
fffff880`012a8cf9 8b8bac000000    mov     ecx,dword ptr [rbx+0ACh]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff880012a8f13 to fffff880012a8cf9

STACK_TEXT:  
fffff880`07fff6b0 fffff880`012a8f13 : fffff880`0792abe0 fffff8a0`0ac06010 00000000`00000002 fffffa80`07a8da01 : Ntfs!NtfsCheckExistingFile+0xf9
fffff880`07fff740 fffff880`012a4d9f : fffff880`0792abe0 00000000`000007ff 00000000`00000000 00000000`00000024 : Ntfs!NtfsOpenExistingAttr+0x73
fffff880`07fff800 fffff880`012a809f : fffffa80`09c28010 fffffa80`09ebd9c0 fffff8a0`0ac06450 fffff880`00000024 : Ntfs!NtfsOpenAttributeInExistingFile+0x50f
fffff880`07fff990 fffff880`012b8166 : fffffa80`09c28010 fffffa80`09ebd9c0 fffff8a0`0ac06450 00000000`00000701 : Ntfs!NtfsOpenExistingPrefixFcb+0x1ef
fffff880`07fffa80 fffff880`012b5911 : fffffa80`09c28010 fffffa80`09ebd9c0 fffff880`07fffc50 fffff880`07fffca0 : Ntfs!NtfsFindStartingNode+0x5e6
fffff880`07fffb50 fffff880`0121ea3d : fffffa80`09c28010 fffffa80`09ebd9c0 fffff880`0792abe0 fffffa80`085aa000 : Ntfs!NtfsCommonCreate+0x3e1
fffff880`07fffd30 fffff800`02884157 : fffff880`0792ab50 000007fe`ef7d27c0 000007fe`ef7d27c0 00000000`01d8fc70 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`07fffd60 fffff800`02884111 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`0792aa20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsCheckExistingFile+f9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce792f9

STACK_COMMAND:  .cxr 0xfffff88007ffecd0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCheckExistingFile+f9

BUCKET_ID:  X64_0x24_Ntfs!NtfsCheckExistingFile+f9

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

STOP 0x00000024: NTFS_FILE_SYSTEM
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

Upload a screenshot of your hard disk using crystal disk info:

• CrystalDiskInfo - Software - Crystal Dew World
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Make a hard drive test from the hard drive manufacturers website

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Hard drive test both short and long with:

• SeaTools for Windows

Later you may take the DOS pass too:

• SeaTools for DOS

 

[blazeo]

I'm using a standard HDD that I've been using since I first built my computer which was around 2-3 years ago. I have not updated it to it's latest firmware. Below I've attached the screenshot of my hard disk.

View attachment 238348

 

[koolkat77]

Do you mean you have both SSD and HDD?

 

[blazeo]

No I just have 1 HDD that is 500GB and that's it.

 

[koolkat77]

Okay, take the tests on my post #4 and let us know the results.

 

[blazeo]

I have done 2 of the main tests that were recommended on your #4 Post which was the Chkdsk and the SeaTools for Windows. The Chkdsk required a restart but afterwards started it's progress, the results seemed fine, it had said there were no problems and there were no bad sectors from when I checked. Afterwards it had restarted again and showed after the reboot that my drive was clean in which afterwards it booted into Windows.

After that test I had done the SeaTools ones both doing the Short and Long tests getting a pass for both. I still haven't done the DOS test yet but these are results right now.

 

[koolkat77]

Thanks for the update.

You should fill your system specs as well.
__________________

1. Click on User CP on the top right of this page
2. Click on Edit System Spec
3. Fill in your computer specs
   • http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

__________________

 

[blazeo]

New Blue Screen Win32k

Hello, it's been a week since I last followed the tests in the previous posts and it looked like the computer would be fine from then on. Unfortunately I had now just encountered a new blue screen that from what I read on the blue screen has something to do with 'Win32k' I believe? I'll attach the dump file below, I thank you in advance for helping me with my problem once again. The crush occurred when exiting the game called 'Osu!' from full screen onto my desktop.

 

[koolkat77]

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION 
Usual causes:  System service, Device driver, graphics driver, ?memory
BugCheck 3B, {c0000005, fffff9600014408a, fffff880088b9e70, 0}
Probably caused by : win32k.sys ( win32k!GdiThreadCallout+3a )
PROCESS_NAME:  osu!.exe

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
• Guide to using Memtest86+ - Geeks to Go Forums

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

I see that you have no antivirus and let me tell you Spybot is known to slow down and corrupt the system at times. Please uninstall it and use MSE.

• Microsoft Security Essentials - Microsoft Windows

Update and make a full scan with it