BSOD problems (Various types usually during browsing/gaming)

Page 1 of 3 123 LastLast

  1. Posts : 12
    Windows 10 x64
       #1

    BSOD problems (Various types usually during browsing/gaming)


    Hello all,

    I upgraded recently to Windows 10, my computer has always had some random BSOD problems but now it's definitely worse, it used to be only while watching videos (on windows media player) then occasionally on gaming,

    Now it even happens while browsing and the errors vary from one type to the other, no real constant. I read a bit online and I tried doing a verifier check but my CPU went into a blue screen bootloop so that didn't really solve my problem (had to reopen in safe mode and undo the colossal mess that was)

    Not sure where else to go from there. I followed the guidelines and have uploaded a zip of the debug log, I sure hope that will give a good starting point...

    Gregg
      My Computer


  2. Posts : 14,903
    Windows 10 Pro
       #2

    Hi gregg141,

    Welcome to the 10forums.

    As you speak, there are quite some different crashes.
    However, some of them are caused by the same.
    Please follow instructions below for some diagnostics tests and update your USB driver from Citrix and clean install the AMD video drivers.

    Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD




    Diagnostics Test

     HDD & SSD TEST


    Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums

    Note   Note
    Do not run SeaTools on an SSD as the results will be invalid.


    Run chkdsk Disk Check - Windows 7 Help Forums




    Diagnostic Test

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.


    The hard drive
    Code:
    STACK_TEXT:  
    ffffd001`3443a3c8 fffff802`4fd9b4aa : 00000000`000000de 00000000`00000002 ffffc001`df0a7fe8 ffffc001`dc6b3e60 : nt!KeBugCheckEx
    ffffd001`3443a3d0 fffff802`4fc820d0 : ffffd001`3443a600 ffffe000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x285aa
    ffffd001`3443a490 fffff802`4fce2ebe : 00000000`02ed0000 00000000`02ed0000 00000000`00000000 00000000`00000000 : nt!CcPurgeCacheSection+0xc8
    ffffd001`3443a500 fffff802`4fce2cbb : ffffe000`fe948920 00000000`02ed0000 ffffe000`00000001 00000000`02ed0000 : nt!CcPurgeAndClearCacheSection+0x72
    ffffd001`3443a5b0 fffff801`6515bed5 : 00000000`02ed0000 00000000`02ed0000 ffffc001`dc0d3150 00000000`00000000 : nt!CcSetFileSizesEx+0x25b
    ffffd001`3443a630 fffff801`6522b18b : 00000000`00000000 ffffd001`3443a731 7fffffff`ffffffff 00000000`00000001 : NTFS!NtfsSetBothCacheSizes+0x5d
    ffffd001`3443a6a0 fffff801`651fc31f : ffffc001`dc0d3150 ffffe000`ffcb7730 ffffc001`dc0d3101 00000000`00000000 : NTFS!NtfsDeleteAllocation+0x2a3
    ffffd001`3443a780 fffff801`651f6306 : ffffd001`36270670 ffffc001`dc0d3001 ffffc001`dc0d3150 00000000`00000001 : NTFS!NtfsDeleteAllocationFromRecord+0x13f
    ffffd001`3443a830 fffff801`65233d5a : ffffc001`dc0d3010 ffffe000`fec83680 00000000`00000705 ffffc001`dc0d3150 : NTFS!NtfsDeleteFile+0x3ca
    ffffd001`3443ab00 fffff801`65232589 : ffffd001`3626fb30 ffffe000`fed3bbd0 ffffd001`36270608 ffffe000`fec83680 : NTFS!NtfsCommonCleanup+0x17aa
    ffffd001`3443af50 fffff802`4fd66e47 : ffffd001`36270608 000000fb`7644f218 00000000`00000000 00000000`00000000 : NTFS!NtfsCommonCleanupCallout+0x19
    ffffd001`3443af80 fffff802`4fd66e0d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
    ffffd001`36270470 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
    The graphics drivers
    Code:
    SYMBOL_NAME:  dxgkrnl!DXGGLOBAL::DestroySyncObject+90
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgkrnl
    
    IMAGE_NAME:  dxgkrnl.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  55fa5392
    
    IMAGE_VERSION:  10.0.10240.16515
    For the 0x1A(MEMORY_MANAGEMENT), 0x4E(PFN_LIST_CORRUPT) and
    Code:
    Probably caused by : memory_corruption
    Please fill in your system specs
    Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.
    How to fill in your system specs:

      My Computers


  3. Posts : 12
    Windows 10 x64
    Thread Starter
       #3

    Alright,

    So I followed the steps, it had to do a few driver updates, I ran a full memtest for 8 passes no errors, windows 10 said no checkdisk was required so I skipped that step but I still ran the Seatools test and it found no errors.

    I will see if updating the drivers was the required fix. I'll work on posting the setup but I'm not even sure if I know what are the exact pieces (built this PC 10 years ago...)

    Will keep informed if this fixed the issue or not
      My Computer


  4. Posts : 12
    Windows 10 x64
    Thread Starter
       #4

    Alright,

    apologies for the double post, this morning I got up, turned the computer on from sleep and had a memory management BSOD.

    I'm open to new options!!
      My Computer


  5. Posts : 14,903
    Windows 10 Pro
       #5

    Old drivers that need updating/verification
    Code:
    dot4usb	Tue Jul 14 02:00:20 2009		dot4usb.sys // Windows
    P17	Mon Aug 03 13:11:59 2009	P17.sys // Creative
    nvmf6264		Thu Apr 21 00:49:36 2011	nvmf6264.sys // Nvidia
    Dot4Prt	Thu Aug 02 19:35:46 2012	Dot4Prt.sys // Windows
    Dot4		Mon Aug 06 19:01:00 2012	Dot4.sys // Windows
    nvstor	Mon Apr 21 20:34:03 2014	nvstor.sys // Nividia
    Creative
    Nvidia





    Diagnostics Test

     System File Check


    Please try following:
    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again

    If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
      My Computers


  6. Posts : 12
    Windows 10 x64
    Thread Starter
       #6

    The scan found no errors through cmd prompt...

    Ok so I spent quite a while updating drivers, got most of them updated but for the life of me I can't seem to update the following 2 (based on the TweakBit scan...)

    PCI Express Root Complex v15.201.0.0000 (by AMD), what I have is the standard 2006 installed it seems.
    and
    Texas Instruments 1394OHCI Compliant Host Controller v2.0.3.14 (Point Grey Research), also have the standard 2006 version

    I tried going into device manager to update both via there but Windows seems to say that that's I have the latest version, but I think I got the rest of the old ones.

    Will reply back to this thread if (hopefully if and not when) I BSOD again

    Thanks!
      My Computer


  7. Posts : 12
    Windows 10 x64
    Thread Starter
       #7

    Well that sucks for me,

    Just woke the PC from sleep and was hit with the IRQL not less or equal bsod.

    I'm at my wits end on this one...
      My Computer


  8. Posts : 14,903
    Windows 10 Pro
       #8

    If you would run the BSOD tool and upload the new zip, I might find something :)
      My Computers


  9. Posts : 12
    Windows 10 x64
    Thread Starter
       #9

    Alright here it is,

    Didn't know that it should be posted every time :)

    Thanks for your time!
      My Computer


  10. Posts : 14,903
    Windows 10 Pro
       #10

    For example, if you post for the first 5 a zip, but later receive another few crashes occur and don't do anything you can tell me how we are able to help.

    There is a read error.
    Stress the drivers to find the bad ones, the memory has been ruled out.
    Note   Note
    No drivers have been updated!!! Update them to minimalize the cause!!

    Code:
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: ffffe001a9d1f8f8, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8000ae53bd1, address which referenced memory



    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computers


 

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

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




Windows 10 Forums