BSOD's and freezing only while in games

Page 1 of 3 123 LastLast

  1. Posts : 13
    Windows 7 Ultimate x64
       #1

    BSOD's and freezing only while in games


    So for the past 2 weeks or so my games have been freezing and an occasional BSOD. Recently it's been getting worse where 5 minutes into any game it freezes instead of freezing every 3-4 hours. I have tried a ton of things including:
    -driver verifier
    -uninstall recent programs/updates
    -chkdsk
    -disk defrag and cleanup
    -running a game from a different hdd (although I have not re-installed windows on a different hdd)
    -swapping sata cables and ports
    -memtest (no errors after 4 hours or so)
    -western digitals hdd checker thing (forgot name)
    -tons of virus scans (bitdefender, malwarebytes, spybot search & destroy)
    -rootkit scans
    -unplugging things from my psu (bluray, cd/dvd, card reader)
    -sfc scan
    -prime95
    -monitored temps of gpu and cpu (all good)

    Here is my system:
    graphics card- http://www.amazon.com/gp/product/B [...] 05_s00_i00
    ram- http://www.amazon.com/gp/product/B [...] 06_s00_i00
    primary hdd- http://www.amazon.com/gp/product/B [...] 06_s00_i00
    monitor- http://www.amazon.com/gp/product/B [...] 02_s01_i00
    mouse- http://www.amazon.com/gp/product/B [...] 02_s00_i01
    keyboard- http://www.amazon.com/gp/product/B [...] 02_s02_i00
    case- http://www.amazon.com/gp/product/B [...] 05_s00_i00
    secondary hdd- http://www.amazon.com/gp/product/B [...] 06_s01_i01
    mobo- http://www.amazon.com/gp/product/B [...] 06_s01_i02
    cpu- http://www.amazon.com/gp/product/B [...] 06_s01_i04
    psu- Ultra LSP 750Pro ATX PSU

    Here is data from 2 recent minidumps.
    If anyone has suggestions that would be awesome. I think I may need to replace my mobo but I'm not sure yet.
    When I ran the wd hdd scanner it came up all clear and everything was fine.
    When I ran chkdsk it came up with a ton of corrupt files, so I tried running a game from a different hard drive and still the same problem. (drive has no OS, I ran it from the same hdd with all game files installed on other hdd)

    anyways here are the minidumps:
    Code:
     
    KERNEL_DATA_INPAGE_ERROR (7a) 
    The requested page of kernel data could not be read in. Typically caused by 
    a bad block in the paging file or disk controller error. Also see 
    KERNEL_STACK_INPAGE_ERROR. 
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185, 
    it means the disk subsystem has experienced a failure. 
    If the error status is 0xC000009A, then it means the request failed because 
    a filesystem failed to make forward progress. 
    Arguments: 
    Arg1: fffff6fc400060f0, lock type that was held (value 1,2,3, or PTE address) 
    Arg2: ffffffffc000000e, error status (normally i/o status code) 
    Arg3: 0000000114119860, current process (virtual address for lock type 3, or PTE) 
    Arg4: fffff88000c1e93c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address) 
     
    Debugging Details: 
    ------------------ 
     
     
    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified. 
     
    DISK_HARDWARE_ERROR: There was error with disk hardware 
     
    BUGCHECK_STR: 0x7a_c000000e 
     
    CUSTOMER_CRASH_COUNT: 1 
     
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT 
     
    PROCESS_NAME: System 
     
    CURRENT_IRQL: 0 
     
    TRAP_FRAME: fffff88003199620 -- (.trap 0xfffff88003199620) 
    NOTE: The trap frame does not contain all registers. 
    Some register values may be zeroed or incorrect. 
    rax=fffff88000c16500 rbx=0000000000000000 rcx=fffffa80074f2050 
    rdx=fffffa80071feb10 rsi=0000000000000000 rdi=0000000000000000 
    rip=fffff88000c1e93c rsp=fffff880031997b8 rbp=fffffa800a37b6f0 
    r8=0000000000000007 r9=fffffa80074f21a0 r10=0000000000000000 
    r11=fffffa80071fecb8 r12=0000000000000000 r13=0000000000000000 
    r14=0000000000000000 r15=0000000000000000 
    iopl=0 nv up ei ng nz ac po cy 
    ataport!ChannelQueryDeviceRelations: 
    fffff880`00c1e93c 4053 push rbx 
    Resetting default scope 
     
    LOCK_ADDRESS: fffff800038d5b80 -- (!locks fffff800038d5b80) 
     
    Resource @ nt!PiEngineLock (0xfffff800038d5b80) Available 
     
    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted. 
     
     
    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted. 
     
    1 total locks 
     
    PNP_TRIAGE: 
    Lock address : 0xfffff800038d5b80 
    Thread Count : 0 
    Thread address: 0x0000000000000000 
    Thread wait : 0x0 
     
    LAST_CONTROL_TRANSFER: from fffff80003747552 to fffff800036d9fc0 
     
    STACK_TEXT: 
    fffff880`03199308 fffff800`03747552 : 00000000`0000007a fffff6fc`400060f0 ffffffff`c000000e 00000001`14119860 : nt!KeBugCheckEx 
    fffff880`03199310 fffff800`03700cbf : fffffa80`06d7e580 fffff880`03199480 fffff800`0390c540 fffffa80`06d7e580 : nt! ?? ::FNODOBFM::`string'+0x36bea 
    fffff880`031993f0 fffff800`036e7589 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffffa80`0e41bf68 : nt!MiIssueHardFault+0x28b 
    fffff880`031994c0 fffff800`036d80ee : 00000000`00000008 fffff880`00c1e93c fffffa80`00000000 fffffa80`071feb10 : nt!MmAccessFault+0x1399 
    fffff880`03199620 fffff880`00c1e93c : fffff880`00c1c4ce 00000000`00000000 fffff880`03199880 fffff800`037d15a0 : nt!KiPageFault+0x16e 
    fffff880`031997b8 fffff880`00c1c4ce : 00000000`00000000 fffff880`03199880 fffff800`037d15a0 fffffa80`06b12ba0 : ataport!ChannelQueryDeviceRelations 
    fffff880`031997c0 fffff800`03a8ffde : 00000000`00000000 00000000`00000000 fffffa80`0a37b6f0 fffff880`030a4180 : ataport!IdePortDispatchPnp+0x22 
    fffff880`031997f0 fffff800`03a9034a : 00000000`00000000 fffffa80`0a37b6f0 fffff800`037d15a0 00000000`00000000 : nt!PnpAsynchronousCall+0xce 
    fffff880`03199830 fffff800`03a92697 : fffff800`038d5940 fffffa80`06b16890 00000000`00000002 00000000`00000600 : nt!PnpQueryDeviceRelations+0xfa 
    fffff880`031998f0 fffff800`03ac2c7c : fffffa80`06b16890 fffffa80`06b10020 fffffa80`06b16890 00000000`00000002 : nt!PipEnumerateDevice+0x117 
    fffff880`03199950 fffff800`03ac3288 : fffff800`038d3500 00000000`00000000 00000000`00000001 fffff800`0393f5e8 : nt!PipProcessDevNodeTree+0x21c 
    fffff880`03199bc0 fffff800`037d3ee7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98 
    fffff880`03199c10 fffff800`036e3641 : fffff800`037d3bc0 fffff800`039cc501 fffffa80`06a29000 fffffa80`06a29040 : nt!PnpDeviceActionWorker+0x327 
    fffff880`03199cb0 fffff800`03970e5a : 00000000`00000000 fffffa80`06a29040 00000000`00000080 fffffa80`06a0cb30 : nt!ExpWorkerThread+0x111 
    fffff880`03199d40 fffff800`036cad26 : fffff880`030a4180 fffffa80`06a29040 fffff880`030af040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a 
    fffff880`03199d80 00000000`00000000 : fffff880`0319a000 fffff880`03194000 fffff880`03199060 00000000`00000000 : nt!KxStartSystemThread+0x16 
     
     
    STACK_COMMAND: kb 
     
    FOLLOWUP_IP: 
    ataport!IdePortDispatchPnp+22 
    fffff880`00c1c4ce eb04 jmp ataport!IdePortDispatchPnp+0x28 (fffff880`00c1c4d4) 
     
    SYMBOL_STACK_INDEX: 6 
     
    SYMBOL_NAME: ataport!IdePortDispatchPnp+22 
     
    FOLLOWUP_NAME: MachineOwner 
     
    MODULE_NAME: ataport 
     
    IMAGE_NAME: ataport.SYS 
     
    DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79293 
     
    FAILURE_BUCKET_ID: X64_0x7a_c000000e_ataport!IdePortDispatchPnp+22 
     
    BUCKET_ID: X64_0x7a_c000000e_ataport!IdePortDispatchPnp+22 
     
    Followup: MachineOwner 
    --------- 
     
    2: kd> .trap 0xfffff88003199620 
    NOTE: The trap frame does not contain all registers. 
    Some register values may be zeroed or incorrect. 
    rax=fffff88000c16500 rbx=0000000000000000 rcx=fffffa80074f2050 
    rdx=fffffa80071feb10 rsi=0000000000000000 rdi=0000000000000000 
    rip=fffff88000c1e93c rsp=fffff880031997b8 rbp=fffffa800a37b6f0 
    r8=0000000000000007 r9=fffffa80074f21a0 r10=0000000000000000 
    r11=fffffa80071fecb8 r12=0000000000000000 r13=0000000000000000 
    r14=0000000000000000 r15=0000000000000000 
    iopl=0 nv up ei ng nz ac po cy 
    ataport!ChannelQueryDeviceRelations: 
    fffff880`00c1e93c 4053 push rbx 
     
     
     
    and the second one: 
    5: kd> !analyze -v 
    ERROR: FindPlugIns 8007007b 
    ******************************************************************************* 
    * * 
    * Bugcheck Analysis * 
    * * 
    ******************************************************************************* 
     
    CRITICAL_OBJECT_TERMINATION (f4) 
    A process or thread crucial to system operation has unexpectedly exited or been 
    terminated. 
    Several processes and threads are necessary for the operation of the 
    system; when they are terminated (for any reason), the system can no 
    longer function. 
    Arguments: 
    Arg1: 0000000000000003, Process 
    Arg2: fffffa8007d2eb30, Terminating object 
    Arg3: fffffa8007d2ee10, Process image file name 
    Arg4: fffff80003998460, Explanatory message (ascii) 
     
    Debugging Details: 
    ------------------ 
     
     
    PROCESS_OBJECT: fffffa8007d2eb30 
     
    IMAGE_NAME: csrss.exe 
     
    DEBUG_FLR_IMAGE_TIMESTAMP: 0 
     
    MODULE_NAME: csrss 
     
    FAULTING_MODULE: 0000000000000000 
     
    PROCESS_NAME: csrss.exe 
     
    EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x. 
     
    BUGCHECK_STR: 0xF4_IOERR 
     
    CUSTOMER_CRASH_COUNT: 1 
     
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT 
     
    CURRENT_IRQL: 0 
     
    STACK_TEXT: 
    fffff880`07b1c0e8 fffff800`03a20822 : 00000000`000000f4 00000000`00000003 fffffa80`07d2eb30 fffffa80`07d2ee10 : nt!KeBugCheckEx 
    fffff880`07b1c0f0 fffff800`039cce0b : ffffffff`ffffffff fffffa80`08f11060 fffffa80`07d2eb30 fffffa80`07d2eb30 : nt!PspCatchCriticalBreak+0x92 
    fffff880`07b1c130 fffff800`0394bf04 : ffffffff`ffffffff 00000000`00000001 fffffa80`07d2eb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176e6 
    fffff880`07b1c180 fffff800`03698253 : fffffa80`07d2eb30 fffff800`c0000006 fffffa80`08f11060 00000000`00ec0e70 : nt!NtTerminateProcess+0xf4 
    fffff880`07b1c200 fffff800`03694810 : fffff800`036e3b7f fffff880`07b1cb78 fffff880`07b1c8d0 fffff880`07b1cc20 : nt!KiSystemServiceCopyEnd+0x13 
    fffff880`07b1c398 fffff800`036e3b7f : fffff880`07b1cb78 fffff880`07b1c8d0 fffff880`07b1cc20 00000000`00ec1a10 : nt!KiServiceLinkage 
    fffff880`07b1c3a0 fffff800`03698642 : fffff880`07b1cb78 00000000`00011b1c fffff880`07b1cc20 00000000`00ec14e8 : nt! ?? ::FNODOBFM::`string'+0x488a4 
    fffff880`07b1ca40 fffff800`036971ba : 00000000`00000000 000007fe`fd60d8c0 00000000`00000001 00000000`00011b1c : nt!KiExceptionDispatch+0xc2 
    fffff880`07b1cc20 00000000`77199c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a 
    00000000`00ec1430 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77199c12 
     
     
    STACK_COMMAND: kb 
     
    FOLLOWUP_NAME: MachineOwner 
     
    FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe 
     
    BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe 
     
    Followup: MachineOwner


    I'm pretty knowledgeable with computers/components/command line/etc, but I'm still newish to troubleshooting and have only done a few things with reading minidump files.

    Thank you in advance for anyone that can help.
    Last edited by Brink; 15 Oct 2012 at 00:51. Reason: code box
      My Computer

  2.   My Computer


  3. Posts : 15,026
    Windows 10 Home 64Bit
       #3

    Sounds like either of your hard drive looks like it's on its way out

    DISK_HARDWARE_ERROR: There was error with disk hardware
    Bug check F4 is usually related to storage/hard drive issues, bug check 7A is also related to hard drive
    Code:
    STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR : Source
    Usual causes:  Memory, Paging file corruption, File system, Hard drive, 
    Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, 
    Missing Service Pack
    Run this tool and delete anything it finds:
    Anti-rootkit utility TDSSKiller

    Uninstall Bit Defender and Spybot S&D.
    Run a full scan with MSE, Microsoft Security Essentials - Free Antivirus for Windows

    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:
    Disk Check

    Hard drive test both short and long with:
    SeaTools for Windows

    Also the DOS version of:
    SeaTools for DOS

    You may also go through these
    Hard Drive Diagnostic Procedure

    and these
    7 Free Hard Drive Testing Software Tools
      My Computer


  4. Posts : 211
    Windows 7 Ultimate x64
       #4

    Windows might be giving problems . . . . .better install a new window in a other HDD and try running from that . . . Use 1 hdd at a time to check the individual one .........
      My Computer


  5. Posts : 13
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Thanks for the input. koolkat, I have ran all of those except for Microsoft Security Essentials. All came up that the HDD was fine except for dskchk came up with a ton of corrupt values. I haven't tried running it again, but I did find out that the games do not crash when I'm running graphics from my MOBO instead of my graphics card.
    I will run another dskchk overnight and post the log here. I'll also try the seatools again and also post the log.

    beret, I was going to try that, but it's kind of funny. I don't have a flash drive big enough or a blank dvd. I need to go to the store tomorrow to get a DVD. But thats my next step as well. I'll post logs and results of what happens tomorrow in the evening.
      My Computer


  6. Posts : 13
    Windows 7 Ultimate x64
    Thread Starter
       #6

    Here is the chkdisk data. I'm running out to the store to grab a dvd to reinstall windows on. I'll post how that goes.

    The type of the file system is NTFS.

    A disk check has been scheduled.
    Windows will now check the disk.

    CHKDSK is verifying files (stage 1 of 5)...
    371456 file records processed. File verification completed.
    331 large file records processed. 0 bad file records processed. 2 EA records processed. 90 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
    494014 index entries processed. Index verification completed.
    0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
    371456 file SDs/SIDs processed. Cleaning up 123 unused index entries from index $SII of file 0x9.
    Cleaning up 123 unused index entries from index $SDH of file 0x9.
    Cleaning up 123 unused security descriptors.
    Security descriptor verification completed.
    61280 data files processed. CHKDSK is verifying Usn Journal...
    34549936 USN bytes processed. Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
    371440 files processed. File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    117565764 free clusters processed. Free space verification is complete.
    CHKDSK discovered free space marked as allocated in the
    master file table (MFT) bitmap.
    CHKDSK discovered free space marked as allocated in the volume bitmap.
    Write failure with status 0xc0000015 at offset 0xaea23d5e00 for 0x200 bytes.
    The second NTFS boot sector is unwriteable.

    Internal Info:
    00 ab 05 00 b0 9a 05 00 4a f1 09 00 00 00 00 00 ........J.......
    72 03 00 00 5a 00 00 00 00 00 00 00 00 00 00 00 r...Z...........
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

    Windows has finished checking your disk.
    Please wait while your computer restarts.
      My Computer


  7. Posts : 15,026
    Windows 10 Home 64Bit
       #7

    Good Luck :)
      My Computer


  8. Posts : 13
    Windows 7 Ultimate x64
    Thread Starter
       #8

    No luck with the Windows install on different HDD. Here is the dump file from the BSOD I received after 5 minutes of gaming. I'm thinking I may need a new MOBO, not sure though.
    Any ideas???



    Code:
     
    3: kd> !analyze -v
    ERROR: FindPlugIns 8007007b
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
     
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8008ea6b30, Terminating object
    Arg3: fffffa8008ea6e10, Process image file name
    Arg4: fffff80002dce460, Explanatory message (ascii)
     
    Debugging Details:
    ------------------
     
     
    PROCESS_OBJECT: fffffa8008ea6b30
     
    IMAGE_NAME: wininit.exe
     
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
     
    MODULE_NAME: wininit
     
    FAULTING_MODULE: 0000000000000000 
     
    PROCESS_NAME: wininit.exe
     
    EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
     
    BUGCHECK_STR: 0xF4_IOERR
     
    CUSTOMER_CRASH_COUNT: 1
     
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
     
    CURRENT_IRQL: 0
     
    STACK_TEXT: 
    fffff880`0a49bb08 fffff800`02e56822 : 00000000`000000f4 00000000`00000003 fffffa80`08ea6b30 fffffa80`08ea6e10 : nt!KeBugCheckEx
    fffff880`0a49bb10 fffff800`02e02e0b : ffffffff`ffffffff fffffa80`070d8b50 fffffa80`08ea6b30 fffffa80`08ea6b30 : nt!PspCatchCriticalBreak+0x92
    fffff880`0a49bb50 fffff800`02d81f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`08ea6b30 0000007f`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176e6
    fffff880`0a49bba0 fffff800`02ace253 : fffffa80`08ea6b30 00000000`c0000006 fffffa80`070d8b50 00000000`00000026 : nt!NtTerminateProcess+0xf4
    fffff880`0a49bc20 00000000`772615da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`026cf9d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772615da
     
     
    STACK_COMMAND: kb
     
    FOLLOWUP_NAME: MachineOwner
     
    FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe
     
    BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe
     
    Followup: MachineOwner
    ---------
    Last edited by Brink; 15 Oct 2012 at 00:52. Reason: code box
      My Computer


  9. Posts : 15,026
    Windows 10 Home 64Bit
       #9

    How old is your current motherboard?
    It could be the graphics card also. Did you try playing with another one?
    Did you lower the settings of the games and see if it still BSoDs?
    How many HDDs are you having actually?
      My Computer


  10. Posts : 13
    Windows 7 Ultimate x64
    Thread Starter
       #10

    I have 2 HDD's. I tried playing with graphics at 1600x900 but it still BSoD'd. I will lower them more and take a look as well. I used to get BSOD's after a new graphics driver install, so I kept an old one that worked and then after about 5 more revisions I finally decided to give the new graphics driver a go. It started BSOD'ing a lot. So then I tried a bunch of things and it still BSOD'd. So I finally installed the old driver again and the BSOD's stopped for about 2 days. And then they came back and are very bad again. I just tried updating my graphics driver again today and no luck. I also ran Memtest tonight for 2 passes and nothing still. My MOBO is fairly new, I will try updating the BIOS tomorrow.
    I bought the MOBO about 1 and a half years ago. I bought the graphics card a year ago.
    I don't have another graphics card, but the on board graphics don't cause BSOD's. I think it's a MOBO compatibility thing with my card, but I'm really not sure. I will see if I can borrow a card tomorrow and see if that fixes anything.
    I have 2 HDDs.
    Tomorrows goals (if I have any time) are to run games at low settings, install a very old graphics driver and try it, and Possibly try flashing BIOS to the beta version (would you recommend this?)
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:24.
Find Us