Windows 10: BSOD On Dell Latitude 5580

Discus and support BSOD On Dell Latitude 5580 in Windows 10 BSOD Crashes and Debugging to solve the problem; We have 6 Dell Latitude 5580 laptops in one department that randomly get a BSOD. They all have the same docking station and all use the same software... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by NickF365, Dec 9, 2019.

  1. NICKF365
    NickF365 Win User

    BSOD On Dell Latitude 5580


    We have 6 Dell Latitude 5580 laptops in one department that randomly get a BSOD. They all have the same docking station and all use the same software daily. There are three other 5580's with the same setup, but do not use the same software and don't get the BCOD. I just can't determine which software may be causing it. I've made sure that the OS was completely up to date, all drivers up to date, reinstalled the OS, swapped out the entire laptop, but the BSOD still occurs. Any help would be appreciated, I have the most recent dump file included below.


    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1





    PROCESSES_ANALYSIS: 1



    SERVICE_ANALYSIS: 1



    STACKHASH_ANALYSIS: 1



    TIMELINE_ANALYSIS: 1





    DUMP_CLASS: 1



    DUMP_QUALIFIER: 401



    BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202



    SYSTEM_MANUFACTURER: Dell Inc.



    SYSTEM_PRODUCT_NAME: Latitude 5580



    SYSTEM_SKU: 07D1



    BIOS_VENDOR: Dell Inc.



    BIOS_VERSION: 1.16.0



    BIOS_DATE: 07/03/2019



    BASEBOARD_MANUFACTURER: Dell Inc.



    BASEBOARD_PRODUCT: 0FH6CJ



    BASEBOARD_VERSION: A00



    DUMP_TYPE: 1



    BUGCHECK_P1: c0000005



    BUGCHECK_P2: fffff80349102770



    BUGCHECK_P3: fffff8034fe2e930



    BUGCHECK_P4: 0



    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.



    FAULTING_IP:

    nt!KiSetClockInterval+60

    fffff803`49102770 3b7a1c cmp edi,dword ptr [rdx+1Ch]



    CONTEXT: fffff8034fe2e930 -- (.cxr 0xfffff8034fe2e930)

    rax=c400000008002000 rbx=fffff803494343a0 rcx=0000000000000000

    rdx=c400000008002000 rsi=fffff80349505c48 rdi=000000000002625a

    rip=fffff80349102770 rsp=ffffb28fffba3670 rbp=ffffb28fffba3701

    r8=0000000000000000 r9=0000000000000001 r10=fffff8034944f300

    r11=0000000000000000 r12=0000000000000000 r13=fffff803491025a0

    r14=ffffb28fffba3730 r15=000000000000000f

    iopl=0 nv up ei ng nz na po nc

    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286

    nt!KiSetClockInterval+0x60:

    fffff803`49102770 3b7a1c cmp edi,dword ptr [rdx+1Ch] ds:002b:c4000000`0800201c=????????

    Resetting default scope



    BUGCHECK_STR: 0x3B_c0000005



    CPU_COUNT: 8



    CPU_MHZ: b58



    CPU_VENDOR: GenuineIntel



    CPU_FAMILY: 6



    CPU_MODEL: 9e



    CPU_STEPPING: 9



    CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: B4'00000000 (cache) B4'00000000 (init)



    BLACKBOXBSD: 1 (!blackboxbsd)





    BLACKBOXNTFS: 1 (!blackboxntfs)





    BLACKBOXPNP: 1 (!blackboxpnp)





    BLACKBOXWINLOGON: 1



    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    PROCESS_NAME: javaw.exe



    CURRENT_IRQL: f



    ANALYSIS_SESSION_HOST:



    ANALYSIS_SESSION_TIME: 12-09-2019 14:18:33.0480



    ANALYSIS_VERSION: 10.0.18362.1 x86fre



    BAD_STACK_POINTER: fffff8034fe2dff8



    LAST_CONTROL_TRANSFER: from fffff80349102670 to fffff80349102770



    STACK_TEXT:

    ffffb28f`ffba3670 fffff803`49102670 : fffff803`467ad180 ffffb28f`ffba37d0 ffffb28f`ffba3800 00000000`00000000 : nt!KiSetClockInterval+0x60

    ffffb28f`ffba36a0 fffff803`4905d8a0 : fffff803`467ad180 ffffb28f`ffba3860 ffff9981`3682b080 00000000`00000000 : nt!ExpUpdateTimerConfigurationWorker+0xd0

    ffffb28f`ffba36d0 fffff803`4905d756 : 00000000`00000000 ffff9981`3277f1f0 00000000`00000001 ffffb28f`ffba39a8 : nt!KeGenericProcessorCallback+0x124

    ffffb28f`ffba3840 fffff803`4905cd96 : 00000000`000026f5 ffff9981`3a7e1080 ffffbbbd`c7757ca6 ffff9981`3a7e1080 : nt!ExpUpdateTimerConfiguration+0x9a

    ffffb28f`ffba3970 fffff803`495ff7c4 : ffff9981`3a7e1080 00000000`0002625a 00000000`2ab6f88c fffff803`496b397f : nt!ExpUpdateTimerResolution+0xa6

    ffffb28f`ffba39a0 fffff803`491d2d15 : ffff9981`3682b080 00000000`00000010 00000000`00000000 ffff9981`00000000 : nt!NtSetTimerResolution+0xf4

    ffffb28f`ffba3a00 00000000`77561cbc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25

    00000000`2ab1f308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77561cbc





    THREAD_SHA1_HASH_MOD_FUNC: c707402e959ba80de9060e827a2cf65c61ddb2bb



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e9813b674a3d015f8be9bd5fe9ceaaf1cdb35724



    THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6



    FOLLOWUP_IP:

    nt!KiSetClockInterval+60

    fffff803`49102770 3b7a1c cmp edi,dword ptr [rdx+1Ch]



    FAULT_INSTR_CODE: 721c7a3b



    SYMBOL_STACK_INDEX: 0



    SYMBOL_NAME: nt!KiSetClockInterval+60



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: nt



    IMAGE_NAME: ntkrnlmp.exe



    DEBUG_FLR_IMAGE_TIMESTAMP: 4efcf7a9



    STACK_COMMAND: .cxr 0xfffff8034fe2e930 ; kb



    BUCKET_ID_FUNC_OFFSET: 60



    FAILURE_BUCKET_ID: 0x3B_c0000005_STACKPTR_ERROR_nt!KiSetClockInterval



    BUCKET_ID: 0x3B_c0000005_STACKPTR_ERROR_nt!KiSetClockInterval



    PRIMARY_PROBLEM_CLASS: 0x3B_c0000005_STACKPTR_ERROR_nt!KiSetClockInterval



    TARGET_TIME: 2019-12-09T16:39:25.000Z



    OSBUILD: 18362



    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: 2011-12-29 18:28:41



    BUILDDATESTAMP_STR: 190318-1202



    BUILDLAB_STR: 19h1_release



    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202



    ANALYSIS_SESSION_ELAPSED_TIME: 24f4



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:0x3b_c0000005_stackptr_error_nt!kisetclockinterval



    FAILURE_ID_HASH: {37a1e7a9-2f78-aaff-5008-5c78ef49dd36}



    Followup: MachineOwner

    ---------

    :)
     
    NickF365, Dec 9, 2019
    #1
  2. LORIERODRIGUEZ
    LorieRodriguez Win User

    Dell 5580 and Microsoft Wireless Display Adapter

    We love the Microsoft Wireless Display Adapter - it's easy for everyone to walk in with their laptop and connect to project their screen. Except for those who have Dell 5580s.

    The Dell 5480s and SurfacePros connect great, but not the Dell 5580s.

    Any suggestions on how to resolve this for the 5580s?
     
    LorieRodriguez, Dec 9, 2019
    #2
  3. ZBOOK
    zbook Win User
    BSOD - Dell Latitude 5580

    Hi saadbg,

    1) There is an existing thread that you have active in the BSOD forum.
    In it you had been working with philc43 and he reported problems with hardware.
    See rules #2 and #4
    Forum Rules - Windows 10 Help Forums

    2) The latest dump displayed WHEA 0x124 and continues to point toward hardware problems.

    3) Please continue in the ongoing thread so that there is one thread:
    BSOD - Dell Latitude 5580 - Windows 10 Forums

    4) Copy and paste this post into the existing thread.

    5) Post a new BETA log collector.

    6) Open file explorer > this PC > C: > in the right upper corner search for C:\windows\memory.dmp > zip > post a separate share link with only the memory dump file into the thread (one drive, drop box, or google drive)

    Code:
    Code:
    7) Open administrative command prompt and type or copy and paste:
    8) sfc /scannow
    9) dism /online /cleanup-image /restorehealth
    10) chkdsk /scan
    11) wmic RecoverOS set AutoReboot = False
    12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    13) Make sure that there is no over clocking while troubleshooting.

    14) Run the Dell hardware diagnostics full tests and post images of the results into the thread.

    Support for Latitude 5580 | Drivers & downloads | Dell US


    15) Running the Dell diagnostics may automatically check for drivers.
    There were many driver updates in December 2018 and January 2019 including the chipset drivers.

    16) Separately check using the Dell update software to make sure that all drivers are up to date

    17) To ensure that there are no improper bios settings please reset the bios.
    18) Sometimes there can be failure to boot after resetting the bios.
    19) Backup the computer files to another drive or to the cloud.
    20) Make a backup image using Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free

    21) Create a brand new restore point:
    Create System Restore Point in Windows 10 | Tutorials

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    https://www.howtogeek.com/131623/how...bios-settings/
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    22) Test the RAM using Memtest86 version 8.01
    MemTest86 - Official Site of the x86 Memory Testing Tool
    MemTest86 - Official Site of the x86 Memory Testing Tool

    Testing is not by time but by passes.
    The more the passes the better the testing conditions
    The best test is 8 or more continuous passes.
    This is no longer available on the free version. and was last available for free with version 8.0
    Using version 8.1 perform two tests with each four passes.
    Use a camera or smart phone camera to take pictures and post images of each test result into the thread.
    Memtest86 version 8.1 also has a txt file. In addition to the image please post the text file into the thread using a share link (one drive, drop box, or google drive)

    23) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    24) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

    25) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
    Speccy - Free Download - Piriform: Speccy - System Information - Free
    Download Speccy | Find your computer specs, free!
    Download Speccy | Find your computer specs, free!
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    HWMONITOR | Softwares | CPUID
    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    SpeedFan - Access temperature sensor in your computer

    26) Run Prime95 - Stress Test Your CPU
    Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
    Prime95 - Stress Test Your CPU | Tutorials
    a) Record the maximum temperature and post the maximum temperature into the thread
    b) Record test duration and post the uninterrupted test duration into the thread
    c) Aim for testing > 3 hrs and abort testing as needed for freezing, temperature changes (see link)
    d) Use the Microsoft snipping tool to post images into the thread.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    Take Screenshot in Windows 10 | Tutorials

    27) Update the specs in the "My Computer" section:

    System Specs - Fill in at Ten Forums | Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums

    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)
     
    zbook, Dec 9, 2019
    #3
  4. PHILC43
    philc43 Win User

    BSOD On Dell Latitude 5580

    BSOD - Dell Latitude 5580

    Please follow the instructions after step 9 provided in BSOD Posting Instructions to create the log files and upload them.
     
    philc43, Dec 9, 2019
    #4
Thema:

BSOD On Dell Latitude 5580

Loading...

  1. BSOD On Dell Latitude 5580 - Similar Threads - BSOD Dell Latitude

  2. BSOD on rebuilt DELL Latitude 5400

    in Windows 10 Gaming
    BSOD on rebuilt DELL Latitude 5400: Purchased a re-conditioned DELL latitude 5400 from DELL i7 8th Gen so good for Win 11. It was originally Win 10 home. So purchased a Retail licence for Win11. Installed Windows 11 from ISO install. Now have had a couple of BSOD. These follow message on a black screen saying...

  3. BSOD on rebuilt DELL Latitude 5400

    in Windows 10 Software and Apps
    BSOD on rebuilt DELL Latitude 5400: Purchased a re-conditioned DELL latitude 5400 from DELL i7 8th Gen so good for Win 11. It was originally Win 10 home. So purchased a Retail licence for Win11. Installed Windows 11 from ISO install. Now have had a couple of BSOD. These follow message on a black screen saying...

  4. New Dell Latitude 7420 - BSODs

    in Windows 10 Drivers and Hardware
    New Dell Latitude 7420 - BSODs: Having several BSODs a day now on a new machine - everything is updated, BIOS, etc. Not sure what will become of this - but looking for some advice on how to fix.Mini-dump files, Dump File and NGO...

  5. BSOD IRLQ_NOT_LESS_OR_EQUAL dell latitude 5580 problem

    in Windows 10 Ask Insider
    BSOD IRLQ_NOT_LESS_OR_EQUAL dell latitude 5580 problem: Can anyone help? I suffered from BSOD problem where different codes appear but the common one is IRLQ_NOT_LESS_OR_EQUAL, I uninstalled my windows 10 pro and installed another windows 10 pro, and after a month of that, the problem came back. I tried all the solutions from the...

  6. Dell Latitude E5450 BSoDs randomly with DRIVER_VERIFIER_DMA_VIOLATION

    in Windows 10 BSOD Crashes and Debugging
    Dell Latitude E5450 BSoDs randomly with DRIVER_VERIFIER_DMA_VIOLATION: I tried to reset the windows, Installed a fresh copy ,and updated the drivers and BIOS. Nothing seems to work. Here's a dump for my last 3 BSoDs. https://1drv.ms/u/s!AjD5HZNO75dkcvykH_zfZ0q1xuI?e=FOxI2j...

  7. BSOD DELL Latitude 5410

    in Windows 10 BSOD Crashes and Debugging
    BSOD DELL Latitude 5410: Hi, I'm working at the IT department of my company and we're having more and more BSOD on this model : DELL Latitude 5410 about 10 laptops affected now and we started using this model a few weeks ago. I tried analyzing minidump files two of them with Winbdg but i can't...

  8. Fan issue on dell inspiron 5580 laptop

    in Windows 10 BSOD Crashes and Debugging
    Fan issue on dell inspiron 5580 laptop: First week of October : Fan started to make noticeable noise, even when the system temperature was low after booting up. Before this time it used to run at max speed without a sound. Third week of October : It started to make more noise and I felt my laptop vibrating...

  9. Dell Latitude 5580 random BSOD

    in Windows 10 BSOD Crashes and Debugging
    Dell Latitude 5580 random BSOD: Hi. This is second time I got BSOD again even all my drivers and BIOS are updated. Please can anyone check it and find the issue here. 126133

  10. BSOD - Dell Latitude 5580

    in Windows 10 BSOD Crashes and Debugging
    BSOD - Dell Latitude 5580: Hi. My all drivers are up-to-dated but recently I experienced BSOD when I was working normally. I have attached crash dump as well. Please can any one help me to find that culprit? Thanks in advance :) 122760