Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

135657

July 17th, 2013 03:00

Constant BSOD on Dell E6520 after BIOS update or Driver Update

Hello there to All.

For the last couple of months my Dell Latitude E6520 (W7pro x64) has been going on a BSOD campaign and is really making me mad. The Blue Screen Error is mostly KMODE_EXCEPTION_NOT_HANDLED 0x0000001e, and has no apparent pattern of appearance, time wise, program wise or any other way wise.

Additionally this also happened when I connect a second Display, either on the Laptop or on the Docking Station. After the reboot and with the Second Display connected the BSOD does not appear.

I have the suspicion that either after installing the latest BIOS update or after a Windows Update this phenomenon started to happen, but I cannot remember the exact circumstances.

After many hours reading the blogs, forums, wikis and sites, uninstalling and reinstalling drivers and programs, I could not find any concrete solution.

The only solution to make it stop the BSOD was (!!!)

  1. to disable these three options in the Dell’s BIOS Performance section:
  • Intel SpeedStep Technology
  • C-States
  • Intel TurboBoost

Turning any single one on again or any other combination of two of them or all three, the BSOD reappears after a while.

  2. Only connect a second display bon the VGA port, not the DVI or the HDMI

Could anyone comment or help?

Thanks in advance

807 Posts

August 16th, 2013 15:00

Hi,

Hope you had a great holiday.

Yes I think we can definitely rule out hardware.

Have a look at these two articles. Seems to be a problem with the Cisco VPN client.

answers.microsoft.com/.../bb62bfb7-f404-444d-829b-a2d2ff0ca981

www.citrix.com/.../dne.html

August 27th, 2013 03:00

Well the news are good.

10 days and NO BSOD so far.

I do not know what solved it, maybe one thing maybe all of them, but the following surely helped

  • Installed MS KB2764302 and KB2661796
  • Un-installed Overlook Fing and WinPcap
  • Upgraded DNE to latest version from http://www.citrix.com/go/lp/dne.html
  • Un-installed and Installed Cisco VPN Client latest version.

Thank you very much for all your help over the last couple of weeks.

I hope this will help others too.

807 Posts

July 17th, 2013 04:00

Googling your Stop error suggests video driver problems. In your troubleshooting process did you update your video drivers to the latest releases?

1.3K Posts

July 17th, 2013 04:00

Hi Athanassios,

Welcome to Dell Community Forum.

We understand you have already tried several troubleshooting steps in order to resolve the BSOD issue however, request you to try the steps mentioned below. Sometimes, if the BIOS is not updated correctly, you may face problems like the one you are facing currently.

The latest BIOS version A18 (released 16th July, 2013) is currently available on the Dell Support Website.  Please try updating the same and check if you are still facing issues with your system. Click on the link below for downloading chipset and video drivers alongwith the BIOS.

Plug your computer to a good, working UPS before you update the BIOS. If you experience a loss of AC power or a significant voltage sag/spike during the BIOS flash, you will either have to replace the BIOS chip or motherboard. Disconnect all external devices and confirm there is no cd/dvd in the optical drive prior to updating the BIOS.

BIOS and Drivers for  Latitude E6520:    http://dell.to/1bIa3zs

Also check this Microsoft link which you may find helpful :

How to troubleshoot a "Stop error code 0x0000001E (KMODE_EXCEPTION_NOT_HANDLED)" error message:  http://bit.ly/15AFIga

Let us know if  you require further assistance. We would be happy to help.

Thanks and regards,
Babita S
#iworkforDell 

For easy access to drivers, manuals and product updates, please visit our Support Site .

July 18th, 2013 01:00

Hello Babita, nice to meet you.

Thank you for you immediate reply. I will download the latest BIOS update ASAP and implement it as per your instructions. Funny though it came out a day before I wrote this message.

I have analyzed also the Microsoft technet link many times , but again no concreete conclusion came out of it.

I will come back with more news.

Thank you in advance

Thanos K

July 18th, 2013 01:00

Hello Paul,

yes I did, I have the latest AND the previous version of the video driver from DELL, but I also downloaded the latest and the previous drivers from Nvidia as well. With all four still some BSOD occoured.

Cheers

807 Posts

July 18th, 2013 07:00

Rootmdm.sys is a modem driver supplied by Microsoft

ntoskrnl.exe is something to do with a corrupted Boot.ini

I would suggest repairing your installation of Windows

July 18th, 2013 07:00

Some feedback after the BIOS patch A18

I did the patch this morning, and all went well. I went into the BIOS and set everything back to the default values, thus enabling also Intel SpeedStep, C States and Intel TurboBoost.

For almost 6 hours I was working without problems, having multiple programs and screens open, and being plugged into the docking station having also the second screen via DVI fully in use.

Then a BSOD when I moved Chrome to the second display: DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 RootMdm.sys+f39c7004

I made sure that verifier was disabled (verifier.exe /reset)

Then an hour later, when I was working via TeamViewer on a customer’s computer: UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f ntoskrnl.exe+75c00

I will disable again my three performance options also Intel SpeedStep, C States and Intel TurboBoost and report back again.

May the Bug be with you… and not me!

1.3K Posts

July 19th, 2013 08:00

Hi Thanos K,

I am glad to meet you too.

Thank you for your reply and details provided. As per the errors you are receiving, the issue could be due to faulty hardware or software (hardware failure is the most common cause).

The most common causes of a STOP 0x7F are:

  • Corrupt memory (RAM)
  • Mismatched memory modules
  • A malfunctioning motherboard

Click on the link below to run the Dell PC Diagnostics to help diagnose and resolve the problems you are having with your system.

http://dell.to/13X4Rq2

Please keep us posted on the results.

Thanks and regards,
Babita S
#iworkforDell 

For easy access to drivers, manuals and product updates, please visit our Support Site .

1.3K Posts

July 23rd, 2013 08:00

Hi Thanos K,

We hope the issue with your computer is resolved.

Unfortunately we have not received feedback from you on this topic. If you need continued support, please respond to my post.

Thanks and regards,
Babita S
#iworkforDell 

For easy access to drivers, manuals and product updates, please visit our Support Site

July 24th, 2013 03:00

Thank you Paul for your feedback, but I knew what these files are.

Unfortunately there are not the same with every Blue Screen Error, so I will ignore them at this point.

Repair Install is always a solution, but I would like to find the source of the problem before I do such a drastic "cover-up".

807 Posts

July 24th, 2013 04:00

For the 1st one see this

ask.wireshark.org/.../npf-driver-problem-in-windows-7

The 3rd one refers to Server Network Driver

The 4th one could be something to do with your Graphics hardware.

The 5th one refers to the parallel printing port.

The others we've already discussed.

If an extended memory test doesn't reveal any errors then I'd say your HDD was failing. Boot to F12 and perform full and extended diagnostic.

If you can get to a command prompt then try SFC or ChkDsk

www.sevenforums.com/.../1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html

In the absence of any HDD / memory failure messages and if SFC or ChkDsk didn't help then advise fresh install of OS.

This is a good tool for checking BSOD's

http://www.resplendence.com/download/whocrashedSetup.exe

or this

http://www.nirsoft.net/utils/blue_screen_view.html

July 24th, 2013 04:00

Sorry, if my previous table is cut down by the blog's width, here is the raw information

Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address Crash Address

072313-37487-01.dmp 23/07/2013 13:25 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00000091 00000000`00000002 fffff800`03e64cc0 00000000`00000000 npf.sys npf.sys+499b000 ntoskrnl.exe+75c00

072013-26988-01.dmp 20/07/2013 12:16 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`000000f6 00000000`000001ec fffffa80`13dd9b30 fffff880`045d1f50 ntoskrnl.exe ntoskrnl.exe+75c00 ntoskrnl.exe+75c00

072013-23805-01.dmp 20/07/2013 11:39 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00000091 00000000`00000002 fffff800`03e1ccc0 00000000`00000000 srvnet.sys srvnet.sys+55a1002 ntoskrnl.exe+75c00

071813-25584-01.dmp 18/07/2013 15:55 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`000000f6 00000000`000001ec fffffa80`12665870 fffff880`06433f50 watchdog.sys watchdog.sys+37f0f50 ntoskrnl.exe+75c00

071813-42869-01.dmp 18/07/2013 15:53 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`000000f6 00000000`000001ec fffffa80`119b1620 fffff880`049adf50 parport.sys parport.sys+fd6d59e0 ntoskrnl.exe+75c00

071813-26754-01.dmp 18/07/2013 15:43 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00000091 00000000`00000002 fffff800`03e60cc0 00000000`00000000 RootMdm.sys RootMdm.sys+f39c7004 ntoskrnl.exe+75c00

July 24th, 2013 04:00

Dear Babita S,

Sorry for the delay but I am trying various scenarios in between work.

For a start let me answer about the faulty HW:

- Corrupt memory (RAM) + Mismatched memory modules

I replaced them twice with two same, new and DELL recommended memory modules, which also succeeded both the Dell PC Diagnostics and the BIOS-boot System Diagnostics Tests

- A malfunctioning motherboard

My suspicion is there also, apart from the obvious faulty and so far unknown software "driver", but how can I make a case to replace it with Dell Support, if the only symptom is a DRIVER_VERIFIER_DETECTED_VIOLATION.

Dell PC Diagnostics

In general all the Dell PC Diagnostics you suggested to me runs came back successfully with no errors or other messages. I did the run many times, with various alternatives, eg. with and without the DVD drive, docked and un-docked, with and without the 2nd monitor, and every time all was well.

I even turned on the verifier.exe once in order to try and do a check (MS KB244617), but I could not even get into Win7, the BSOD was even before the logo screen (July 18th...)

Here is a list of all BSOD which have occurred since I posted this message:

Created by using BlueScreenView

Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size
072313-37487-01.dmp 23/07/2013 13:25:26 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00000091 00000000`00000002 fffff800`03e64cc0 00000000`00000000 npf.sys npf.sys+499b000         x64 ntoskrnl.exe+75c00         C:\Windows\Minidump\072313-37487-01.dmp 8 15 7601 338.898
072013-26988-01.dmp 20/07/2013 12:16:27 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`000000f6 00000000`000001ec fffffa80`13dd9b30 fffff880`045d1f50 ntoskrnl.exe ntoskrnl.exe+75c00 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533) x64 ntoskrnl.exe+75c00         C:\Windows\Minidump\072013-26988-01.dmp 8 15 7601 338.730
072013-23805-01.dmp 20/07/2013 11:39:10 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00000091 00000000`00000002 fffff800`03e1ccc0 00000000`00000000 srvnet.sys srvnet.sys+55a1002         x64 ntoskrnl.exe+75c00         C:\Windows\Minidump\072013-23805-01.dmp 8 15 7601 339.048
071813-25584-01.dmp 18/07/2013 15:55:05 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`000000f6 00000000`000001ec fffffa80`12665870 fffff880`06433f50 watchdog.sys watchdog.sys+37f0f50         x64 ntoskrnl.exe+75c00         C:\Windows\Minidump\071813-25584-01.dmp 8 15 7601 338.790
071813-42869-01.dmp 18/07/2013 15:53:11 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`000000f6 00000000`000001ec fffffa80`119b1620 fffff880`049adf50 parport.sys parport.sys+fd6d59e0         x64 ntoskrnl.exe+75c00         C:\Windows\Minidump\071813-42869-01.dmp 8 15 7601 338.790
071813-26754-01.dmp 18/07/2013 15:43:11 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00000091 00000000`00000002 fffff800`03e60cc0 00000000`00000000 RootMdm.sys RootMdm.sys+f39c7004         x64 ntoskrnl.exe+75c00         C:\Windows\Minidump\071813-26754-01.dmp 8 15 7601 338.764

Thank you in advance for your time:

July 24th, 2013 08:00

Hey Paul,

I also checked the HDD, via various standard (SFC or ChkDsk) and 3rd party tools many times and NOTHING.

A fresh install of OS is a bit drastic and a too easy solution suggestion, since this a work related PC for over a year now but the problems only started 3-4 months ago. A fresh install of OS will take too much time for now.

Also, is it just my idea or is it not strange that all the BSOD's are not the same, but point to different drivers ... ?? I could understand the same BSOD all the time, but 6 BSOD and 6 different drivers? Too strange to be just coincidence,

I will boot to F12 and perform full and extended diagnostic and come back to you.

Thank you again

No Events found!

Top