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

Welcome

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

Problematic software:

Code:

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.

Code:

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION   
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
 nvlddmkm+0xd9ad1
.................................
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.

Code:

STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION 
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.

• RAM - Test with Memtest86+
• Guide to using Memtest86+ - Geeks to Go Forums

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.

Code:

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL   
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 )
-------------------
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA   
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

Thanks for letting us know.