BSoD - 1e

Hello there.

I got a BSoD a few weeks ago, but chose to ignore it to see if more would pop up. Today, for some reason, I get BSoDs near instantly when I don't run in safe mode with the BCCode 1e.
Here's the windows info it gives me on startup after a BSoD, if that helps:

BCCode: 1e
BCP2: FFFFF80002CC722E
BCP3: 0000000000000000
BCP4: FFFFFA80047B0000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

I've attached a couple of minidumps, my dxdiag and a System health Report.
My Anti-Virus program (AVG) didn't catch anything and my system is running fine in safe mode.

If you need more info from me, just tell (but please include instructions if it gets complicated).

Hope you guys can help me out :)




Noob Whisperer
Update the driver for your Nvidia video card nvlddmkm.sys 8/19/2009 from here Drivers - GeForce
BugCheck D1, {58, 2, 0, fffff88007d472bf}
Unable to load image \SystemRoot\system32\DRIVERS\[COLOR=#ff0000][U][B]nvlddmkm.sys[/B][/U][/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]nvlddmkm.sys[/B][/U][/COLOR]
fffff880`02f227f8 fffff800`02c8b2e9 : 00000000`0000000a 00000000`00000058 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f22800 fffff800`02c89f60 : 00000000`00000002 00000000`00000000 00000000`00200246 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f22940 fffff880`07d472bf : fffffa80`069d11f0 fffff880`07569a15 fffffa80`04f26010 fffff880`073bc798 : nt!KiPageFault+0x260
fffff880`02f22ad0 fffff880`07d4737a : fffffa80`069d11f0 fffffa80`06fa3060 fffffa80`069d11f0 fffff880`073be39f : dxgmms1!VidSchiCheckConditionDeviceCommand+0x33
fffff880`02f22b00 fffff880`07d421f1 : fffffa80`06bf8010 fffffa80`06c108e0 fffffa80`06fa3000 fffffa80`069d11f0 : dxgmms1!VidSchiCheckPendingDeviceCommand+0x3e
fffff880`02f22b40 fffff880`07d41ce8 : fffffa80`00000000 fffff880`0000002e fffffa80`00000000 00000000`00000000 : dxgmms1!VidSchiProcessDpcVSyncCookie+0x399
fffff880`02f22c00 fffff880`07d41c4c : fffffa80`069d59b0 fffffa80`06bf8010 fffffa80`051f9480 fffffa80`051f9aa8 : dxgmms1!VidSchDdiNotifyDpcWorker+0x80
fffff880`02f22c50 fffff880`066c41cf : fffffa80`051f9480 00000000`00000002 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02f22ca0 fffff880`072a8add : 00000000`00000000 fffffa80`053ff000 fffffa80`051f9480 fffffa80`0526d000 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`02f22cd0 00000000`00000000 : fffffa80`053ff000 fffffa80`051f9480 fffffa80`0526d000 fffffa80`053ff000 : [COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]+0x6fadd
Update both these RealTek drivers
Rt64win7.sys 2/26/2009 Realtek servers seem intermittent so keep trying
RTL8187B.sys 3/24/2009 Realtek same deal servers are up and down
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
fffff880`03376de8 fffff800`02c89bbe : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`02ce870b : nt!KeBugCheck
fffff880`03376df0 fffff800`02cbce4d : fffff800`02e968ec fffff800`02dd8f88 fffff800`02c13000 fffff880`03377d08 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`03376e20 fffff800`02cbbc25 : fffff800`02dd8f80 fffff880`03376e98 fffff880`03377d08 fffff800`02c13000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`03376e50 fffff800`02cccbb1 : fffff880`03377d08 fffff880`03377560 fffff880`00000000 fffff880`093bc530 : nt!RtlDispatchException+0x415
fffff880`03377530 fffff800`02c91842 : fffff880`03377d08 fffff880`093bc530 fffff880`03377db0 fffff880`01869800 : nt!KiDispatchException+0x135
fffff880`03377bd0 fffff800`02c8f99f : fffff880`03377db0 00000000`00000002 fffffa80`05885600 fffff880`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`03377db0 fffffa80`07019b50 : fffff880`01869800 fffffa80`07019b50 fffff800`02c89cb7 fffff880`01869800 : nt!KiInvalidOpcodeFault+0x11f
fffff880`03377f48 fffff880`01869800 : fffffa80`07019b50 fffff800`02c89cb7 fffff880`01869800 00000000`00000000 : 0xfffffa80`07019b50
fffff880`03377f50 fffffa80`07019b50 : fffff800`02c89cb7 fffff880`01869800 00000000`00000000 00000000`00000000 : tcpip!Ipv6Global
fffff880`03377f58 fffff800`02c89cb7 : fffff880`01869800 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`07019b50
fffff880`03377f60 fffff800`02c89c78 : 00000000`00000000 00000000`00000001 fffff880`03378000 fffff800`02c9e032 : nt!KxSwitchKernelStackCallout+0x27
fffff880`093bc530 fffff800`02c9e032 : 00000000`00000000 fffff880`00000019 fffffa80`05888500 00000000`00000000 : nt!KiSwitchKernelStackContinue
fffff880`093bc550 fffff880`01739c7f : fffff880`01786c44 fffffa80`046fb9b0 fffff880`093bc700 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x2a2
fffff880`093bc630 fffff880`01756f29 : fffffa80`06fef190 fffffa80`05711350 fffffa80`046fb9b0 fffffa80`04b74b00 : [COLOR=#ff0000][U][B]tcpip[/B][/U][/COLOR]!IppLoopbackEnqueue+0x22f
fffff880`093bc6e0 fffff880`017585d5 : 00000000`00000000 fffffa80`05880160 fffffa80`04b74bfc 00000000`00000011 : [COLOR=#ff0000][U][B]tcpip[/B][/U][/COLOR]!IppDispatchSendPacketHelper+0x409
fffff880`093bc7a0 fffff880`0175785e : fffffa80`04b74b11 fffff880`093bcc00 00000000`00000028 fffffa80`00000000 : [COLOR=#ff0000][U][B]tcpip[/B][/U][/COLOR]!IppPacketizeDatagrams+0x2d5
fffff880`093bc8c0 fffff880`0175a17e : 00000000`00000000 fffff880`01528f04 00000000`00000011 fffffa80`0588a010 : [COLOR=#ff0000][U][B]tcpip[/B][/U][/COLOR]!IppSendDatagramsCommon+0x87e
fffff880`093bca60 fffff880`01738258 : fffffa80`0588a010 fffffa80`05880030 fffffa80`05880030 fffffa80`05711350 : [COLOR=#ff0000][U][B]tcpip[/B][/U][/COLOR]!IpNlpSendDatagrams+0x3e
fffff880`093bcaa0 fffff880`017384ab : fffffa80`0558f280 fffff880`0182fcc0 fffff880`093bd3f0 00000000`00000000 : [COLOR=#ff0000][U][B]tcpip[/B][/U][/COLOR]!UdpSendMessagesOnPathCreation+0x688
fffff880`093bce20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : [COLOR=#ff0000][U][B]tcpip[/B][/U][/COLOR]!UdpSendMessages+0x1db
Completely remove AVG. Use the programs uninstaller or the programs and features applet in the control panel and follow that up by running this vendor specific proprietary removal tool from here AVG Download tools and utilities Replace it with MSE from here Spyware Protection | Free Spyware Protection | Microsoft Security Essentials
BugCheck 1E, {ffffffffc0000005, fffff88001024ee1, 0, ffffffffffffffff}

Unable to load image \SystemRoot\system32\DRIVERS\   [COLOR=#ff0000][B]avgmfx64.sys[/B][/COLOR]   , Win32 error 0n2
*** WARNING: Unable to verify timestamp for    [COLOR=#ff0000][B]avgmfx64.sys[/B][/COLOR]   
*** ERROR: Module load completed but symbols could not be loaded for    [COLOR=#ff0000][B]avgmfx64.sys[/B][/COLOR]   
Unable to load image \SystemRoot\system32\DRIVERS\   [COLOR=#ff0000][B]AVGIDSFilter.Sys[/B][/COLOR]   , Win32 error 0n2
*** WARNING: Unable to verify timestamp for   [B] [COLOR=#ff0000]AVGIDSFilter.Sys[/COLOR][/B]   
*** ERROR: Module load completed but symbols could not be loaded for    [COLOR=#ff0000][B]AVGIDSFilter.Sys[/B][/COLOR]      
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR=#ff0000][U][B]Probably caused by : avgmfx64.sys ( avgmfx64+1963 )[/B][/U][/COLOR]
fffff880`0dbbcb18 fffff800`02d18db8 : 00000000`0000001e ffffffff`c0000005 fffff880`01024ee1 00000000`00000000 : nt!KeBugCheckEx
fffff880`0dbbcb20 fffff800`02ccd842 : fffff880`0dbbd2f8 fffffa80`04ad1f10 fffff880`0dbbd3a0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x48d3d
fffff880`0dbbd1c0 fffff800`02ccc14a : 00000000`00000000 00000000`00000000 fffff8a0`03d0c76c fffff8a0`03d0c778 : nt!KiExceptionDispatch+0xc2
fffff880`0dbbd3a0 fffff880`01024ee1 : 00000000`00000011 fffff800`02cc2b65 00000000`00000000 fffffa80`04d4e8f8 : nt!KiGeneralProtectionFault+0x10a
fffff880`0dbbd530 fffff880`01024e1e : fffffa80`04ad1f10 fffff880`0101d6c0 00000000`00000000 00000000`000007ff : fltmgr!FltpGetNormalizedFileNameWorker+0x21
fffff880`0dbbd570 fffff880`01010b9d : c00000bb`00000000 00000000`00000000 fffffa80`04ea7b00 fffff880`0dbbf000 : fltmgr!FltpCreateFileNameInformation+0xee
fffff880`0dbbd5d0 fffff880`0100abf6 : fffffa80`046e2080 fffffa80`04ea7010 fffffa80`04d4e8f8 00000000`00000000 : fltmgr!HandleStreamListNotSupported+0x15d
fffff880`0dbbd610 fffff880`01011b44 : 00000000`00008000 00000000`00000000 fffffa80`04ea7010 00000000`00000401 : fltmgr! ?? ::FNODOBFM::`string'+0x30f3
fffff880`0dbbd690 fffff880`01beb963 : fffffa80`04ad1f10 00000000`00000001 fffffa80`06b208f0 00000000`00000001 : fltmgr!FltGetFileNameInformation+0x184
fffff880`0dbbd720 fffffa80`04ad1f10 : 00000000`00000001 fffffa80`06b208f0 00000000`00000001 00000000`00000001 : [COLOR=#ff0000][U][B]avgmfx64[/B][/U][/COLOR]+0x1963
fffff880`0dbbd728 00000000`00000001 : fffffa80`06b208f0 00000000`00000001 00000000`00000001 fffffa80`03c6f910 : 0xfffffa80`04ad1f10
fffff880`0dbbd730 fffffa80`06b208f0 : 00000000`00000001 00000000`00000001 fffffa80`03c6f910 fffff880`0dbbd900 : 0x1
fffff880`0dbbd738 00000000`00000001 : 00000000`00000001 fffffa80`03c6f910 fffff880`0dbbd900 fffffa80`04e36520 : 0xfffffa80`06b208f0
fffff880`0dbbd740 00000000`00000001 : fffffa80`03c6f910 fffff880`0dbbd900 fffffa80`04e36520 fffffa80`070e4070 : 0x1
fffff880`0dbbd748 fffffa80`03c6f910 : fffff880`0dbbd900 fffffa80`04e36520 fffffa80`070e4070 00000000`0000004e : 0x1
fffff880`0dbbd750 fffff880`0dbbd900 : fffffa80`04e36520 fffffa80`070e4070 00000000`0000004e 00000000`1000000c : 0xfffffa80`03c6f910
fffff880`0dbbd758 fffffa80`04e36520 : fffffa80`070e4070 00000000`0000004e 00000000`1000000c fffffa80`06b20840 : 0xfffff880`0dbbd900
fffff880`0dbbd760 fffffa80`070e4070 : 00000000`0000004e 00000000`1000000c fffffa80`06b20840 fffffa80`04e36740 : 0xfffffa80`04e36520
fffff880`0dbbd768 00000000`0000004e : 00000000`1000000c fffffa80`06b20840 fffffa80`04e36740 fffff880`01002067 : 0xfffffa80`070e4070
fffff880`0dbbd770 00000000`1000000c : fffffa80`06b20840 fffffa80`04e36740 fffff880`01002067 00000000`00000000 : 0x4e
fffff880`0dbbd778 fffffa80`06b20840 : fffffa80`04e36740 fffff880`01002067 00000000`00000000 fffff880`0dbbd808 : 0x1000000c
fffff880`0dbbd780 fffffa80`04e36740 : fffff880`01002067 00000000`00000000 fffff880`0dbbd808 fffffa80`06b20990 : 0xfffffa80`06b20840
fffff880`0dbbd788 fffff880`01002067 : 00000000`00000000 fffff880`0dbbd808 fffffa80`06b20990 fffff800`02ce1d59 : 0xfffffa80`04e36740
fffff880`0dbbd790 fffff880`010049aa : fffffa80`070e4000 fffffa80`070e4000 fffffa80`04c3fd00 fffffa80`04d4e800 : fltmgr!FltpPerformPreCallbacks+0x2f7
fffff880`0dbbd890 fffff880`010222a3 : fffffa80`04c13810 fffffa80`04c13810 fffffa80`04c13810 00000000`00000000 : fltmgr!FltpPassThroughInternal+0x4a
fffff880`0dbbd8c0 fffff880`08bf732b : fffffa80`04c13bf8 fffff800`02ce42bf fffffa80`0741a820 00000000`00000000 : fltmgr!FltpCreate+0x293
fffff880`0dbbd970 fffffa80`04c13bf8 : fffff800`02ce42bf fffffa80`0741a820 00000000`00000000 fffffa80`070e4070 : [COLOR=#ff0000][U][B]AVGIDSFilter[/B][/U][/COLOR]+0x332b
fffff880`0dbbd978 fffff800`02ce42bf : fffffa80`0741a820 00000000`00000000 fffffa80`070e4070 fffffa80`04c13810 : 0xfffffa80`04c13bf8
fffff880`0dbbd980 fffff800`02fc7be5 : 00000000`00000005 fffffa80`08164cc8 fffffa80`0417fb10 fffffa80`070e4108 : nt!RtlCopyUnicodeString+0x3f
fffff880`0dbbd9b0 fffff800`02fc4488 : fffffa80`04c2f5c0 fffff800`00000000 fffffa80`08164b10 fffffa80`00000001 : nt!IopParseDevice+0x5a5
fffff880`0dbbdb40 fffff800`02fc56a6 : 00000000`00000000 fffffa80`08164b10 c4600000`364b1867 fffffa80`03d55260 : nt!ObpLookupObjectName+0x588
fffff880`0dbbdc30 fffff800`02fc6fac : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`02fb5c0c : nt!ObOpenObjectByName+0x306
fffff880`0dbbdd00 fffff800`02fb27d4 : fffff880`0dbbe740 00000000`001000a1 fffff880`0dbbe128 fffff880`0dbbe158 : nt!IopCreateFile+0x2bc
fffff880`0dbbdda0 fffff800`02ccd453 : 00000000`00000002 00000000`000000ec 00000000`00000000 fffff880`0c32688f : nt!NtOpenFile+0x58
fffff880`0dbbde30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
Couple other older drivers you should probably attend to
[TABLE="width: 193"]
[TD="align: right"]4/29/2008[/TD]
[TD="align: right"]9/26/2008[/TD]
[TD="align: right"]5/11/2009[/TD]
One looks like an old modem and one of the others looks like a chipset driver for your motherboard. Use Google and see what you can find.

ahh, updating my drivers ... Forgot about that. Had a total reset of my computer a month or 2 ago using an image from when I just got the computer. Completely forgot that my drivers wouldn't be even close to up to date, I feel so dumb right now.

Thanks for a quick response, I'll try updating all my drivers tomorrow and see if it fixes my problems. It's incredible how you can get so much info out of something that looks like gibberish to me - Very impressive, Keep up the good work.


Noob Whisperer
You're welcome. Keep us posted.
And don't forget AVG, it has been a thorn in the side of some BSOD resolutions.
Welcome to the forum.

Deleted AVG with it's uninstall feature.
Updated my GeForce Driver.
Downloaded the recommended Spyware program.

I'm not really sure what to do in the realtek ones. Looks rather complicated to me (Note: I am by no means a computer expert. I sit behind my computer all day using it, but don't really know how it works). Could you maybe give me a short hint in the right direction when it comes to realtek update? :)

Thanks so far, will keep you updated.

I checked up on the 3 other drivers.

First is the build-in camera in the pc (It's a laptop)
Second is a Motorola modem.
And the last one is NVIDIA hdmi audio driver (which maybe belongs to my headset?)

The problem is finding updates for them ^_^

Last edited:


Noob Whisperer
For the Realtek drivers;
The 8187B.sys go here and grab this one UI and Driver auto install package(Support XP/Vista/Win7) 1181 2011/2/8 16809k save it to a new folder on your desktop and extract the zip contents. The file you need will be contained in RTL8187B_Drv_XP_5.1162.0610.2009_Win7_62.1181.1105.2009_UI_1.00.0145.ALL.L\RTL8187B\Win764 (assuming you have 64 bit windows installed which I believe is the case otherwise it'll be in the Win7X86 folder) called net8187b.inf
Use the technique described below to manually update the driver.
For the Rt64win7.sys go here Realtek and grab this one Win7 and WinServer 2008 R2 Driver 7.053 2012/3/22 740k save and extract it to a new folder. The driver you need will be located here Driver_Win7_7053_03162012\WIN7\64 and called rt64win7.inf (same deal as above).
Driver Install - Manual Method

  1. Download the driver and extract it to a folder.
  2. Open the Device Manager.
  3. Right click the device you wish to change the drivers for. You can select Properties > Driver > Driver Details to check you have the right device.
  4. Choose Update Driver Software.
  5. Select Browse My Computer For Driver Software.
  6. Select Let me pick from a list of device drivers on my computer.
  7. Select Have disk...
  8. Select Browse..
  9. Navigate to the extracted folder and double click on the .inf file
  10. Hit OK, then Next and the driver(s) will then begin to install.
  11. After it has installed, GoTo C:\Windows\System32\Drivers. Locate the driver you've just updated, right click it and check the dates under its properties.

Last edited:
Here is 4 more minidump from today - I'll try to update my realtek driver now.

Edit: Updated my realtek drivers. Haven't had BSoD since, only time will show.

Also, I looked inside the device manager and looked for the ones you had listed:

"Couple other older drivers you should probably attend to
[TABLE="class: cms_table, width: 193"]
[TD="align: right"]4/29/2008[/TD]
[TD="align: right"]9/26/2008[/TD]
[TD="align: right"]5/11/2009"[/TD]

This is what I found:
BisonC07.sys is 'BisonCam, NB Pro' (Aka. The webcam in my laptop)
SmSerl64.sys is is 'Motorola SM56 Data Fax Modem'
nvhda64v.sys is 'NVIDIA High Definition Audio'

Do I need to look for updates for the drivers, because I'm having a tough time finding them.


Last edited:


Noob Whisperer
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area .
Good luck

I've attached my Seven Forums folder which also includes my Rammon Report. I've also uploaded a zip with all the CPUz tabs (except the "About" tab) and more minidumps.

Hamachi.sys has been removed - Also trying to removed SmSerl64.sys, but it keeps coming back. I've also uninstalled Daemon tools.


Last edited:


Noob Whisperer
Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+

I've been busy with exams and stuff, but my dad already had an CD with an older version of Memtest and we found no problems. I also cleaned my cooling system. The weird thing is I haven't had ANY problems after I ran the test, and that's now over 2 weeks ago. I'll report back if I get future problems :)


Windows Forum Admin
Staff member
Premium Supporter
It could have been a legitimate cooling problem if the card was aired out. It is sort of an unspoken rule that numerous people are always appreciative when you reply giving a response as to what happened. This can help an enormous number of people having a very similar incident. Hope that you consider joining us at :)

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.