none
Win 7 Pro - Event ID 1001 - EventName Bluescreen RRS feed

  • Domanda

  • Hello,

    I have a W7 Pro x64 system that has recently started experiencing degraded performance a few times per week and when this occurs all the icons disappear from the desktop. 

    - there is a blank desktop.
    - no response to keyboard but you can move the mouse
    - computer responds to pings
    - net use / net view work
    - RDP no longer works
    - remote shutdown sometimes works

    After looking through the EventLog, I have noted the following events

    - ID 1001
    - EventName: BlueScreen
    - the reported minidump file is the same for each event (see screenshots)
    - but the file in the minidump folder has a timestamp from 2016??

    Hardware diagnostics don't report any faults

    After suggestions on how to troubleshoot

    Thanks

    VW

    1st 1001 event2nd 1001 event3rd 1001 eventminidump folder

    domenica 14 luglio 2019 14:00

Risposte

  • Hello,

    Thanks for responding.

    I was eventually able to solve this issue.

    The issue was not related to this entry in the EventLog

    In fact unfortunately no meaningful events were logged.

    After observing the behaviour, I had a hunch that it was a storage related issue. Even though the hardware diagnostics reported no faults.

    The system was using Intel onboard RAID (i.e. not a dedicated RAID card like a PERC). Software RAID via the motherboard

    After disabling the RAID the issues ceased.

    It would have been good to have a more systematic approach to have isolated this fault.

    Thanks

    Vaughan


    • Contrassegnato come risposta vwickham domenica 11 agosto 2019 23:55
    • Modificato vwickham lunedì 12 agosto 2019 00:01 auto-correct error
    domenica 11 agosto 2019 23:55

Tutte le risposte

  • Hi,

    According to your description, please refer to “If you can start Windows” section in the link below first

    Resolving stop (blue screen) errors in Windows 7

    https://support.microsoft.com/en-us/help/17074/windows-7-resolving-stop-blue-screen-errors

    Meanwhile, the timestamp of minidump file is strange. Please just check it to see if any helpful information or you could upload the minidump file to OneDrive and share us the link.

    Hope it could be helpful.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    lunedì 15 luglio 2019 02:31
    Moderatore
  • Hello David,

    Thanks for responding.

    The issue with the minidump file in C:\Windows\Minidump is that it is as per the timestamp (i.e. back in 2016)

    Minidump analysis

    The second "issue" is that what is being reported as a "Bluescreen" is not a typical BSOD.

    Windows is still running, however the performance is degraded, the desktop is not usable (you can move the mouse pointer) but all the icons have disappeared and you cannot access any of the running applications. No response to the keyboard.\

    VW 

    lunedì 15 luglio 2019 04:02
  • Hi,

    You also could use Performance Monitor to troubleshoot referring to the link below:

    Method 3: Performance Monitor

    https://docs.microsoft.com/en-us/windows/client-management/troubleshoot-windows-freeze#method-3-performance-monitor

    Best Regards,


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    venerdì 9 agosto 2019 17:03
    Moderatore
  • To evaluate the BSOD please post logs for troubleshooting.

    Using administrative command prompt copy and paste this whole command.

    Make sure the default language is English so that the logs can be scanned and read.

    Choose the applicable link for the operating system:
    https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html
    https://www.eightforums.com/threads/language-add-or-remove-in-windows-8.5849/
    https://www.sevenforums.com/tutorials/87317-display-language-change.html

    The command will automatically collect the computer files and place them on the desktop.

    Then use 7zip to organize the files and one drive, drop box, or google drive to place share links into the thread for troubleshooting.

    https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

    This command will automatically collect these files:  msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.

    Open administrative command prompt and copy and paste the whole command:

    copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

    There are two files for you to find manually:

    a) C:\Windows\MEMORY.DMP

    Use file explorer > this PC > local C: drive > right upper corner search enter the above to find results.

    b) dxdiag:  

    In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread

    .

    .

    For startup and recovery:

    a) select kernel memory dump

    b) un-check automatically restart

    c) reboot to maintain settings

    d) post images into the thread for startup and recovery and virtual memory settings

    .

    .

    1) Open administrative command prompt and type or copy and paste:

    2) sfc /scannow

    3) bcdedit /enum {badmemory}

    4) 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


    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.
    .
    .
    .
    .
    .

    sabato 10 agosto 2019 08:30
  • Hello,

    Thanks for responding.

    I was eventually able to solve this issue.

    The issue was not related to this entry in the EventLog

    In fact unfortunately no meaningful events were logged.

    After observing the behaviour, I had a hunch that it was a storage related issue. Even though the hardware diagnostics reported no faults.

    The system was using Intel onboard RAID (i.e. not a dedicated RAID card like a PERC). Software RAID via the motherboard

    After disabling the RAID the issues ceased.

    It would have been good to have a more systematic approach to have isolated this fault.

    Thanks

    Vaughan


    • Contrassegnato come risposta vwickham domenica 11 agosto 2019 23:55
    • Modificato vwickham lunedì 12 agosto 2019 00:01 auto-correct error
    domenica 11 agosto 2019 23:55