Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD Caused By Driver ntoskrnl.exe (+7f1c0)

20 Oct 2012   #1
that ninja

Windows 7 Ultimate
BSOD Caused By Driver ntoskrnl.exe (+7f1c0)

I'm decent with computers, but I've definitely managed to end up a bit over my head with this one. I've got 4 different BSODs due to this one file now, all at seemingly random times. One while running Guild Wars 2, several while trying to run HULU via Chrome, and one while moving Chrome from one screen to the other. I even managed to get one in Safe Mode and one while trying to load into Safe Mode. Even got one while checking the C Drive for errors. I have never in my life seen a BSOD outside of Windows, so I know something is definitely wrong. I figured I'd come in here and ask what you guys think instead of tinkering around with stuff and possibly making it worse.

My System SpecsSystem Spec
20 Oct 2012   #2

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit


What antivirus are you using? I cannot see any listed.

Problematic software:
Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public
Please uninstall Daemon Tools, it's known to cause BSODs. Search our forum for evidence.

Usual causes:  System service, Device driver, graphics driver, ?memory
BugCheck 3B, {c000001d, fffffa8010e0d060, fffff880045c2ad0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
fffff880`045c25a0  fffff880`0f507ad1Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f42e000 fffff880`101f0000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue May 15 13:35:36 2012 (4FB20748)
    CheckSum:         00DA5E91
    ImageSize:        00DC2000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Please update your graphic card drivers to their latest.
Click on the Start ► Control Panel ► Programs ► Uninstall a program ► Uninstall the NVIDIA related stuff and use Driver Sweeper to remove any remaining drivers of NVIDIA. Get the latest version installed from the manufacturers website.

4 of your dumps indicate problems with memory.
Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
BugCheck 109, {a3a039d89e8db8ba, b3b7465ef10a8810, fffff80003930d10, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

Follow this strategy:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
BugCheck A, {3e4, 2, 0, fffff800035b47fc}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!PipSetDevNodeState+cc )
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
BugCheck 50, {fffff88008fc27b0, 1, fffff80003780c10, 2}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!GetDpiSetting+f6 )
Keep us posted
My System SpecsSystem Spec
23 Oct 2012   #3
that ninja

Windows 7 Ultimate

I had figured it was the RAM, but I wanted a second opinion. Things are fine now, so this can be considered solved.
My System SpecsSystem Spec

24 Oct 2012   #4

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

Thanks for letting us know.
My System SpecsSystem Spec

 BSOD Caused By Driver ntoskrnl.exe (+7f1c0)

Thread Tools

Similar help and support threads
Thread Forum
BSOD playing COD MW3 error caused by ntoskrnl.exe+7f1c0
Keep getting these BSOD when playing COD MW3. Have run memtest86+4.2 and tests passed. Here is my SF Diagnostics report. Would appreciate your help solving this problem
BSOD Help and Support
BSOD ntoskrnl.exe+7f1c0 after NVIDIA Driver update
Hi there, I recently updated my NVIDIA Drivers for my GTX 570 from 296.10 to 306.23 and immediately received a BSOD when trying to start up Skyrim. Since I did a clean install I had no drivers to rollback to so I decided to install the 301.42 drivers which worked fairly well... for about an...
BSOD Help and Support
BSOD ntoskrnl.exe+7f1c0 Vista Driver
I built a new PC back in June and have been receiving numerous BSOD's and have just been working through it until now, can you help me with it? I have attached the dump files as outlined in the SF Diagnostic Tool. I have the following: asrock z77 extreme6 board Curcial M4 SSD Kingston 8GB...
BSOD Help and Support
BSOD : Caused by address : ntoskrnl.exe+7f1c0
I have had a new system built, Had it for almost 2 weeks and been getting the BSOD at least 2x a day. Ihave been browsing the web and had it happen, been playing online games and have it happen. Have even come home after work to find that the computer crashed and had to be restarted because of...
BSOD Help and Support
new laptop, BSOD caused by ntoskrnl.exe+7f1c0?
Hello, i recently got a new HP Pavillion dv6-6c50us about a week ago. Intel Core i5-2450M 6GB DDR3 RAM (1 x 2GB, 1 x 4GB) 750GB 5400RPM Hard Drive - x86 (32-bit) or x64 ? - Windows Home Premium 64bit - the original installed OS on the system? - Yes
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 21:11.
Twitter Facebook