Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 406
  • Last Modified:

How to identify cause/s to blue screen of death

Hi,

I logged onto one of our client's servers (SBS 2008 server, standard edition, 64bit and SP1) today via RDP. While it was connecting i went off to do something else, coming back in 5mins to find the connection lost. I tried to reconnect and found that the server had restarted. Once i could log in again, an error message appeared saying that the server had suffered a blue screen (minidump attached).

Is there an easy way to interpret this mini dump? I searched through the event logs for this server and it didn't elude to any errors or possible causes leading up to this BSOD, so im guessing the minidump has the answers/causes. This is the first time it has happened in recent memory. The server was purposely restarted earlier in the day due to USB devices not being recognized, which the restart solved.  
Mini090611-01.dmp
0
LogicalSolutionsNZ
Asked:
LogicalSolutionsNZ
  • 3
  • 2
2 Solutions
 
rindiCommented:
It seems ekrn.exe caused this, which seems part of eset antivirus. Maybe check for patches or upgrades if it happens again.
0
 
rdudek101Commented:
I got ntoskrnl.exe that caused it.  Error code was 1E.  I usually blame the RAM first.  Try running a Memtest86+ 5 or 10 times and see if it finds any errors.

Also check the system Event Log and see if those errors were the same or different each time Bugcheck occured
0
 
LogicalSolutionsNZAuthor Commented:
Thanks,

I will run memtest at the earliest opportunity. I will also look into ESET NOD32 Antivirus as it just recently started prompting for re-license  
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
LogicalSolutionsNZAuthor Commented:
Oh and i looked at Bugcheck. There was only one event for it and it had the error code 1E
0
 
rdudek101Commented:
If it only happened once, it could also be a software glitch that caused it.  I think most anti-virus programs attach themselves to network drivers which could result in random blue screen as well.  I've seen that happen in the past.
0
 
LogicalSolutionsNZAuthor Commented:
Thanks guys, it hasn't happened before and hasn't happened again so i'll put it down to a small glitch
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now