Irregular BSODs for many months.

Page 3 of 9 FirstFirst 12345 ... LastLast

  1. Posts : 39,972
    windows 10 professional version 1607 build 14393.969 64 bit
       #21

    For any BSOD:

    a) run the V2 log collector to collect new log files

    b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive
      My Computer


  2. Posts : 759
    Windows 10 Home x64
       #22

    MrPepka said:
    Maybe the driver is guilty, but I bet
    that this driver was in the wrong place at the wrong time
    That's correct, but it doesn't necessarily points towards the faulty disk. It could be faulty RAM, MoBo, dodgy driver (audio or MEI. Or RST. Or combination of all?) - anything.

    We need more data to jump to some realistic conclusions - but equally: getting all relevant drivers updated whilst obtaining it will not hurt.
      My Computers


  3. Posts : 39
    Windows 10
    Thread Starter
       #23

    Very pleased to see you all take an active interest in this case.

    I've done various diagnostic tests a couple of months ago (when these issues were still going on). Both, the ones from the bootup screen and this 3rd party test called memtest86 Both tests gave me a pass result. Although, I think the one from the bootup screen just does one run and then gives the result after which if you proceed, it restarts. Whereas the memtest tool just repeats the scan again after the first pass to pass the scan again. It took me several hours to get to the first pass (I have 32 gigs of Ram) so I assumed one pass was enough.
    Apparently, according to a couple of threads online, people say that about 3-4 passes are required just to be sure. I haven't done so because doing so would literally take me about 24 hours+ of RAM test. And I would like to exhaust all options before I do such intensive tests.
    However, I'm willing to do a fresh test if you guys say so.

    Is there also a possibility that there is more than one issue causing the crash? I say so because, as I took an investigative approach to narrow down these problems, the symptoms are all over the place. Sometimes they don't crash for a whole week (happened twice) and other times they crash once a day. I also could be doing something totally random like browsing, watching some videos, listening to music, gaming etc and this crash could happen. Nothing particular I do 'triggers' the crash. I've kept the computer idle in safe mode for 48 hours+ and there was no crash (during a period where it crashes at least once every 48 hours). Which makes me think it may not be hardware after all.
    There is no discernable pattern here. Makes me tear my hair off!

    Finally, why doesn't windows automatically update my drivers? Is there a dependable software I can install which would install these drivers without me having to manually check them regularly? I've been told that driver installing softwares like DriveEasy and Driverpack are unnecessary and possibly install backdoors/adwares, so I'm staying away from those. Also, if software A says driver X is outdated, software B says driver Y is outdated. There is no uniformity between them. Hence, I distrust them more. I did scan my computer using the dell website and installed the critical updates they recommended. I've been also told that even though some drivers are not the latest, they are what's right for my computer and hardware. Meaning super latest may not be what's right for my pc. A safe bet, from multiple sources, was the dell homepage itself for installing drivers. Where the drivers they recommend are most usually enough.

    Sorry to make this seem like a rant. Once again, thank you guys for the active interest.
      My Computer


  4. Posts : 39,972
    windows 10 professional version 1607 build 14393.969 64 bit
       #24

    Please update the thread with a new V2.
      My Computer


  5. Posts : 39
    Windows 10
    Thread Starter
       #25

    zbook said:
    Please update the thread with a new V2.
    What's that? And how do I do it?

    - - - Updated - - -

    zbook said:
    Please update the thread with a new V2.
    What's that? And how do I do it?

    Edit : Nevermind. Got it
      My Computer


  6. Posts : 14,894
    Windows 10 Pro
       #26

    MrPepka said:
    I have never had problems with Realtek drivers or their stability. An error code indicates a disk malfunction. And the fact that Realtek's driver was guilty may be due to the fact that the driver was in a place where the bad sector is (maybe because of that the driver has even been damaged)
    It is more likely that the data the system was trying to page in had become corrupted or that the IRP had trouble along the way of paging in the data than the driver being located on a bad sector.
      My Computers


  7. Posts : 14,894
    Windows 10 Pro
       #27

    krzemien said:
    Well, disk has been checked apparently - I've not seen the results myself but OP claims all was well. So I daresay issue lies elsewhere - would not trust MS codes & explanations too much without looking into DMPs...

    Thus I agree with OP and would still pursue investigative avenue and try to narrow down the issue itself - so far there's nothing concrete to put finger on, it could be anything.
    Based on experience I would trust the MS codes and explanations, knowing what they could mean.

    According to OP, we got a couple of different crashes, however none of them seem to generate a crash dump file or even log the crashes. There is only one event in the eventlogs about a manually initiated crash which OP explained.

    There also appear to be a lot of dump file creation failures, which in my opinion is not very surprising with a 0x154, 0xEF and 0x7A which each have a few causes in common. Hard drive and RAM.

    Based on all this, I would test the hard drive and RAM first before doing anything else.

    @DrakeJen, please run the extensive test of the bootable diagnostic test.
      My Computers


  8. Posts : 39
    Windows 10
    Thread Starter
       #28

    zbook said:
    For any BSOD:

    a) run the V2 log collector to collect new log files

    b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive
    The updated V2 log is here

    Do confirm if you want the memory.dmp file because it's 29 GB.
      My Computer


  9. Posts : 14,894
    Windows 10 Pro
       #29

    When was the memory.dmp file created?
      My Computers


  10. Posts : 39,972
    windows 10 professional version 1607 build 14393.969 64 bit
       #30

    When posting V2 please use one of these 4 methods: (see posting instructions)


    1) Upload directly into the thread without a share link
    2) share links using: one drive, drop box, or google drive
      My Computer


 

  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 04:11.
Find Us




Windows 10 Forums