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

BSOD going on for a while


  • Please log in to reply
11 replies to this topic

#1 jimmyfoddrell

jimmyfoddrell

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:01 PM

Posted 16 August 2017 - 09:54 AM

About 2 months ago, my Windows 2008 server (32 bit) begin experiencing BSOD's.  Too my knowledge no software was updated or added, and no new hardware has been added.  I have no experience in reading the debugger, but I have tried.  I did run MEMTest twice, one of them running 12 hrs with over 10 passes.  It shows no issues.  The HP diagnostics show no hardware problems.   Attached File  SysnativeFileCollectionApp.zip   1021.98KB   3 downloadsAttached File  PERBDC.txt   229.61KB   1 downloadsAttached File  SysnativeFileCollectionApp.zip   1021.98KB   3 downloads

 

 

Any help will be greatly appreciated.  Thanks in advance. 



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:06:01 PM

Posted 16 August 2017 - 10:18 AM

Hi,

Unfortunately, I can't get symbols to load for your dump files, so we'll be groping in the dark in your case. However, I did manage to get some information out of one dump file, and it said that it was probably caused by hardware.

 

I'd like you to run Seagate SeaTools for Windows. Be sure to test all your drives with the S.M.A.R.T. and Long Generic tests to ensure the hard drives are healthy. If the Seagate tests pass, I would proceed with a CHKDSK to check the file system:

:step1: Check Disk

WARNING: It is recommended that you backup ALL your files. If CHKDSK finds and repairs a corrupted sector, you may lose your data.

  • Click Start, enter cmd.exe in the Search box, right-click on cmd.exe, and then click Run as administrator.
  • Type the following command and hit ENTER:
chkdsk /R
  • You should see this message:
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process.  Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
  • Type Y and hit Enter on your keyboard.
  • Restart your computer and CHKDSK will run.

Once CHKDSK is complete, we need the log:

  • Click Start, enter powershell.exe in the Search box, right-click on powershell.exe, and then click Run as administrator.
  • Copy this command:
Get-WinEvent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file $Env:UserProfile\Desktop\CHKDSKResults.txt
  • Right-click in Powershell to paste the command.
  • You will find CHKDSKResults.txt on your Desktop. Copy/paste that log in your next reply.

Apart from that, there's a chance that this could be driver related (some of the bugchecks seem to indicate that). Please run Driver Verifier according to these instructions. I'm not sure whether if the dumps will be readable, but I hope we'll able to get some information out of them even with no symbols.

Regards,
bwv848

P.S. If you have time, please go ahead and update your BIOS + drivers from HP's website, best thing to do since we don't know exactly the culprit.


Edited by bwv848, 16 August 2017 - 10:19 AM.

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


#3 jimmyfoddrell

jimmyfoddrell
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:01 PM

Posted 16 August 2017 - 10:30 AM

Thanks so much for the reply. I did rebuild the server last week with a fresh install of the OS.  The Bios has the latest firmware and the server has the latest drivers installed. 

 

I will follow your instructions and post the results. 



#4 jimmyfoddrell

jimmyfoddrell
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:01 PM

Posted 16 August 2017 - 01:56 PM

I tried running the Seagate Tools. It would only recognize 1 logical drive, which did pass the tests.  I then installed WD Data LifeGuard Diags and ran the extended tests.  Results are below. 

 

I will run the chkdsk after hours today on both logical drives and post results. I will then run the verifier as instructed. 

 

 

 

 

est Option: EXTENDED TEST 
Model Number: HP LOGICAL VOLUME 
Unit Serial Number: P57820PXQS50DZ 
Firmware Number: 2.80 
Capacity: 145.67 GB 
SMART Status: Not Available 
Test Result: PASS 
Test Time: 13:57:55, August 16, 2017 
 
 
Test Option: EXTENDED TEST 
Model Number: HP LOGICAL VOLUME 
Unit Serial Number: P57820PXQS50DZ 
Firmware Number: 2.80 
Capacity: 72.83 GB 
SMART Status: Not Available 
Test Result: PASS 
Test Time: 14:16:54, August 16, 2017 


#5 jimmyfoddrell

jimmyfoddrell
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:01 PM

Posted 17 August 2017 - 02:16 PM

Below are the results from CHKDSK /R

 

Also, I was able to get a DUMP with Verifier running.  I am unsure where to upload too. Any sugestions?

 

Level Date and Time Source Event ID Task Category
Information 8/16/2017 6:16:32 PM Microsoft-Windows-Wininit 1001 None "
 
Checking file system on D:
The type of the file system is NTFS.
Volume label is New Volume.
 
A disk check has been scheduled.
Windows will now check the disk.                         
  142784 file records processed.                                  
 
  238 large file records processed.                            
 
  0 bad file records processed.                              
 
  0 EA records processed.                                    
 
  3 reparse records processed.                               
 
  160558 index entries processed.                                 
 
  0 unindexed files processed.                               
 
  142784 security descriptors processed.                          
 
Cleaning up 8 unused index entries from index $SII of file 0x9.
Cleaning up 8 unused index entries from index $SDH of file 0x9.
Cleaning up 8 unused security descriptors.
  8888 data files processed.                                    
 
CHKDSK is verifying Usn Journal...
  538925032 USN bytes processed.                                     
 
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  142768 files processed.                                         
 
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  4583346 free clusters processed.                                 
 
Free space verification is complete.
Windows has checked the file system and found no problems.
 
 142249183 KB total disk space.
 123118260 KB in 107569 files.
     53288 KB in 8889 indexes.
         0 KB in bad sectors.
    744251 KB in use by the system.
     65536 KB occupied by the log file.
  18333384 KB available on disk.
 
      4096 bytes in each allocation unit.
  35562295 total allocation units on disk.
   4583346 allocation units available on disk.
 
Internal Info:
c0 2d 02 00 f5 c6 01 00 23 0d 03 00 00 00 00 00  .-......#.......
69 0d 00 00 03 00 00 00 00 00 00 00 00 00 00 00  i...............
42 00 00 00 a2 74 d2 77 c0 54 2a 00 c0 4c 2a 00  B....t.w.T*..L*.
 
 
 
Level Date and Time Source Event ID Task Category
Information 8/16/2017 5:32:22 PM Microsoft-Windows-Wininit 1001 None "
 
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.                         
  108992 file records processed.                                  
 
  663 large file records processed.                            
 
  0 bad file records processed.                              
 
  0 EA records processed.                                    
 
  60 reparse records processed.                               
 
  137444 index entries processed.                                 
 
  0 unindexed files processed.                               
 
  108992 security descriptors processed.                          
 
Cleaning up 2081 unused index entries from index $SII of file 0x9.
Cleaning up 2081 unused index entries from index $SDH of file 0x9.
Cleaning up 2081 unused security descriptors.
  14227 data files processed.                                    
 
CHKDSK is verifying Usn Journal...
  1122024 USN bytes processed.                                     
 
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  108976 files processed.                                         
 
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  11717917 free clusters processed.                                 
 
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
 
  71126623 KB total disk space.
  24012480 KB in 89630 files.
     59192 KB in 14228 indexes.
         0 KB in bad sectors.
    183279 KB in use by the system.
     65536 KB occupied by the log file.
  46871672 KB available on disk.
 
"


#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:06:01 PM

Posted 17 August 2017 - 02:33 PM

Thanks, CHKDSK log looks fine. Sometimes systems behave much better after a CHKDSK because the file system has been cleaned up, but there doesn't appear to be much corruption on your hard drives. To send me the dumps, copy the latest dump file(s) in C:\Windows\Minidump to your Desktop and zip it/them up (the file(s) must be zipped so it/they can be uploaded). To upload the file, please click Reply to this topic on the top right-side of the page. Next, on the bottom, under Attach Files, click Browse..., then click Open, and finally Attach This File. To finalize and post your post, click Add Reply. Of course, make sure you zip the .dmp files before posting, or the forums won't allow you to upload it.


Edited by bwv848, 17 August 2017 - 02:33 PM.

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


#7 jimmyfoddrell

jimmyfoddrell
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:01 PM

Posted 17 August 2017 - 02:41 PM

Attached File  minidumps0817.zip   67.05KB   1 downloadsThanks for the response. The MEMORY.DMP created by the verifier is over 600 MB zipped. Do you want that one?  Also, I have attached the minidumps created, some that were while verifier was running.  



#8 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:06:01 PM

Posted 17 August 2017 - 04:48 PM

You're welcome. Unfortunately, I'm getting symbol errors for the dump files again, so I can't get any information out of them at all. I was actually hoping that one of the dump files would have a third-party driver listed directly on the call stack, so that I could a symbol error for that third-party component, regardless whether if I have kernel symbols.

 

Can you open an Elevated Command Prompt and enter the following

verifier /query | clip

Driver Verifier info will be saved to your clipboard. Simply paste it in your next reply.

 

I suggest you monitor the server's temps with HWMonitor:

 

:step1: HWMonitor by CPUID

  • Download and save CPUID from here.

  • Navigate to the directory in which you saved the ZIP file.

  • Right-click on the downloaded ZIP file, click Extract all, taking note of where the files will be extracted, and then hit Extract.

  • Open up the extracted folder, right-click on HWMonitor_x64.exe (or HWMonitor_x32.exe, if your system is 32-bit) and select Run as administrator. Please accept any User Account Control prompts.

  • Monitor your temps and ensure nothing is overheating

I honestly suspect this is a hardware issue (since the server is about a decade old), but I can't say for sure.


Edited by bwv848, 17 August 2017 - 04:49 PM.

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


#9 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:06:01 PM

Posted 17 August 2017 - 04:53 PM

One more thing, I should have mentioned... :) Please run Prime95 (blend test) according to these instructions, following the instructions carefully: http://www.carrona.org/hwdiag.html#prime95 I'd like to see the results.txt file it creates if possible too.

 

BTW, when you "rebuilt your server" what exactly did you do? It was after the BSODs, right?


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


#10 jimmyfoddrell

jimmyfoddrell
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:01 PM

Posted 21 August 2017 - 06:52 AM

TO rebuild the server, I formatted the OS drive and reinstalled the OS. The BSOD's have occurred before and after the rebuild.   
 
 
Here are the results of the verifier query     
 
8/21/2017, 7:47:26 AM
No drivers are currently verified.


#11 jimmyfoddrell

jimmyfoddrell
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:01 PM

Posted 21 August 2017 - 02:47 PM

Below are the results from the PRIME95 test.  It ran for almost 2 hrs. I can rerun tomorrow for a longer period of time if needed.

 

[Mon Aug 21 14:08:17 2017]
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
[Mon Aug 21 14:13:26 2017]
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
[Mon Aug 21 14:18:48 2017]
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 12K passed!
Self-test 12K passed!
[Mon Aug 21 14:23:53 2017]
Self-test 12K passed!
Self-test 12K passed!
Self-test 672K passed!
Self-test 672K passed!
[Mon Aug 21 14:29:03 2017]
Self-test 672K passed!
Self-test 672K passed!
Self-test 16K passed!
Self-test 16K passed!
Self-test 16K passed!
[Mon Aug 21 14:35:51 2017]
Self-test 16K passed!
Self-test 800K passed!
Self-test 800K passed!
Self-test 800K passed!
[Mon Aug 21 14:41:01 2017]
Self-test 800K passed!
Self-test 24K passed!
Self-test 24K passed!
Self-test 24K passed!
[Mon Aug 21 14:46:28 2017]
Self-test 24K passed!
Self-test 960K passed!
Self-test 960K passed!
Self-test 960K passed!
[Mon Aug 21 14:51:57 2017]
Self-test 960K passed!
Self-test 32K passed!
Self-test 32K passed!
Self-test 32K passed!
[Mon Aug 21 14:57:20 2017]
Self-test 1120K passed!
Self-test 32K passed!
Self-test 1120K passed!
Self-test 1120K passed!
[Mon Aug 21 15:02:35 2017]
Self-test 48K passed!
Self-test 1120K passed!
Self-test 48K passed!
Self-test 48K passed!
[Mon Aug 21 15:08:06 2017]
Self-test 1280K passed!
Self-test 48K passed!
Self-test 1280K passed!
Self-test 1280K passed!
[Mon Aug 21 15:13:10 2017]
Self-test 64K passed!
Self-test 1280K passed!
Self-test 64K passed!
Self-test 64K passed!
[Mon Aug 21 15:18:22 2017]
Self-test 1440K passed!
Self-test 1440K passed!
Self-test 64K passed!
Self-test 1440K passed!
Self-test 80K passed!
[Mon Aug 21 15:26:19 2017]
Self-test 80K passed!
Self-test 1440K passed!
Self-test 80K passed!
Self-test 1600K passed!
[Mon Aug 21 15:31:22 2017]
Self-test 1600K passed!
Self-test 80K passed!
Self-test 1600K passed!
Self-test 96K passed!
[Mon Aug 21 15:37:12 2017]
Self-test 96K passed!
Self-test 1600K passed!
Self-test 1920K passed!
Self-test 96K passed!
[Mon Aug 21 15:42:52 2017]
Self-test 1920K passed!
Self-test 96K passed!
Self-test 128K passed!


#12 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:06:01 PM

Posted 23 August 2017 - 08:55 PM

Hi,

 

Since you reinstalled your OS and are still getting BSODs (plus you've updated your BIOS) I'm certain it's most likely hardware. With older systems (and no dump files) it's really hard to tell what's going on. Can you run Prime95 for 24 hours? Let's run this RAM test for 24 hours: http://hcidesign.com/memtest/ Please also try to run MemTest86 when the system is cold, once.

 

Regards...

bwv848


Edited by bwv848, 23 August 2017 - 08:56 PM.

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