BlueScreen STOP: 0x0000001E
Hello,
My system recently got a BSOD, the error code was STOP 0x0000001E
With BlueScreen view I get these information:
Bug Check String:
KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code:
0x0000001e
Parameter 1: 00000000`00000000
Parameter 2: 00000000`00000000
Parameter 3: 00000000`00000000
Parameter 4: 00000000`00000000
Caused by driver: ndis.sys
Caused by address: ndis.sys+2624
Processor: x64
Crass address: ntoskrnl.exe+7cc10
Processor count: 8
Major version:
15
Minor version: 7601
Dump file size: 324,704
System Specs:
Motherboard: Asus Rampage III Extreme Edition
CPU: i7 - 950 @ 3.2GHz
RAM: 6GB (3x2GB) @ 1866 Mhz
GPU: nVidia GTX 280
System disk: SSD OCZ Agility connected at a Sata III port
OS: Windows 7 Ultimate x64
What caused the BSOD?
How can I fix the problem?
Thank you for your time!
September 12th, 2011 11:56pm
First, it is strange that the first and the second parameters are 0. For example, the first should contain a Windows error code whereas 0 means "no error", which is quite unexpected. Are you sure that there was really a zero?
ndis is a Microsoft driver which is used by most vendor-specific network adapters drivers.
So you might start with checking for Windows Updates and for the new version of your network adapter driver.
Free Windows Admin Tool Kit Click here and download it now
September 13th, 2011 12:24am
You may boot in Clean Boot Mode.
Perform a clean startup to determine whether background programs are interfering with your game or program
If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files,
rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver
is the root cause.
Another way is enable muni-dump and use Windbg. Please refer:
How to read the small memory dump files that Windows creates for debuggingPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
September 15th, 2011 9:37am