Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random BSOD's don't know whats going on


  • Please log in to reply
3 replies to this topic

#1 TitanGuard

TitanGuard

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:08:15 AM

Posted 29 April 2017 - 03:48 AM

this Speccy report should give all the required answers.
http://speccy.piriform.com/results/kTCc5zPeyymD5yP1M0A1KkJ


 

Attached Files



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:15 AM

Posted 02 May 2017 - 09:43 PM

This is an interesting case. The attached dump files indicate three different bugchecks: STOP 0x000000F4: CRITICAL_OBJECT_TERMINATIONs, STOP 0x0000007A: KERNEL_DATA_INPAGE_ERRORs, and STOP 0x00000124: WHEA_UNCORRECTABLE_ERRORs. I've never debugged a 0xF4 before, so we can only have a look at the 0x124s and 0x7As, unfortunately. First, however, please uninstall ALL MSI and GIGABYTE software installed on your machine — they are known to cause BSODs.

From the latest 0x124 dump file...

We need to inspect the WHEA_ERROR_RECORD structure, by utilizing the !errrec command coupled with the second parameter of the 0x124 bugcheck:

6: kd> !errrec fffffa8007a1e028
===============================================================================
Common Platform Error Record @ fffffa8007a1e028
-------------------------------------------------------------------------------
Record Id     : 01d2bfe7d0b73586
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/28/2017 6:22:58 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007a1e0a8
Section       @ fffffa8007a1e180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000006

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007a1e0f0
Section       @ fffffa8007a1e240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000006
CPU Id        : c3 06 03 00 00 08 10 06 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8007a1e240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007a1e138
Section       @ fffffa8007a1e2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL0_WR_ERR (Proc 6 Bank 1)
  Status      : 0xbf80000000000124
  Address     : 0x000000021b1816c0
  Misc.       : 0x0000000000000086

We have a Cache Error on Processor 6, Bank One. Similiar results are shown from earlier dump files:

7: kd> !errrec fffffa8007a22028
===============================================================================
Common Platform Error Record @ fffffa8007a22028
-------------------------------------------------------------------------------
Record Id     : 01d2bfe7ec224086
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/28/2017 6:23:24 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007a220a8
Section       @ fffffa8007a22180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000007

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007a220f0
Section       @ fffffa8007a22240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000007
CPU Id        : c3 06 03 00 00 08 10 07 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8007a22240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007a22138
Section       @ fffffa8007a222c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL0_WR_ERR (Proc 7 Bank 1)
  Status      : 0xbf80000000000124
  Address     : 0x000000010582e640
  Misc.       : 0x0000000000000086

Now for the 0x7As.

It's important to understand that this bugcheck often indicates a problem with the disk, though malware, improper cabling, BIOS corruption are other probable causes. From two dump files that I could find...

0: kd> .bugcheck
Bugcheck code 0000007A
Arguments fffff6fc`40009a48 ffffffff`c000000e 00000001`7fb60860 fffff880`01349748
0: kd> .bugcheck
Bugcheck code 0000007A
Arguments fffff6fc`40009a58 ffffffff`c000000e 00000001`db5cd860 fffff880`0134b748

So we have a good generalization just by looking at the parameters. It seems to be that the disk subsystem has experienced a failure (according to the WinDbg help file).

However, one dump file blames Avast:

4: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff880`09fdb8f8 fffff800`034c2358 nt!KeBugCheckEx
01 fffff880`09fdb900 fffff800`034714f7 nt!MiWriteComplete+0x278
02 fffff880`09fdb9c0 fffff800`0347b473 nt!IopCompletePageWrite+0x57
03 fffff880`09fdb9f0 fffff800`0347b727 nt!KiDeliverApc+0x1e3
04 fffff880`09fdba70 fffff880`00fdd6e6 nt!KiApcInterrupt+0xd7
05 fffff880`09fdbc08 fffff880`00fde9fa ataport!IdeStartDeviceRequest+0x342
06 fffff880`09fdbc20 fffff880`00fda4ee ataport!IdePortPdoDispatch+0xb6
07 fffff880`09fdbc50 fffff880`03caa3b8 ataport!IdePortDispatch+0x16
08 fffff880`09fdbc80 fffffa80`069ab060 aswSP+0x3e3b8 <=== Avast Driver
09 fffff880`09fdbc88 00000000`00000001 0xfffffa80`069ab060
0a fffff880`09fdbc90 fffffa80`09ed5dc0 0x1
0b fffff880`09fdbc98 fffffa80`09ed5dc0 0xfffffa80`09ed5dc0
0c fffff880`09fdbca0 00000009`e8831000 0xfffffa80`09ed5dc0
0d fffff880`09fdbca8 fffff880`0186a445 0x00000009`e8831000
0e fffff880`09fdbcb0 fffff880`0186a975 CLASSPNP!ServiceTransferRequest+0x355
0f fffff880`09fdbd50 fffff880`00eb50af CLASSPNP!ClassReadWrite+0xd5
10 fffff880`09fdbda0 fffff880`00eca18c partmgr!PmGlobalDispatch+0x9f
11 fffff880`09fdbdd0 fffff880`0181a2bf volmgr!VmReadWrite+0x11c
12 fffff880`09fdbe10 fffff880`0181a53c fvevol!FveReadWrite+0x47
13 fffff880`09fdbe50 fffff880`0181a593 fvevol!FveFilterRundownReadWrite+0x1dc
14 fffff880`09fdbeb0 fffff880`010044a9 fvevol!FveFilterRundownWrite+0x2f
15 fffff880`09fdbee0 fffff880`0126f03a volsnap! ?? ::FNODOBFM::`string'+0x19f8
16 fffff880`09fdbf30 fffff800`0347fe77 Ntfs!NtfsStorageDriverCallout+0x16
17 fffff880`09fdbf60 fffff800`0347fe38 nt!KxSwitchKernelStackCallout+0x27
18 fffff880`03524660 00000000`00000000 nt!KiSwitchKernelStackContinue
4: kd> lm k vm ASWSP
start             end                 module name
fffff880`03c6c000 fffff880`03d18000   aswSP    T (no symbols)           
    Loaded symbol image file: aswSP.sys
    Image path: \SystemRoot\system32\drivers\aswSP.sys
    Image name: aswSP.sys
    Timestamp:        Tue Mar 28 11:24:26 2017 (58DA802A)
    CheckSum:         0008D69A
    ImageSize:        000AC000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I sincerely doubt Avast's related though.

All of the above seem to point to hardware. I have several suggestions:
-update your BIOS
-update Windows
-run MemTest86 for a minimum of eight passes. Here's a good guide if you need help.
-run Seagate SeaTools for Windows. Be sure to test all your drives with the S.M.A.R.T. and Long Generic tests.
-run Prime95 (read the details in the link)
-run these remaining hardware diagnostics
-monitor your temps

Let me know how everything goes.

Regards,
bwv848


Edited by bwv848, 02 May 2017 - 09:45 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 TitanGuard

TitanGuard
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:08:15 AM

Posted 04 May 2017 - 01:50 AM

thank you very much, i updated my BIOS and i haven't had a BSOD since then. i'll keep this page bookmarked encase i start getting them again, i even got to install the full 16 GB of RAM i thought was going bad from this. I tested those long before this and they were fine, it was just a precaution, anyway, enough rambling from me, thank you!



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:15 AM

Posted 04 May 2017 - 08:28 AM

Glad we could help, you're welcome.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users