W7 BSOD 0x000001e

[bokasi]

Hi
I have just build this system and keep experiencing the BSOD 0x000001e error, could someone help me with this? I have attached the dump files

 

[Lomai]

Hi bokasi

Welcome to Seven Forums
While waiting for the SF BSOD Squad to have a look at your dump, check out this thread:

0x0000001e BSOD New build

Be sure to try out some of the recommended actions mentioned on that thread

Keep us posted on your progress and regards

 

[Jonathan_King]

Welcome!

First, try updating your Intel storage drivers.

HECIx64.sys  Thu Sep 17 15:54:16 2009
iaStor.sys   Fri Oct 02 15:58:50 2009

If that doesn't work, enable driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Wait for a few crashes, and then post back using these directions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 10:14:43.509 2010 (UTC - 4:00)
System Uptime: 0 days 2:51:25.696
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 05:21:58.164 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:48.741
BugCheck 3B, {c0000005, fffff800031d371f, fffff88008496fc0, 0}
Probably caused by : ntkrnlmp.exe ( nt!AlpcpLookupMessage+bf )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  mscorsvw.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/font]

 

[bokasi]

i've just installed newer drivers for Intel® Rapid Storage Technology but am finding difficulty in getting the hecix64.sys driver. could you please point me into the right direction?

 

[Jonathan_King]

Sure, just upload your msinfo file.

Enter msinfo32.exe into the start menu, and press enter. Go to File>Save, and save a copy on your desktop. Right-click on it, and select Send to>New compressed folder. Then attach the file to your next post.

 

[bokasi]

Here's the file

 

[Jonathan_King]

I believe your best bet is to uninstall the Intel Management Engine Interface. It should be found in Programs and Features.

 

[bokasi]

I have uninstall Intel Managemtn Interface, however before that i got another BSOD not sure if it is related, but here is the dump
Thank you

 

[Jonathan_King]

Honestly not much info useful to be in that dump. I think our best bet is just to wait at this point.

If you get any more BSODs, please follow the BSOD Posting Instructions sticky.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 23:53:54.783 2010 (UTC - 4:00)
System Uptime: 0 days 2:41:47.359
BugCheck 3B, {c0000005, fffff8000318748e, fffff8800a9dc170, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+3e )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wmplayer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[bokasi]

it isnt happening as often anymore but still does.. came out with the same 0x000001e error again

i've attached the dump below

 

[Jonathan_King]

A consistent bugcheck indicates predictability, which bad hardware typically does not afford. In other words, I suspect a driver issue.

Please enable driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

If Verifier doesn't flag anything, we'll start on hardware.

When you get more BSODs, please use these directions to post it: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html


...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep  9 16:30:03.807 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:08.384
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[bokasi]

ok i had a few bsod's before doing the driver verifier bit. after enabling the driver verfier, it had another crash... bdfm.sys was mentioned but a report was never generated when it crashed.

 

[Jonathan_King]

That is Bit Defender. Please remove it with this tool: http://www.bitdefender.com/uninstall

Replace it with MSE: http://www.microsoft.com/security_essentials

Be sure Verifier is disabled.

 

[bokasi]

ok i didnt have much bsod after installing MSEE but today got a number of blue screens again.

not sure if it is the software i installed which is causing it as its been happening randomly again..

attached the dump again ..

 

[bokasi]

i did the driver verifier once more and it crashed on the first boot up and fine on the 2nd.. how do you find out the results of what's been done by driver verifier as i cant find the log of the bsod during that crash in the event viewer

 

[Jonathan_King]

I wonder if your Atheros network adapter drivers are the cause. See if you can find some updated drivers for it, on your computer manufacturer's site or another source.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 22:54:30.288 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:37.864
BugCheck C4, {91, 2, fffff800031fac40, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4904 )
BUGCHECK_STR:  0xc4_91
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 22:38:16.524 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:29.101
BugCheck 24, {1904fb, fffff88008ab96e8, fffff88008ab8f50, fffff880014c974c}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+111c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 22:28:44.584 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:04.160
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcVSyncCookie+464 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 22:21:36.860 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:08.047
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ndis.sys ( ndis!ndisMTimerObjectDpc+18 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 20:43:21.263 2010 (UTC - 4:00)
System Uptime: 0 days 4:16:24.465
BugCheck 3B, {c0000005, fffff80003083905, fffff88008f11940, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 16:25:53.073 2010 (UTC - 4:00)
System Uptime: 0 days 19:12:00.650
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

athrx.sys    Fri Nov 06 15:56:02 2009 (4AF48D62)

 

[bokasi]

just bought a new wlan card.

was fine for a day but then this error popped up again. the bsod rate has gone down though

here's the dump for it

 

[Jonathan_King]

Might want to install these network drivers: Realtek

Update your Logitech QuickCam drivers for the heck of it:

lvuvc64.sys  Wed Oct 07 04:28:44 2009

If the BSODs persist, start out by doing a RAM test: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Enable driver verifier, wait for a few BSODs, and then follow these directions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

...Summary of the Dumps:

[FONT=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 17 15:56:55.614 2010 (UTC - 4:00)
System Uptime: 0 days 14:03:38.190
BugCheck 1E, {ffffffffc0000005, fffff88008a377e0, 0, 0}
Probably caused by : tcpip.sys ( tcpip!WfpAleFastUdpInspection+27e )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/FONT]

 

[bokasi]

ok.. just replaced the power supply as that was faulty but still got a blue screen

did a mem test too and it passed

enabled driver verifier and found that nvbridge.kmd is not loaded.

could it be possibly that?

attached the dump file too..

 

[Jonathan_King]

Hmm...driver verifier is not enabled in that dump. In fact, looking back, I notice that verifier wasn't enabled for any.

Please follow these directions: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Reboot, then open a command prompt and enter the following:

verifier /query>%userprofile%\desktop\verifier.txt

Could you please attach the new verifier.txt file to your next post?