BSOD - srvnet.sys and ntoskrnl.exe

Hi

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 have already ran checked disk for errors and ran a memtest86. Both showed no issues.


(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 :
==================================================

curagw said:

Hi

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 have already ran checked disk for errors and ran a memtest86. Both showed no issues.


(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 :
==================================================

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

Hi

Thanks for the response. For some strange reason, the minidumps disappear in my computer. The minidump was available last night, but I couldn't post it yesterday because the computer said I didn't have administrator rights even though I am the administrator. Today, I just checked to see if I can zip it, and the minidump is now gone.

This isn't the first time the minidumps will disappear on me. I have set it so it to "small memory dump" and kept the minidump directory with systemroot. My paging file is 4095 MB. Therefore, there shouldn't be a reason as to why my minidumps disappear.

Anyways, the above information was what I was able to copy from the minidump using bluescreenview.exe

In terms of history, I have had BSOD issues a week ago. It happened after I plugged and unplugged a headphone plug into the different audio jacks. I updated my drivers, and I didn't have a BSOD for a few days. During that time, I uninstalled my DVD ROM because it was acting up. Two nights ago I got a "A disk read error occurred" and that message did not fix until I reinstalled my DVD ROM (reconnected). Than windows booted as normal, but few minutes after that I got a BSOD in relation to the above. I haven't had a BSOD today, but I did nothing to fix the BSOD noted above other than check my hard drives for errors and running a memtest. Both which came good.

Strangely though, when I ran a hard drive error test using Ashampoo Winoptimizer, I found the following for Drive C and Drive E (partition of C):

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.

For Drive C:

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.

Do you think this may have something to do with the BSOD?

My computer just went through several BSODs in the last hour. I was watching a video and than BSOD occurred. I went onto Safe Mode, and there were two minidumps. I was about to copy them, and than another BSOD occurred. I went through repair start up twice, restore point one, and none of it seemed to work. Kept restarting telling me to do the same thing but nothing being fixed. Everytime i went to Windows logo, BSOD will occur (safe mode and normal mode). Than I shut off the computer, and I unplugged one of my hard drive (the one where I was watching video). Same scenario, no fix. Than I shut off again and unplugged dvd rom but reconnected hard drive. I was able to get into safe mode, and zip the minidump. Strange enough, the minidumps before the last boot all disappeared and I only had one minidump (the latest one).

Please see attached.

Please assist where you can, I am at a breaking point with this computer.

curagw said:

My computer just went through several BSODs in the last hour. I was watching a video and than BSOD occurred. I went onto Safe Mode, and there were two minidumps. I was about to copy them, and than another BSOD occurred. I went through repair start up twice, restore point one, and none of it seemed to work. Kept restarting telling me to do the same thing but nothing being fixed. Everytime i went to Windows logo, BSOD will occur (safe mode and normal mode). Than I shut off the computer, and I unplugged one of my hard drive (the one where I was watching video). Same scenario, no fix. Than I shut off again and unplugged dvd rom but reconnected hard drive. I was able to get into safe mode, and zip the minidump. Strange enough, the minidumps before the last boot all disappeared and I only had one minidump (the latest one).

Please see attached.

Please assist where you can, I am at a breaking point with this computer.

This crash was caused by your HD, hardware. BACK UP YOUR DATA NOW.

Please run a chkdsk to test it and download form the mfr their diagnostic software and run it

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.



Also please run a system file check to verify and repair your OS files and let us know what it says at the end of the report.

SFC /SCANNOW Command - System File Checker


let us know if you need help with any of this


ken J

Hi, Thanks for the response. I am backing up my files now. I have also scheduled CHKDSK /R /F for my drives, but I can't run them until all my files are backed up.

In the meantime, I ran a system file check and the computer found errors. Please see attached.

I don't know how to fix this, as the computer wouldn't repair automatically.

I got another BSOD while I was backing up one of my drives. Unfortunately, a minidump was not created. After I tried to restart in safe mode, it did not work and the "a disk read error" occurred. So I reconnected DVD ROM and the computer restarted. When straight to the scheduled chkdsk and Windows was able to restart.

Please see below two CHKDSK results (I have two more to go, and I will post those when they are finished).


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3db1.
The multi-sector header signature in file 0x548f is incorrect.
42 41 41 44 30 00 03 00 89 d0 27 0c 00 00 00 00 BAAD0.....'.....
02 00 02 00 38 00 03 00 00 03 00 00 00 04 00 00 ....8...........
Deleting corrupt file record segment 21647.
195328 file records processed. File verification completed.
149 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
Index entry SelfUpdate of index $I30 in file 0xe1e1 points to unused file 0x548f.
Deleting index entry SelfUpdate in index $I30 of file 57825.
Index entry SELFUP~1 of index $I30 in file 0xe1e1 points to unused file 0x548f.
Deleting index entry SELFUP~1 in index $I30 of file 57825.
250258 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
3 unindexed files scanned. CHKDSK is recovering remaining unindexed files.
3 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
195328 file SDs/SIDs processed. Cleaning up 60 unused index entries from index $SII of file 0x9.
Cleaning up 60 unused index entries from index $SDH of file 0x9.
Cleaning up 60 unused security descriptors.
Security descriptor verification completed.
27466 data files processed. CHKDSK is verifying Usn Journal...
35206704 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
195312 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
5124920 free clusters processed. Free space verification is complete.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Windows has made corrections to the file system.

61336575 KB total disk space.
40461136 KB in 122218 files.
75728 KB in 27469 indexes.
0 KB in bad sectors.
300031 KB in use by the system.
65536 KB occupied by the log file.
20499680 KB available on disk.

4096 bytes in each allocation unit.
15334143 total allocation units on disk.
5124920 allocation units available on disk.

Internal Info:
00 fb 02 00 c0 48 02 00 96 5e 04 00 00 00 00 00 .....H...^......
6e 03 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 n...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Chkdsk # 2


Checking file system on D:
The type of the file system is NTFS.
Volume label is Hippocampus.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
31488 file records processed. File verification completed.
0 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
36318 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
31488 file SDs/SIDs processed. Cleaning up 13 unused index entries from index $SII of file 0x9.
Cleaning up 13 unused index entries from index $SDH of file 0x9.
Cleaning up 13 unused security descriptors.
Security descriptor verification completed.
2416 data files processed. CHKDSK is verifying Usn Journal...
26450480 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
31472 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
173813128 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

789923839 KB total disk space.
94512332 KB in 28115 files.
11324 KB in 2417 indexes.
0 KB in bad sectors.
147667 KB in use by the system.
65536 KB occupied by the log file.
695252516 KB available on disk.

4096 bytes in each allocation unit.
197480959 total allocation units on disk.
173813129 allocation units available on disk.

Internal Info:
00 7b 00 00 50 77 00 00 7d b5 00 00 00 00 00 00 .{..Pw..}.......
37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7...............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Chkdsk #3

Checking file system on E:
The type of the file system is NTFS.
Volume label is Fruit.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
99328 file records processed. File verification completed.
159 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
117216 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
99328 file SDs/SIDs processed. Cleaning up 1 unused index entries from index $SII of file 0x9.
Cleaning up 1 unused index entries from index $SDH of file 0x9.
Cleaning up 1 unused security descriptors.
Security descriptor verification completed.
8945 data files processed. CHKDSK is verifying Usn Journal...
37620328 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
99312 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
15790608 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

94839695 KB total disk space.
31431900 KB in 90007 files.
39996 KB in 8946 indexes.
0 KB in bad sectors.
205367 KB in use by the system.
65536 KB occupied by the log file.
63162432 KB available on disk.

4096 bytes in each allocation unit.
23709923 total allocation units on disk.
15790608 allocation units available on disk.

Internal Info:
00 84 01 00 95 82 01 00 a8 93 02 00 00 00 00 00 ................
e8 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 ................


Chkdsk # 4 (Last one)

Checking file system on V:
The type of the file system is NTFS.
Volume label is Video Box.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
1792 file records processed. File verification completed.
1 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
1998 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
1792 file SDs/SIDs processed. Cleaning up 5 unused index entries from index $SII of file 0x9.
Cleaning up 5 unused index entries from index $SDH of file 0x9.
Cleaning up 5 unused security descriptors.
Security descriptor verification completed.
104 data files processed. CHKDSK is verifying Usn Journal...
1730064 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
1776 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
99980351 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

976759807 KB total disk space.
576738160 KB in 1361 files.
640 KB in 105 indexes.
0 KB in bad sectors.
99599 KB in use by the system.
65536 KB occupied by the log file.
399921408 KB available on disk.

4096 bytes in each allocation unit.
244189951 total allocation units on disk.
99980352 allocation units available on disk.

Internal Info:
00 07 00 00 c6 05 00 00 5d 0b 00 00 00 00 00 00 ........].......
01 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 ................


Please advise the next steps I should take.

After doing all of the above, I restarted my computer. Before Windows start up, the computer said "DISK READ ERROR" occurred. I followed the instructions and pressed CTRL + to restart. Than windows started normally.

Is this error happening because of the BSODs & CHKDSK errors? I thought through the CHKDSK above, the disks have been fixed.