TechSpot

BSOD - srvnet.sys

By curagw
Jan 12, 2011
Post New Reply
  1. Hi

    Recently my computer has been shutting down because of BSOD.
    Using the BlueScreenView program, I managed to get the below information. Any assistance would be much appreciated.

    I run x64 Windows 7 Ultimate. The major changes I've made is to reinstall a DVD Rom Driver, because last night the windows wouldn't start (A disk read error occurred), so when I plugged the DVD ROM back, that fixed that issue.

    (Top panel of BlueScreenView _crash information)
    ==================================================
    Dump File : 011311-30357-01.dmp
    Crash Time : 13/01/2011 7:28:25 AM
    Bug Check String : CRITICAL_OBJECT_TERMINATION
    Bug Check Code : 0x000000f4
    Parameter 1 : 00000000`00000003
    Parameter 2 : fffffa80`07489670
    Parameter 3 : fffffa80`07489950
    Parameter 4 : fffff800`031995d0
    Caused By Driver : srvnet.sys
    Caused By Address : srvnet.sys+ff1cc670
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Computer Name :
    Full Path : C:\Windows\Minidump\011311-30357-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7600
    Dump File Size : 366,811
    ==================================================

    Bottom panel - driver information
    (the pink highlighted drivers - found in stack)
    ==================================================
    Filename : ntoskrnl.exe
    Address In Stack : ntoskrnl.exe+3fc652
    From Address : fffff800`02e1e000
    To Address : fffff800`033fa000
    Size : 0x005dc000
    Time Stamp : 0x4c1c44a9
    Time String : 19/06/2010 3:16:41 PM
    Product Name : Microsoft® Windows® Operating System
    File Description : NT Kernel & System
    File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
    Company : Microsoft Corporation
    Full Path : C:\Windows\system32\ntoskrnl.exe
    ==================================================

    ==================================================
    Filename : srvnet.sys
    Address In Stack : srvnet.sys+ff1cc670
    From Address : fffff880`082bd000
    To Address : fffffbb5`082ea000
    Size : 0x000003350002d000
    Time Stamp : 0x4c7732f4
    Time String : 27/08/2010 2:37:24 PM
    Product Name :
    File Description :
    File Version :
    Company :
    Full Path :
    ==================================================

    other drivers (in lower panel)
    see attached.

    Sorry I could not attach minidump, my computer says I don't have permission to open this file, when I am the admin and only user. I don't know how to bypass that.
     

    Attached Files:

  2. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    srvnet.sys relates to a Server Network driver... Check your memory using Memtest86 and check your hard drive for errors
     
  3. curagw

    curagw TS Rookie Topic Starter

    I ran the memtest today and it passed with no errors.

    I did think maybe it had to do with my hard drive. But when I checked my hard drives for errors via Windows (i.e. Drive C >> Disk Error Check) the computer found nothing (yesterday and today). But than when i checked for disk errors using Ashampoo Winoptimizer, I found the following for Drive C and Drive E (partition of C):

    For Drive C (yesterday):
    Wed 12. Jan. 2011, 21:23:10: C:\ Volume Label: , File System: NTFS
    Wed 12. Jan. 2011, 21:23:16: Attribute record (128, "") from file record segment 131457
    is corrupt.
    Wed 12. Jan. 2011, 21:23:17: Attribute record (128, "") from file record segment 182212
    is corrupt.
    Wed 12. Jan. 2011, 21:23:17: 195328 file records processed.
    Wed 12. Jan. 2011, 21:23:17: File verification completed.
    Wed 12. Jan. 2011, 21:23:17: 159 large file records processed.

    For Drive C (today): - the strange thing is, the errors changed but I didn't make any changes to the system.

    Thu 13. Jan. 2011, 18:47:00: C:\ Volume Label: , File System: NTFS
    Thu 13. Jan. 2011, 18:47:08: 195328 file records processed.
    Thu 13. Jan. 2011, 18:47:08: File verification completed.
    Thu 13. Jan. 2011, 18:47:08: 159 large file records processed.
    Thu 13. Jan. 2011, 18:47:08: 0 bad file records processed.
    Thu 13. Jan. 2011, 18:47:08: 2 EA records processed.
    Thu 13. Jan. 2011, 18:47:08: 44 reparse records processed.
    Thu 13. Jan. 2011, 18:47:31: Index entry pando.save in index $I30 of file 68056 is incorrect.
    Thu 13. Jan. 2011, 18:47:31: Index entry PANDO~1.SAV in index $I30 of file 68056 is incorrect.
    Thu 13. Jan. 2011, 18:47:31: Index entry f_00103b in index $I30 of file 68813 is incorrect.
    Thu 13. Jan. 2011, 18:47:50: 250180 index entries processed.
    Thu 13. Jan. 2011, 18:47:50: Index verification completed.

    For Drive E (the second partition for drive C):

    Wed 12. Jan. 2011, 21:23:10: C:\ Volume Label: , File System: NTFS
    Wed 12. Jan. 2011, 21:23:16: Attribute record (128, "") from file record segment 131457
    is corrupt.
    Wed 12. Jan. 2011, 21:23:17: Attribute record (128, "") from file record segment 182212
    is corrupt.
    Wed 12. Jan. 2011, 21:23:17: 195328 file records processed.
    Wed 12. Jan. 2011, 21:23:17: File verification completed.
    Wed 12. Jan. 2011, 21:23:17: 159 large file records processed.
    Wed 12. Jan. 2011, 21:50:08: 15790020 free clusters processed.
    Wed 12. Jan. 2011, 21:50:08: Free space verification is complete.
    Wed 12. Jan. 2011, 21:50:09: The Volume Bitmap is incorrect.
    Wed 12. Jan. 2011, 21:50:09: 94839695 KB total disk space.
    Wed 12. Jan. 2011, 21:50:09: 31434252 KB in 90025 files.
    Wed 12. Jan. 2011, 21:50:09: 39996 KB in 8945 indexes.
    Wed 12. Jan. 2011, 21:50:09: 205367 KB in use by the system.
    Wed 12. Jan. 2011, 21:50:09: 65536 KB occupied by the log file.
    Wed 12. Jan. 2011, 21:50:09: 63160080 KB available on disk.
    Wed 12. Jan. 2011, 21:50:09: 4096 bytes in each allocation unit.
    Wed 12. Jan. 2011, 21:50:09: 23709923 total allocation units on disk.
    Wed 12. Jan. 2011, 21:50:09: 15790020 allocation units available on disk.

    Could you please advise as to what I should do next? I can't fix it through Windows because Windows is not picking it up. WinOptimizer will not rectify the issue.
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...