Solved BSOD death, no minidumps generated, random times

[adjc98]

Hello,

I am trying to troubleshoot daily BSOD's on my Microsoft 7 computer. I had BSOD's last year on this same computer and it ended up being a bad stick of ram. Once I removed the ram the BSOD's went away.


Now I am seeing BSOD's on a daily basis, but the minidumps are not generating like they were last year. In fact the same minidumps from last summer are still in the minidump folder.

I am uploading the DM Log Collector. Let me know if you need more information.

I uploaded a new DM Log Collector file. The first one was corrupt.

 

[axe0]

Please provide some system information manually :ar: http://www.sevenforums.com/tutorials/374583-system-information-file-create-windows.html

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Make a photo of the result and post it.

 

[adjc98]

Ran SFC two times

I got this below when I ran SFC a second time. Do you still need the CBS file?

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>sfc/scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>

 

[axe0]

As said only when SFC cannot fix corruption.

 

[adjc98]

The computer is still blue screening about twice a day. I am still not getting any minidumps and the system log is stating:

The previous system shutdown at 1:56:25 PM on ‎6/‎22/‎2016 was unexpected.

I am not sure where to go from here. Any suggestions?

 

[axe0]

I requested a system file, this file is necessary for analysis for proper suggestions.
Some files contain event logs, the event logs may provide reasons why no dump is created. The system file is 1 of the files that contain event logs.

 

[adjc98]

I missed that file request, but see it now that you said something. I will try and get it uploaded tonight. Thanks.

 

[adjc98]

System Info

Here is the system info file. Let me know if you need anything else.

Thank you.

 

[adjc98]

Blue Screen Screenshot

I am also attaching a photo of the last blue screen that I saw. It had a Memory_Managment indicator on it so I ran a Windows memory test. It doesn't look like it found any bad pages.

Here is the xml of the result:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> 
- <System> 
<Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5F92BC59-248F-4111-86A9-E393E12C6139}" /> 
<EventID>1101</EventID> 
<Version>0</Version> 
<Level>4</Level> 
<Task>0</Task> 
<Opcode>0</Opcode> 
<Keywords>0x8000000000000000</Keywords> 
<TimeCreated SystemTime="2016-06-24T03:00:45.486668000Z" /> 
<EventRecordID>152494</EventRecordID> 
<Correlation /> 
<Execution ProcessID="4912" ThreadID="4916" /> 
<Channel>System</Channel> 
<Computer>MikeOffice</Computer> 
<Security UserID="S-1-5-18" /> 
</System> 
- <UserData> 
- <Results xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events"> 
<LaunchType>Manual</LaunchType> 
<CompletionType>Pass</CompletionType> 
<MemorySize>24269</MemorySize> 
<TestType>10</TestType> 
<TestDuration>269</TestDuration> 
<TestCount>12</TestCount> 
<NumPagesTested>6211823</NumPagesTested> 
<NumPagesUnTested>1125</NumPagesUnTested> 
<NumBadPages>0</NumBadPages> 
<T1NumBadPages>0</T1NumBadPages> 
<T2NumBadPages>0</T2NumBadPages> 
<T3NumBadPages>0</T3NumBadPages> 
<T4NumBadPages>0</T4NumBadPages> 
<T5NumBadPages>0</T5NumBadPages> 
<T6NumBadPages>0</T6NumBadPages> 
<T7NumBadPages>0</T7NumBadPages> 
<T8NumBadPages>0</T8NumBadPages> 
<T9NumBadPages>0</T9NumBadPages> 
<T10NumBadPages>0</T10NumBadPages> 
<T11NumBadPages>0</T11NumBadPages> 
<T12NumBadPages>0</T12NumBadPages> 
<T13NumBadPages>0</T13NumBadPages> 
<T14NumBadPages>0</T14NumBadPages> 
<T15NumBadPages>0</T15NumBadPages> 
<T16NumBadPages>0</T16NumBadPages> 
</Results> 
</UserData> 
</Event>

 

[axe0]

The msinfo is corrupted.

Please do not upload logs from the event viewer, those are mostly useless when it comes to BSODs. Run the DM Log Collector.

 

[adjc98]

Ok, will upload a new msinfo soon.

Thanks

 

[adjc98]

Here is the new msinfo file

Here is the new msinfo file. I tested this one to make sure it opens before I uploaded it.

 

[axe0]

Ensure the Crucial SSD firmware is up to date.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

1. Short Drive Self Test
2. Short generic
3. Long generic

If the short generic fails, no need for the long generic.

   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
Upload the chkdsk log :ar: http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• 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.

 

[adjc98]

SSD and Seatools?

In your instructions it says to run SeaTools, but then it says:

Do not run SeaTools on an SSD as the results will be invalid.

My hard drive is SSD.


Should I skip running Seatools and run the others chkdsk and HD Tune?

 

[axe0]

My reply is a standard reply when testing the hard drives, skip SeaTools for SSD as it says..

 

[adjc98]

Screenshots

Thanks,

I ran the tests. Here are the screenshots. Also the crucial SSD is not upgraded to the highest firmware. It looks like it is behind an iteration. I need to backup the hard drive in order to upgrade. Should I go ahead and back up the hard drive and upgrade the firmware? It will probably take me a while to make sure everything is backed up correctly. Let me know if I missed something with the tests.

 

[axe0]

Please run the chkdsk command again to see if there still are corrections that need to be made.

 

[adjc98]

I ran chkdsk again

Here is the txt file for the new chkdsk check.

 

[axe0]

That looks better

See if you get problems again.

Should I go ahead and back up the hard drive and upgrade the firmware?

IMHO it shouldn't be a question necessary to ask, because I asked to do it

 

[adjc98]

Upgrade for firmware

Ok, I will go ahead and try and upgrade the firmware today.

It seems like the Blue screens have either stopped or slowed down tremendously.

The last confirmed blue screen I saw was on the 24th. There was an indication of one on the 26th, but I think I might have manually caused that shut down.

Anyway, after I upgrade the firmware and monitor a bit longer, I will mark this a solved.

Thank You!