BSOD when using Microsoft Excel, error 0x0000000a


  1. Posts : 41
    Windows 10 Pro 64-bit (22H2)
       #1

    BSOD when using Microsoft Excel, error 0x0000000a


    Hi. I just got a new BSOD when using Microsoft Excel 2016. The BSOD is titled IRQL_NOT_LESS_OR_EQUAL, and after using BlueScreenView app, it states that it was ntoskrnl.exe which caused the problem. However it cannot really sure what drivers or any particular apps that causes the problem at that moment, so any help will be very appreciated.
    I have uploaded the zip file for my system information and also the crash note extracted from BlueScreenView for further information.
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    No dumps in the zip file you uploaded. According to the WER data there should have been a minidump create at 3/4/2019 at 12:35AM

    Code:
    3/4/2019 12:35 AM
    Windows Error Reporting
    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: a
    P2: ffff940000000000
    P3: 2
    P4: 0
    P5: fffff801113b27c4
    P6: 10_0_17763
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    Attached files:
    \\?\C:\WINDOWS\Minidump\030419-45468-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-212828-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC66E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC6FB.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC70A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC759.tmp.txt
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_3a84f61fbdcea5dbfafaa278b58352ce4f6fec5_00000000_02ffc777
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 082af912-7b84-4102-b3c1-e1a4c138b6aa
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    Please run the Beta log collector and upload the resulting zip file. It collects additional data that may help figure out what is going on.

    Do you run any cleanup program like CCLeaner? If so, it may have deleted the minidump.

    If you get another BSOD, run the Beta log collector immediately and upload the zip file in this thread, before the dump gets deleted.

    Also see a lot of APPCRASH events for Xau_ki_tu_2.exe which seems to have something to do with Bai tap pascal
      My Computers


  3. Posts : 41
    Windows 10 Pro 64-bit (22H2)
    Thread Starter
       #3

    Ztruker said:
    No dumps in the zip file you uploaded. According to the WER data there should have been a minidump create at 3/4/2019 at 12:35AM

    Code:
    3/4/2019 12:35 AM
    Windows Error Reporting
    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: a
    P2: ffff940000000000
    P3: 2
    P4: 0
    P5: fffff801113b27c4
    P6: 10_0_17763
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    Attached files:
    \\?\C:\WINDOWS\Minidump\030419-45468-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-212828-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC66E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC6FB.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC70A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC759.tmp.txt
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_3a84f61fbdcea5dbfafaa278b58352ce4f6fec5_00000000_02ffc777
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 082af912-7b84-4102-b3c1-e1a4c138b6aa
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    Please run the Beta log collector and upload the resulting zip file. It collects additional data that may help figure out what is going on.

    Do you run any cleanup program like CCLeaner? If so, it may have deleted the minidump.

    If you get another BSOD, run the Beta log collector immediately and upload the zip file in this thread, before the dump gets deleted.

    Also see a lot of APPCRASH events for Xau_ki_tu_2.exe which seems to have something to do with Bai tap pascal
    First of all, the minidump file got deleted unexpectedly after I restarted my laptop from System Restore (it shouldn't have been deleted even if I didn't use System Restore right?)
    Secondly, I don't use any cleaning programs, not even CCleaner, so this isn't the possibility.
    I've already copied the minidump file at that moment to another disk drive, but the forum here didn't allow me to upload the .dmp file itself. Now I will try uploading the whole .dmp file in .zip file, so you can check this one out in more detail.
    APPCRASH like Xau_ki_tu_2.exe is actually some C programs that failed to run. I'm studying software engineering at my university so those errors are normal.
      My Computer


  4. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #4

    Thanks for the dump. Unfortunately it didn't help.

    I want you to run memtest86+ v 5.01 as follows:
    ===================================================
    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    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   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   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.
    Take a picture when done and post in the forum please.

    If that doesn't indicate a memory problem then give Driver Verifier a try.

    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 may run very sluggishly due to the stress being applied to the drivers.

    Directions here: Driver Verifier - Enable and Disable in Windows 10

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

    warning   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 so you have a way to recover if it goes haywire. Seldom does but it can happen.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the Beta log collector and upload the resulting zip file.

    Here is some additional info on Driver Verifier posted by @axe0 today in another thread:
    Random weekly BSODs even after reset, CRITICAL_PROCESS_DIED
      My Computers


  5. Posts : 41
    Windows 10 Pro 64-bit (22H2)
    Thread Starter
       #5

    Ztruker said:
    Thanks for the dump. Unfortunately it didn't help.

    I want you to run memtest86+ v 5.01 as follows:
    ===================================================
    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    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   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   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.
    Take a picture when done and post in the forum please.

    If that doesn't indicate a memory problem then give Driver Verifier a try.

    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 may run very sluggishly due to the stress being applied to the drivers.

    Directions here: Driver Verifier - Enable and Disable in Windows 10

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

    warning   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 so you have a way to recover if it goes haywire. Seldom does but it can happen.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the Beta log collector and upload the resulting zip file.

    Here is some additional info on Driver Verifier posted by @axe0 today in another thread:
    Random weekly BSODs even after reset, CRITICAL_PROCESS_DIED
    Thank you for taking your time, but I reinstalled Win 10 on my laptop already. I haven't had a problem since but due to the fact that I'm still using HDD for my laptop so I think that could be the culprit to lead to this annoying BSOD. I'm switching to SSD tomorrow morning to see if it gets better and I will inform you later on after certain day usage.
    Anyway I'm very sorry for replying this late. I did memtest86 on my laptop but it ran so slow that it hadn't fully reached 8 passes in just one night and afraid for any further system instabilities, so I chose to do the above method. My laptop could only run to 7 passes, but all of them didn't find any errors.
      My Computer


  6. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #6

    That's okay. Good luck with the SSD.
      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 15:01.
Find Us




Windows 10 Forums