Windows 10: BSOD On Just About Every Action

Page 1 of 4 123 ... LastLast
  1.    20 Jul 2016 #1

    BSOD On Just About Every Action


    First off, my specs.
    System Spec

    Computer type:PC/DesktopSystem Manufacturer/Model Number:Cyberpower PCOS:Windows 10CPU:AMD Fx 4300 Quad Core Processor 3800 mhz, 2 cores and 4 logival processorsMotherboard:Gigabyte Technology Co, Base Board, Ultra Durable 4Memory:8 gig RAMGraphics Card(s):Nividia Geoforce GT 730

    The devices I have plugged in are as follows. Cyberpower PC keyboard and mouse, ENHANCE GX-H2 headphones, and a Belkin wireless adapter.

    This imgur link is a picture of screenshots I took from the BlueScreenView app used to read .dmp files (the usual method doesn't work for me)
    https://i.imgur.com/TiqLZAg.png

    As you can see, the drivers causing all this are ntoskrnl.exe, hal.dll, and NTFS.sys. All the information regarding the dmp files themselves are on the picture at the link. If the picture is too small/blurry, open it in Paint or some other photo editing software.

    What I'm doing when the BSOD occurs is varied. Sometimes it's when I log in, sometimes it's when I game, sometime's it's when I browse the internet.

    Some background information on my drivers. I used the Windows Auto Updater and it says I'm updated. I've tried manually updating the graphics card, keyboard, and the wireless adapter but all of them said it was the latest.

    Some help would be appreciated as having 50 BSOD in the time period between 7/13 and 7/20 is not fun.

    Forgot to include the zip file so here you go.
    Attachment 91151
      My ComputerSystem Spec


  2. Posts : 4,998
    Windows 10 Pro X64 15063.138
       20 Jul 2016 #2

    All the dumps I looked at point to microsoft base or kernel files so not likely to be the cause. More likely a non-MS driver problem. Nvidia is often the culprit.

    The driver for your NVIDIA GeForce GT 730 is quite old, version 355.82: 8/25/2015 9:41:50 AM C:\Windows\system32\DRIVERS\nvlddmkm.sys

    Try the latest, see if it fixes the problem: http://www.nvidia.com/download/drive...x/105037/en-us

    Code:
    Version:     368.81  WHQL
    Release Date:     2016.7.14
    Operating System:     Windows 10 64-bit
    Language:     English (US)
    File Size:     343.87 MB
    If that doesn't fix it, then lets try Driver Verifier, see if it shows anything:

    Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to
    PART TWO
    and make sure the correct boxes are checked.

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
      My ComputersSystem Spec

  3.    20 Jul 2016 #3

    Thank you for a speedy response. Downloading the new driver now and will run various programs to see if it helps. If not then I'll move on to Driver Verifier. I will post a response after I use the Driver Verifier or if the updated driver stops the BSOD.
    Thanks again.
      My ComputerSystem Spec

  4.    21 Jul 2016 #4

    Alright. Last night I updated the drivers and it installed fine. Soon after I had another BSOD so I moved on to the Driver Verifier. That also created a BSOD. However, I was not able to log on to disable the Verifier as it would create a BSOD on log in. Sadly, turning it off through the Control Panel was the only way I knew how so I decided to just reset the PC. No biggie, I've only had it a week. After the fact I realized the .dmp files were not included in the files that the PC decided to keep, which is kind of dumb but oh well it happened. I then reapplied the Nividia update, just in case, and got three BSOD from then until now.
    Those .dmp files I do have.
    Attachment 91255Attachment 91254
      My ComputerSystem Spec

  5.    21 Jul 2016 #5

    Another update. Some more crashes throughout the day.
    Attachment 91317Attachment 91320Attachment 91317
      My ComputerSystem Spec


  6. Posts : 4,998
    Windows 10 Pro X64 15063.138
       21 Jul 2016 #6

    4 or 5 of the dumps show Authe3nticAMD as the cause. This is generally a CPU problem, sometimes caused by incorrect voltage from PSU or clock speed wrong (over or under clocked). Sometimes is just defective hardware:

    Code:
    2: kd> !errrec ffffe001d78e3028
    ===============================================================================
    Common Platform Error Record @ ffffe001d78e3028
    -------------------------------------------------------------------------------
    Record Id     : 01d1e366232a5bf1
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 7/21/2016 15:40:34 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe001d78e30a8
    Section       @ ffffe001d78e3180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : BUS error
    Operation     : Generic
    Flags         : 0x00
    Level         : 3
    CPU Version   : 0x0000000000600f20
    Processor ID  : 0x0000000000000002
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe001d78e30f0
    Section       @ ffffe001d78e3240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000002
    CPU Id        : 20 0f 60 00 00 08 04 02 - 0b 32 98 3e ff fb 8b 17
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    Proc. Info 0  @ ffffe001d78e3240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe001d78e3138
    Section       @ ffffe001d78e32c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : BUSLG_GENERIC_ERR_*_NOTIMEOUT_ERR (Proc 2 Bank 5)
      Status      : 0xb080000000080e0f
    Error from the CPU cache controller for processor 2 bank 5.
    No BIOS update available as you already have the latest which is F6.

    Check voltages and clocking, make sure all are in spec.
      My ComputersSystem Spec

  7.    22 Jul 2016 #7

    I downloaded CPUZ to check clock speeds and OpenHardwareMoniter to check voltages.
    Here is the result
    Attachment 91528
    According to CPUZ, my clock speeds varies with the lowest seen being 1406 and the highest being 3917.
    According to OpenHardwareMoniter my voltage is at 3.168v and that is also the max. However, it may be possible that I have read OHM wrong.
      My ComputerSystem Spec

  8.    22 Jul 2016 #8

    Update.
    Attachment 91618
    This is the only crash that happened today.
    Attachment 91619
      My ComputerSystem Spec


  9. Posts : 4,998
    Windows 10 Pro X64 15063.138
       22 Jul 2016 #9

    Nothing useful in the dump unfortunately.

    Are you overclocking anything? I'm not a hardware type so don't know much about clocking and voltage. I'll ask one of the other folks here to take a look at this thread.

    Meantime it would be good to test your RAM, make sure there are no problems there.

    RAM:

    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    Information


    MemTest86+
    is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses


    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
      My ComputersSystem Spec


  10. Posts : 11,485
    Windows 10 Pro
       23 Jul 2016 #10

    4 or 5 of the dumps show Authe3nticAMD as the cause.
    @Ztruker, never noticed the difference between GenuineIntel & AuthenticAMD in 0x124?

    @Mashalien, were those BSODs at boot when driver verifier was enabled this BSOD? No dump showed driver verifier enabled.

    The 0x4E look like to be caused by drivers, it looks like something keeps attempting to free memory that was already freed. Though that would give usually a different BSOD than a 0x4E (IME), but as we have only a minidump the memory descriptors of the addresses with which this driver attempted to free the memory cannot be checked.
    Code:
    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000099, A PTE or PFN is corrupt
    Arg2: 0000000000075305, page frame number
    Arg3: 0000000000000002, current page state
    Arg4: 00000170001786cc, 0
      My ComputersSystem Spec


 
Page 1 of 4 123 ... LastLast

Related Threads
Customization Open Action Center in Windows 10 in Tutorials
How to Open and Use Action Center in Windows 10 In Windows 10, action center is where to find your app notifications, as well as quick actions, which give you quick access to commonly used settings and apps. The action center will show you...
I use the mail app from windows 10 for my e-mail.Is it possible to get a pop-up from the action center when i get a e-mail? At the moment i see only on the icon in the taskbar that a got a e-mail but without a pop-up.
There's anyway to open action center like the Charm Bar from Windows 8?
Looking for the syntax to create a shortcut to open the new Win 10 Action Center (Winkey+A). Thanks
Action Center in General Support
How to remove those annoying "back up files" notifications in action center when I already use an external drive
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 10:52.
Find Us