"Your PC encountered a problem and needs to restart." - Round 2.

Page 4 of 7 FirstFirst ... 23456 ... LastLast

  1. Posts : 172
    Microsoft Windows 10 Pro 64-bit
    Thread Starter
       18 Apr 2017 #31

    axe0 said: View Post
    Let's see if there may be a driver issue




    "Your PC encountered a problem and needs to restart." - Round 2. Diagnostic Test "Your PC encountered a problem and needs to restart." - Round 2.
     DRIVER VERIFIER

    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.


    It will be at least several days (possibly longer) before I'm able to do that. I'll provide you with any updates.
      My ComputerSystem Spec

  2. axe0's Avatar
    Posts : 13,781
    Windows 10 Pro
       18 Apr 2017 #32

    No problem, I have the time to wait :)
      My ComputersSystem Spec


  3. Posts : 172
    Microsoft Windows 10 Pro 64-bit
    Thread Starter
       05 May 2017 #33

    axe0 said: View Post
    No problem, I have the time to wait :)

    I went through the process to use Driver Verifier described in the tutorial that you linked to (Part 1 - Option 1, then Part 2, including the restart), but I am not noticing any sluggishness on my computer. Might it be that Driver Verifier isn't working (possibly the reboot didn't cause it to kick on)?

    Is there any way that I can tell for certain whether it's running (such as an item in my Task Manager)?
    Last edited by hbenthow; 05 May 2017 at 00:59.
      My ComputerSystem Spec

  4. axe0's Avatar
    Posts : 13,781
    Windows 10 Pro
       05 May 2017 #34

    Some settings in driver verifier require the system to reboot for it to be enabled, if you don't reboot the system those settings won't be used whilst running driver verifier.

    It happens from time to time that no sluggishness isn't noticed.

    In an admin command prompt, run following command to see the status of driver verifier.
    Code:
    verifier /query
      My ComputersSystem Spec


  5. Posts : 172
    Microsoft Windows 10 Pro 64-bit
    Thread Starter
       05 May 2017 #35

    axe0 said: View Post
    Some settings in driver verifier require the system to reboot for it to be
    axe0 said: View Post
    enabled, if you don't reboot the system those settings won't be used whilst running driver verifier.


    But (as I mentioned in my last post), I did restart my computer after applying the settings.

    axe0 said: View Post
    In an admin command prompt, run following command to see the status of driver verifier.
    Code:
    verifier /query

    I've now done that. I have the result that the command prompt showed me attached as a text file below. Does this information confirm that Driver Verifier is indeed running?

    Attachment 133590
    Last edited by hbenthow; 05 May 2017 at 10:28.
      My ComputerSystem Spec

  6. axe0's Avatar
    Posts : 13,781
    Windows 10 Pro
       05 May 2017 #36

    It was only an explanation why driver verifier needs to be restarted, nothing else :)

    Driver verifier is running on your system. If driver verifier wasn't running you wouldn't get this kind of information
    Code:
        Raise IRQLs:                                861860
        Acquire Spin Locks:                        6822007
        Synchronize Executions:                          4
        Trims:                                           0
    
        Pool Allocations Attempted:               17556682
        Pool Allocations Succeeded:               17556682
        Pool Allocations Succeeded SpecialPool:        915
        Pool Allocations With No Tag:                   24
        Pool Allocations Not Tracked:                    0
        Pool Allocations Failed:                         0
        Pool Allocations Failed Deliberately:            0
      My ComputersSystem Spec


  7. Posts : 172
    Microsoft Windows 10 Pro 64-bit
    Thread Starter
       05 May 2017 #37

    axe0 said: View Post
    It was only an explanation why driver verifier needs to be restarted, nothing else :)

    Driver verifier is running on your system. If driver verifier wasn't running you wouldn't get this kind of information
    Code:
        Raise IRQLs:                                861860
        Acquire Spin Locks:                        6822007
        Synchronize Executions:                          4
        Trims:                                           0
    
        Pool Allocations Attempted:               17556682
        Pool Allocations Succeeded:               17556682
        Pool Allocations Succeeded SpecialPool:        915
        Pool Allocations With No Tag:                   24
        Pool Allocations Not Tracked:                    0
        Pool Allocations Failed:                         0
        Pool Allocations Failed Deliberately:            0
    Ah, that's good. The 48 hours will be over at 8:57 PM tomorrow night, so I should report back shortly after that (if I don't get a BSOD first).
      My ComputerSystem Spec


  8. Posts : 172
    Microsoft Windows 10 Pro 64-bit
    Thread Starter
       06 May 2017 #38

    axe0 said: View Post
    Please follow this tutorial to run driver verifier.
    Well, I have now run Driver Verifier for over 48 hours. It ran without incident. There were no BSODs. Right before I turned Driver Verifier off, I saved the information from Command Prompt again. Here's a text file of it:

    Attachment 133883
    Last edited by hbenthow; 06 May 2017 at 23:23.
      My ComputerSystem Spec

  9. axe0's Avatar
    Posts : 13,781
    Windows 10 Pro
       07 May 2017 #39

    Partly good :)

    Going back a bit to the hardware tests, did you run the hard disk tests on all your hard drives or partitions?
    I just went through the event logs a bit, there is an unbelievable large amount of issues with multiple disks spread over months.

    The day this thread was created, a large amount of event logs like these were created
    Code:
    Event[10497]:
      Log Name: System
      Source: disk
      Date: 2017-03-08T01:50:00.872
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-AVBIS4C
      Description: 
    The IO operation at logical block address 0x1ecc9fb0 for Disk 3 (PDO name: \Device\0000004f) was retried.
    
    Event[10515]:
      Log Name: System
      Source: disk
      Date: 2017-03-08T01:50:36.038
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-AVBIS4C
      Description: 
    An error was detected on device \Device\Harddisk3\DR3 during a paging operation.
    Almost 2 months earlier, the same
    Code:
    Event[8063]:
      Log Name: System
      Source: disk
      Date: 2017-01-31T01:12:13.851
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-AVBIS4C
      Description: 
    The IO operation at logical block address 0x137d5000 for Disk 3 (PDO name: \Device\0000004d) was retried.
    
    Event[6421]:
      Log Name: System
      Source: disk
      Date: 2017-01-16T16:24:57.552
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-AVBIS4C
      Description: 
    An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
      My ComputersSystem Spec


  10. Posts : 172
    Microsoft Windows 10 Pro 64-bit
    Thread Starter
       07 May 2017 #40

    axe0 said: View Post
    Partly good :)

    Going back a bit to the hardware tests, did you run the hard disk tests on all your hard drives or partitions?
    No. As my C drive is the only one that necessary for the computer to function correctly, I only tested it. I've run rudimentary tests on my other drives, but nothing advanced.

    I just went through the event logs a bit, there is an unbelievable large amount of issues with multiple disks spread over months.
    The two hard drives listed as having problems in those reports (Disk 2 and Disk 3) are both external drives (neither of which is necessary for my computer to run correctly). Disk 3 is an ancient external Western Digital drive that I use only as a backup and which showed me some warnings in a hard drive test long ago. I already knew that it likely had issues.

    Disk 2 is an internal SATA drive placed in an external USB enclosure (also used as a backup). I had to replace said enclosure, as it was faulty and kept causing (non-dangerous to my system) errors (hence the read errors on Disk 2). All of those error reports for Disk 2 are from times when I had a faulty hard drive enclosure.
      My ComputerSystem Spec


 
Page 4 of 7 FirstFirst ... 23456 ... LastLast

Related Threads
I was using my computer today when suddenly a bluescreen message saying "Your PC encountered a problem and needs to restart" popped up. It had some other information and some sort of countdown. I ran into another room to grab my camera to take a...
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x00000000, 0x00000501, 0x00000500, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: f1d94767-a34a-414f-a8b0-b616cc772393.
I have recently upgraded from Windows 7 to Windows 10, and have successfully installed previous Windows 7 games, which seem to function without problems. However Spider Solitaire often returns message "Unexpected Null Pointer Encountered", usually...
I don't know what's causing this, but I keep getting the blue screen with that warning on it. Any way I can fix it? Been happening a lot the last couple of days.
Firstly, I am using Win 10 Pro(Activated) on a HP laptop with Dual GPU(Intel HD Graphics and Nvidia GT 820M). Here are my full specs :- http://speccy.piriform.com/results/cREP1ITvTTAH3Jw52Y7triX Since the last 10 hours, I am constantly getting...
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:51.
Find Us