BSOD 0x0000000a, 0x000000c2, 0x00000019 and the most common 0x00000024

Page 2 of 2 FirstFirst 12

  1. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #11

    Apparently the BSOD is caused by VirtualBox network driver.
    Code:
    BugCheck 19, {20, fffffa8006954d00, fffffa8006955040, 43492b8}
    
    *** WARNING: Unable to verify timestamp for VBoxNetFlt.sys
    *** ERROR: Module load completed but symbols could not be loaded for VBoxNetFlt.sys
    Probably caused by : VBoxNetFlt.sys ( VBoxNetFlt+2f0a )
    
    Followup: MachineOwner
    ---------
    But the driver is very latest.
    Code:
    fffff880`04d90000 fffff880`04db8000   VBoxNetFlt T (no symbols)           
        Loaded symbol image file: VBoxNetFlt.sys
        Image path: VBoxNetFlt.sys
        Image name: VBoxNetFlt.sys
        Timestamp:        Thu Jul 04 19:26:56 2013 (51D57F28)
        CheckSum:         0002F464
        ImageSize:        00028000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Which means that despite of being the prima facie cause, it is not the real cause.

    A deeper search reveals that the Realtek PCI GBE Family Controller driver is failing there.
    Code:
    fffff880`02fb09c8  fffff880`042b5f26Unable to load image Rt64win7.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
     Rt64win7+0xef26
    And the driver is really old.
    Code:
    fffff880`042a7000 fffff880`0432c000   Rt64win7 T (no symbols)           
        Loaded symbol image file: Rt64win7.sys
        Image path: Rt64win7.sys
        Image name: Rt64win7.sys
        Timestamp:        Fri Jun 10 12:03:15 2011 (4DF1BAAB)
        CheckSum:         0008B67F
        ImageSize:        00085000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    It may cause the virtual machines driver fail. You need to update it from Realtek . Get the Win7 and WinServer 2008 R2 Auto Installation Program, version 7.073, dated 2013/8/1.

    Let us know the results.
      My Computer


  2. Posts : 35
    Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #12

    No BSOD since the last one, still going to wait for a week or so if another appears.
      My Computer


  3. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #13

    I guess your issue is solved. If you want to wait more, take your time :)

    BTW, how many viruses were there in your computer? What was the net output of your virus removal mission? I see that you got to use all the possible tools.
      My Computer


  4. Posts : 35
    Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #14

    There were 3-5 trojans if I remember correctly. And with the last check there was only one.
      My Computer


  5. Posts : 35
    Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #15

    And again, two BSODs. Minidumps attached, no malicious software found with scans.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #16

    This time it is showing NTFS_FILE_SYSTEM (Stop 0x24) error.
    Code:
    BugCheck 24, {1904fb, fffff88002fcc8d8, fffff88002fcc130, fffff8800129ee27}
    
    Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+1e7 )
    
    Followup: MachineOwner
    ---------
    IMHO it would be the best for you if you format the entire HDD and perform a Clean Reinstall - Factory OEM Windows 7 .
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:46.
Find Us