Windows 10: BSOD On Just About Every Action

Discus and support BSOD On Just About Every Action in Windows 10 BSOD Crashes and Debugging to solve the problem; First off, my specs. System Spec Computer type:PC/DesktopSystem Manufacturer/Model Number:Cyberpower PCOS:Windows 10CPU:AMD Fx 4300 Quad Core... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Mashalien, Jul 20, 2016.

  1. Mashalien Win User

    BSOD On Just About Every Action


    First off, my specs.
    System Spec

    Computer typeBSOD On Just About Every Action :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

    :)
     
    Mashalien, Jul 20, 2016
    #1

  2. ASTERISK ON SEARCH, LOGON AND JUST ABOUT EVERY WINDOW USING WINDOWS 10

    Whenever I logon, try to use the internet, even when trying to put a subject into this question, an asterisk appears and continues for a line or so. The only way I can get rid of it is to delete or backspace. Very frustrating (just did it again) when
    you're in the middle of something and the asterisk interrupts whatever you are doing. Anyone else experiencing this ? Would apprec*iate any suggestions.*************************************************************************************************
     
    Paul and Judy Williams, Jul 20, 2016
    #2
  3. ASTERISK ON SEARCH, LOGON AND JUST ABOUT EVERY WINDOW USING WINDOWS 10

    Thanks Sam. I'm hoping the asterisk key sticking was the problem as I did what you suggested and it seems to be working fine now.
     
    Paul and Judy Williams, Jul 20, 2016
    #3
  4. Ztruker Win User

    BSOD On Just About Every Action

    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[/quote] 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

    BSOD On Just About Every Action [​IMG]
    PART TWO
    BSOD On Just About Every Action [​IMG]

    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.
     
    Ztruker, Jul 20, 2016
    #4
  5. Mashalien Win User
    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.
     
    Mashalien, Jul 20, 2016
    #5
  6. Mashalien Win User
    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
     
    Mashalien, Jul 20, 2016
    #6
  7. Mashalien Win User
    Another update. Some more crashes throughout the day.
    Attachment 91317Attachment 91320Attachment 91317
     
    Mashalien, Jul 20, 2016
    #7
  8. Ztruker Win User

    BSOD On Just About Every Action

    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[/quote] 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.
     
    Ztruker, Jul 21, 2016
    #8
  9. Mashalien Win User
    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.
     
    Mashalien, Jul 21, 2016
    #9
  10. Mashalien Win User
    Update.
    Attachment 91618
    This is the only crash that happened today.
    Attachment 91619
     
    Mashalien, Jul 22, 2016
    #10
  11. Ztruker Win User
    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


    BSOD On Just About Every Action [​IMG]
    Information

    BSOD On Just About Every Action [​IMG]


    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.


    BSOD On Just About Every Action [​IMG]
    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.


    BSOD On Just About Every Action [​IMG]
    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.
     
    Ztruker, Jul 22, 2016
    #11
  12. axe0 New Member
    @Ztruker, never noticed the difference between GenuineIntel & AuthenticAMD in 0x124? *Smile

    @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[/quote]
     
  13. Mashalien Win User

    BSOD On Just About Every Action

    Memtest had 10 runs with no errors. @axe0 yes those were the BSOD on boot when driver verifier was on. Sorry about the lack of dump files about it but in order to access the pc I had to reset it. For whatever reason, dump files aren't included in the 'Keep Documents' option and I had yet to make a restore point.

    How would I go about checking the memory descriptors of the addresses with which this driver attempted to free the memory?
     
    Mashalien, Jul 23, 2016
    #13
  14. axe0 New Member
    That is more a thing that we do.
    You would require knowledge about Windows as you need to know what is and what is not a violation, you also need to know how to debug a kernel memory dump.
    With knowledge about Windows I do not mean the visible part, but the part 'behind the scenes', thus the part that happens in the background that the user is not aware of.

    An example of a mini memory dump.
    Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: ffffd000ebb96a30 Arg3: 000000007267d5e9 Arg4: fffff8016286ffb3 Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 10240.17022.amd64fre.th1_st1.160623-1726 SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M. SYSTEM_SKU: To Be Filled By O.E.M. SYSTEM_VERSION: To Be Filled By O.E.M. BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: P2.60 BIOS_DATE: 07/11/2013 BASEBOARD_MANUFACTURER: ASRock BASEBOARD_PRODUCT: FM2A75 Pro4-M BASEBOARD_VERSION: DUMP_TYPE: 2 DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_P1: 8 BUGCHECK_P2: ffffd000ebb96a30 BUGCHECK_P3: 7267d5e9 BUGCHECK_P4: fffff8016286ffb3 BUGCHECK_STR: 0x7f_8 BAD_STACK_POINTER: 000000007267d5e9 CPU_COUNT: 4 CPU_MHZ: ed1 CPU_VENDOR: AuthenticAMD CPU_FAMILY: 15 CPU_MODEL: 10 CPU_STEPPING: 1 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: DESKTOP-FO9QHGA ANALYSIS_SESSION_TIME: 07-24-2016 14:34:50.0967 ANALYSIS_VERSION: 10.0.10586.567 amd64fre MISALIGNED_IP: nt!PpmIdleExecuteTransition+e43 fffff801`6286ffb3 0200 add al,byte ptr [rax] UNALIGNED_STACK_POINTER: 000000007267d5e9 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8016286ffb3 STACK_TEXT: 00000000`7267d5e9 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmIdleExecuteTransition+0xe43 STACK_COMMAND: kb THREAD_SHA1_HASH_MOD_FUNC: 65379b530d41d556923d028b21bfeaf00278ad84 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 350c605a2a491af7c8be756570a5f8f1e6fb91d1 THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3 FOLLOWUP_IP: nt!PpmIdleExecuteTransition+e43 fffff801`6286ffb3 0200 add al,byte ptr [rax] FAULT_INSTR_CODE: 48000002 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!PpmIdleExecuteTransition+e43 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: 10.0.10240.17022 MODULE_NAME: hardware FAILURE_BUCKET_ID: IP_MISALIGNED BUCKET_ID: IP_MISALIGNED PRIMARY_PROBLEM_CLASS: IP_MISALIGNED TARGET_TIME: 2016-07-23T15:24:42.000Z OSBUILD: 10240 OSSERVICEPACK: 0 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2016-06-24 05:57:23 BUILDDATESTAMP_STR: 160623-1726 BUILDLAB_STR: th1_st1 BUILDOSVER_STR: 10.0.10240.17022.amd64fre.th1_st1.160623-1726 ANALYSIS_SESSION_ELAPSED_TIME: 3ed ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:ip_misaligned FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750} Followup: MachineOwner[/quote]
     
  15. axe0 New Member
    @Mashalien, please provide results to suggested tests, we are waiting for you to reply.
     
Thema:

BSOD On Just About Every Action

Loading...
  1. BSOD On Just About Every Action - Similar Threads - BSOD Every Action

  2. Just asking about KB4517389

    in Windows 10 Installation and Upgrade
    Just asking about KB4517389: Hi A few weeks ago I installed this via update and I lost the use of my the Windows button in the bottom left. I could not find the item to uninstall manually so I did a system restore and my system was ok. Looking at the Windows release dashboard and googling various...
  3. BSOD with restart about every 12 hours

    in Windows 10 BSOD Crashes and Debugging
    BSOD with restart about every 12 hours: I am not sure what the root cause, but since about 2 weeks my computer (Intel I5-4590 with 8GB of DDR3 RAM) is having a BSOD about every 12 hours. Interesting is that the BSOD has changed a few days ago to a "PSOD" (pink screen of death :-) Looking into the error log I see...
  4. Random BSOD While Doing Just About Anything On My PC

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD While Doing Just About Anything On My PC: Hi. About one or or two times a day for the past week or so, I've been experiencing BSOD and I'm not really sure what the problem is because this is a new PC and of course, there shouldn't be anything wrong with it. Initially, I thought something about minecraft was causing...
  5. Just a small question about Steam

    in Windows 10 BSOD Crashes and Debugging
    Just a small question about Steam: Just wanted to know if my Windows 10 laptop with nothing extra on it, (e.g. extra storage, not including apps) could run Portal 1. Thanks in advance! https://answers.microsoft.com/en-us/windows/forum/all/just-a-small-question-about-steam/7e259984-551d-4e8b-8d98-7528116a0a87
  6. BSOD about every 5 mins

    in Windows 10 BSOD Crashes and Debugging
    BSOD about every 5 mins: Getting bsod about every 5 mins and have to reboot to use for about 5 more mins. Pretty sure that it is MB related and hoping your tool will help diag the problem. The bsod happens with both my win 10 OSs after about the same time frame. 120335
  7. BSOD playing WOW, but occasionally doing just about anything

    in Windows 10 BSOD Crashes and Debugging
    BSOD playing WOW, but occasionally doing just about anything: First of all I want to thank all of you for the great tutorials on trying to figure this out on my own. I have tried and tried everything that was suggested, but I just can't figure it out by myself. I would really appreciate some help. I keep getting BSODs mostly when...
  8. Question About Action Center Icon

    in Windows 10 Support
    Question About Action Center Icon: Hey, Every now and then my Action Bar Icon in the Task Bar will switch from the normal rectangle with lines inside to the same thing except now there is a small circle in the lower right hand corner. If I click it the Action Center comes up like it normally would. Just...
  9. not just about Windws 10, but...

    in Windows 10 Support
    not just about Windws 10, but...: Had my Dell PC crash after a year running 10. I got new hard drive and USB with OS/drivers to restore Windows 7.Problem is that I am unable to do some stuff, like add folders to start menu and move individual programs into them. 10 worked great while I had it, maybe it was...
  10. Just a question about pricing

    in Windows 10 Support
    Just a question about pricing: How much US dollars is Windows 10 64-bit Pro and Windows 10 64-bit Home? 42487