BSOD when starting up PC, but then it restarts fine


  1. Posts : 4
    Windows 10
       #1

    BSOD when starting up PC, but then it restarts fine


    Hello,

    I recently got a new GPU and fresh installed the drivers. For the first day, the PC booted up fine and there were no errors, but in the coming days after, when I start up the PC, it crashes with just a black screen (before entering windows login screen), then restarts normally with no errors.

    By checking BlueScreenView, the bug check string is MULTIPLE_IRP_COMPLETE_REQUESTS, and I assume the files that are affecting it is ntoskrnl.exe and nvlddmkm.sys.

    I have also uploaded the crash logs in the attachment.

    Thanks!
      My Computer


  2. Posts : 258
    Windows 10 Pro
       #2

    multiple_irp_complete_requests on windows 8.1 - Microsoft Community

    Bit of an old post but worth having a look at. Suggests removing LogmeIn if you have it installed?
      My Computer


  3. Posts : 4
    Windows 10
    Thread Starter
       #3

    kingtez1984 said:
    multiple_irp_complete_requests on windows 8.1 - Microsoft Community

    Bit of an old post but worth having a look at. Suggests removing LogmeIn if you have it installed?
    I don't have it installed, sadly.
      My Computer


  4. Posts : 14,901
    Windows 10 Pro
       #4

    Hi awesomealvin,

    When did you install the GPU?

    Have you recently cleaned up your partitions to reserve space?
      My Computers


  5. Posts : 4
    Windows 10
    Thread Starter
       #5

    axe0 said:
    Hi awesomealvin,

    When did you install the GPU?

    Have you recently cleaned up your partitions to reserve space?
    It was installed on the 16th, so 10 days ago from this reply.

    Cleaned my partitions as in hard drives? I haven't really cleaned them, but they've got plenty of space left. SSD where Windows is installed has over 100gb free space.

    Also to mention, I haven't got the crash two days after my previous reply. I haven't uninstalled or installed anything though, so I am sort of confused as to why it's not crashing anymore. Though if it does happen again, I'd still like to know what is causing it.
      My Computer


  6. Posts : 14,901
    Windows 10 Pro
       #6

    Your hard drives yes, I say 'partition' as that is what you see in Windows Explorer.I asked, because there's only 1 dump present whilst your eventlog shows multiple crashes.
    Code:
    2018-04-21T13:56:43.592        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000044 (0xffff9b04a0acd060, 0x000000000000120c, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 1a038bb1-eeb0-4284-81a3-913eebba2496.
    2018-04-20T12:16:06.500        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000044 (0xffffb104aa5439d0, 0x000000000000120c, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: fb91b348-26b5-4813-b247-8e39fc2fff2d.
    2018-04-17T23:10:26.663        The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffd70d8f8f5060, 0xffffd40ea6a5ac40, 0xffffd70d897da1d0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: a0562a40-6b42-405e-91bb-45d213b4084f.
    2018-03-29T17:14:13.915        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000119 (0x0000000000000005, 0xffffb383725fb000, 0xffffb383725658f0, 0x000000000000000c). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 09166212-5876-4d71-81c0-9faa50d56f15.
    2018-02-11T17:16:43.982        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8039ea7b370, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\021118-12062-01.dmp. Report Id: 83ae1682-196c-49c8-b4c5-3b5a385f0ec8.
    Due to the nature of the crash, I can't say with certainty if what I think is correct, but it looks like there are issues with the Focusrite USB device or its software.
    The common meaning of this crash is that there is 1 resource (as a somewhat better description for IRP) that 2 drivers both believe they own. 1 of them succeeds in using the resource and the other fails. In such situations the second driver covers the tracks of the first driver making it difficult to find the first one. Although there's only a minidump, which means the dump can't be analyzed in a matter a complete kernel dump can, it's very likely to be the Focusrite device or software as there are lots of USB related calls.
      My Computers


  7. Posts : 4
    Windows 10
    Thread Starter
       #7

    The Focusrite USB device is for my sound as I am using studio monitors. Is there a way to possibly prevent further crashes regarding the issue? I would assume reinstalling drivers?
      My Computer


  8. Posts : 14,901
    Windows 10 Pro
       #8

    Either reinstalling the driver or updating it usually does the trick yes.
      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 10:30.
Find Us




Windows 10 Forums