Random BSOD Pc, BSOD IRQL_NOT_LESS_OR_EQUAL and more...


  1. Posts : 3
    Windows 10 pro
       #1

    Random BSOD Pc, BSOD IRQL_NOT_LESS_OR_EQUAL and more...


    Hey Everybody


    im facing a problem for a while now,
    I installed ( clean install ) my windows 10 & updated all updates,
    now, im getting BSOD ( usually when i watch a movie )....
    i restored my system but problem is still there...
    im posting my Log , hope you help me:

    Attachment 95581




    ps.i had BSOD problem when i used windows 7 , thats why i clean installed my current windows 10
      My Computer

  2. axe0's Avatar
    Posts : 14,789
    Windows 10 Pro
       #2

    Hi Kouros,

    Welcome to the 10forums :)

    Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial




    Diagnostic Test

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.


    Make a photo of the result and post it.

    Addition:
    If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
    If errors show up and you see them a lot later, no problem, the errors don't affect the test.




    Diagnostics Test

     HDD TEST


    Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
    Run the long test.
    Note   Note
    Do not run SeaTools on an SSD as the results will be invalid.

    Make a photo of the result and post it.

    Run chkdsk
    Disk Check - Windows 7 Help Forums
    Use option TWO with parameter /r
    Upload the chkdsk log Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

    Run HDTune to
    • scan for errors, no quick scan but full scan
    • check the health,
    • run a benchmark.

    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    • the error scan,
    • the health,
    • the benchmark incl. following
      • transfer rate,
      • access time,
      • burst rate,
      • cpu usage.


    Code:
    Event[1563]:
      Log Name: System
      Source: volmgr
      Date: 2016-08-07T03:27:23.271
      Event ID: 46
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-UR71OD6
      Description: 
    Crash dump initialization failed!
      My Computers


  3. Posts : 3
    Windows 10 pro
    Thread Starter
       #3

    Thank you axe0for your reply & guidance...


    i did all that you asked me & here are the results :
    Attachment 95863Attachment 95864Attachment 95865Attachment 95866Attachment 95867

    and here is log file of chkdsk:
    Code:
    Log Name:      Application
    Source:        Microsoft-Windows-Wininit
    Date:          8/13/2016 12:45:20 PM
    Event ID:      1001
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      DESKTOP-UR71OD6
    Description:
    
    
    
    
    Checking file system on C:
    The type of the file system is NTFS.
    
    
    A disk check has been scheduled.
    Windows will now check the disk.                         
    
    
    Stage 1: Examining basic file system structure ...
      225792 file records processed.                                                        
    
    
    File verification completed.
      4165 large file records processed.                                   
    
    
      0 bad file records processed.                                     
    
    
    
    
    Stage 2: Examining file name linkage ...
      294988 index entries processed.                                                       
    
    
    Index verification completed.
      0 unindexed files scanned.                                        
    
    
      0 unindexed files recovered to lost and found.                    
    
    
    
    
    Stage 3: Examining security descriptors ...
    Cleaning up 1059 unused index entries from index $SII of file 0x9.
    Cleaning up 1059 unused index entries from index $SDH of file 0x9.
    Cleaning up 1059 unused security descriptors.
    Security descriptor verification completed.
      34599 data files processed.                                           
    
    
    CHKDSK is verifying Usn Journal...
      37114752 USN bytes processed.                                                           
    
    
    Usn Journal verification completed.
    
    
    Stage 4: Looking for bad clusters in user file data ...
      225776 files processed.                                                               
    
    
    File data verification completed.
    
    
    Stage 5: Looking for bad, free clusters ...
      54412846 free clusters processed.                                                       
    
    
    Free space verification is complete.
    
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
    
     262041599 KB total disk space.
      43923928 KB in 181998 files.
        128252 KB in 34600 indexes.
             0 KB in bad sectors.
        338031 KB in use by the system.
         65536 KB occupied by the log file.
     217651388 KB available on disk.
    
    
          4096 bytes in each allocation unit.
      65510399 total allocation units on disk.
      54412847 allocation units available on disk.
    
    
    Internal Info:
    00 72 03 00 b6 4d 03 00 f4 91 06 00 00 00 00 00  .r...M..........
    3d 01 00 00 02 0b 00 00 00 00 00 00 00 00 00 00  =...............
    
    
    Windows has finished checking your disk.
    Please wait while your computer restarts.
    
    
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>4</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2016-08-13T08:15:20.082488200Z" />
        <EventRecordID>3352</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>DESKTOP-UR71OD6</Computer>
        <Security />
      </System>
      <EventData>
        <Data>
    
    
    Checking file system on C:
    The type of the file system is NTFS.
    
    
    A disk check has been scheduled.
    Windows will now check the disk.                         
    
    
    Stage 1: Examining basic file system structure ...
      225792 file records processed.                                                        
    
    
    File verification completed.
      4165 large file records processed.                                   
    
    
      0 bad file records processed.                                     
    
    
    
    
    Stage 2: Examining file name linkage ...
      294988 index entries processed.                                                       
    
    
    Index verification completed.
      0 unindexed files scanned.                                        
    
    
      0 unindexed files recovered to lost and found.                    
    
    
    
    
    Stage 3: Examining security descriptors ...
    Cleaning up 1059 unused index entries from index $SII of file 0x9.
    Cleaning up 1059 unused index entries from index $SDH of file 0x9.
    Cleaning up 1059 unused security descriptors.
    Security descriptor verification completed.
      34599 data files processed.                                           
    
    
    CHKDSK is verifying Usn Journal...
      37114752 USN bytes processed.                                                           
    
    
    Usn Journal verification completed.
    
    
    Stage 4: Looking for bad clusters in user file data ...
      225776 files processed.                                                               
    
    
    File data verification completed.
    
    
    Stage 5: Looking for bad, free clusters ...
      54412846 free clusters processed.                                                       
    
    
    Free space verification is complete.
    
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
    
     262041599 KB total disk space.
      43923928 KB in 181998 files.
        128252 KB in 34600 indexes.
             0 KB in bad sectors.
        338031 KB in use by the system.
         65536 KB occupied by the log file.
     217651388 KB available on disk.
    
    
          4096 bytes in each allocation unit.
      65510399 total allocation units on disk.
      54412847 allocation units available on disk.
    
    
    Internal Info:
    00 72 03 00 b6 4d 03 00 f4 91 06 00 00 00 00 00  .r...M..........
    3d 01 00 00 02 0b 00 00 00 00 00 00 00 00 00 00  =...............
    
    
    Windows has finished checking your disk.
    Please wait while your computer restarts.
    </Data>
      </EventData>
    </Event>


    Ps.I removed some of my softwares ( as you mentioned me on 7forum ) including AutoKMS & office & ...

    hope we find a solution to my problem
      My Computer

  4. axe0's Avatar
    Posts : 14,789
    Windows 10 Pro
       #4

    The reallocated sector count is at a critical point, not critical enough for a failure but close to it.
    I would suggest to simply replace the hard drive to avoid problems with it :)
      My Computers


  5. Posts : 3
    Windows 10 pro
    Thread Starter
       #5

    So the hard mainly causes the BSOD , am i right ? so then with replacing hdd with a new hard the bsod problem is gone???
      My Computer

  6. axe0's Avatar
    Posts : 14,789
    Windows 10 Pro
       #6

    Yes, you may want to clean install on the new hard drive. A clean install prevents that you take other problems that may be BSOD risks (like outdated or buggy drivers) to the new drive.
      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 12:01.
Find Us




Windows 10 Forums