BSOD while playing, ntoskrnl.exe

SFC came up with no intergrity violations, chkdisk is scheduled, will reseat card now then apply chkdisk of C:\ on startup. other disks were fine with chkdisk. I currently have a pagefile on my other SSD (not the boot one) since warnings came up..

There's no problems with your operating system which is good, however, Daemon Tools Lite is still on your system and drivers for this program are known to cause problems such as BSODs.

Uninstall Daemon Tools Lite:

Code:

Start Menu\Programs\DAEMON Tools Lite

DAEMON Tools uninstalled
All cards and cables have been reseated,
Removed CPU fan and removed excess cooling paste,
ChkDsk has been run on all disks and they're fine according to results.,

Im thinking it might be the motherboard..

Will repost as soon as new bluescreen occurs

Any alternatives to Daemon Tools?

Windows already provides most of the features in which Daemon Tools gave, such as the ablity to make bootable .ISO files and burn files to CDs/DVDs:

• Burn Disc Image - ISO or IMG file

The related tutorials section contains a few other features too.

Oh no. It seems I wasn't in the clear. Just got a new bluescreen relating to ntoskrnl.sys and fltmgr.sys. File uploaded. While playing BF3. It seems that it only happens in BF3 nowadays. Have been using other games for a while and bf3 too to some extent without any problems. .

Code:

BugCheck 1A, {41201, fffff680000b5088, f68000004acf8367, fffffa8012a2ea40}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+136f2 )

Code:

Usual causes:  Device driver, memory, kernel

Delete/Recreate the Pagefile
Vista:

1. Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
2. Click on the Advanced tab
3. Click on the Performance Settings button
4. Click on the Advanced tab
5. Click on the Virtual Memory Change button
6. Uncheck the "Automatically manage paging file size for all drives" box (it's the default)
7. If the above box isn't checked, then make a note of what the paging file settings are
8. Click on the "No paging file" radio button, then click on "Set"
9. Answer Yes to the confirmation dialog that pops up.
10. Click on OK 3 times (to close all the Windows)
11. Reboot the system (this will delete the paging file)
12. Once Windows starts, go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
13. Click on the Advanced tab
14. Click on the Performance Settings button
15. Click on the Advanced tab
16. Click on the Virtual Memory Change button
17. Place a checkmark in the "Automatically manage paging file size for all drives" box (it's the default)
18. If the above box wasn't checked at first, then re-enter the paging file settings that you noted in Step 7
19. Click on "Set" (it'll be greyed out if you checked the box 2 steps earlier
20. Click on OK 3 times (to close all the Windows)
21. Reboot the system (this will recreate the paging file)

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

Additional Help - Using Driver Verifier to identify issues with Drivers

Thanks for reply BlueRobot, as always you are so supportive!

Uhm, enabling verifier this time around made my Windows unable to boot , and at the startup screen where the Windows-logo forms, it stuck for half a second, then threw a bluescreen and restarted. happened so fast i couldnt see what was on it.. Is there any way to "catch" that bluescreen? I had to system restore to be able to start the computer again, so pagefile is reset I suppose. Will try again

Reset pagefile, and redid driver verifier. Still crashes on startup, got me to thinking there might be errors in windows files?

Disable Driver Verifier and then boot into Windows normally, check this folder:

Code:

C:\Windows\Minidump

You may change C:\ to any partition which you have Windows installed upon, seems there may be some driver issues if a BSOD keeps occurring with Driver Verifier enabled. You can type the above folder path into the Search box within the Start Menu, and it should take you to the folder automatically after pressing Enter.

If you wish, you can check for any missing or corrupted protected Windows files with:

• SFC /SCANNOW Command - System File Checker

Post back your results :)