BSOD while playing, ntoskrnl.exe

[catch22]

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..

 

[x BlueRobot]

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:

Start Menu\Programs\DAEMON Tools Lite

 

[catch22]

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

 

[catch22]

Any alternatives to Daemon Tools?

 

[x BlueRobot]

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:

• http://www.sevenforums.com/tutorials/548-burn-disc-image-iso-img-file.html

The related tutorials section contains a few other features too.

 

[catch22]

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. .

 

[x BlueRobot]

[COLOR="Red"]BugCheck 1A[/COLOR], {41201, fffff680000b5088, f68000004acf8367, fffffa8012a2ea40}

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

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:

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

:info: Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[catch22]

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

 

[catch22]

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

 

[x BlueRobot]

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

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:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Post back your results

 

[catch22]

Recreated the bluescreen and booted into safemode to avoid bootlooping, minidump folder is empty. It doesnt seem to save a dump. Is there a setting to enable it?

 

[x BlueRobot]

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

[catch22]

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Blue you gotta help me, It seems it doesn't help. I have tried both MInidump and complete memory dump and none of them are stored. It crashes on startup still.. Is there a way to save the log from the crash? :s Should i upload a video?

EDIT; heres a video of it happening

http://dl.dropbox.com/u/61768451/20121229_142627.mp4

 

[x BlueRobot]

Scan for any malware or rootkits using:

• http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html
• Anti-rootkit utility TDSSKiller

Make sure you have a paging file set also:

• Virtual Memory Paging File - Change - Vista Forums

 

[catch22]

I freezeframed the movie , found out what the culprit was

 

[x BlueRobot]

Which was?

 

[catch22]

Well, first of all, sorry for resurrecting this thread but I thought it would be better than to start a new one.


Okay, so, formatted my C-drive clean, did a fresh install of windows, no errors this time. I have gotten 3 bluescreens since friday, e.g. 3 days ago, once a day so to speak. I hope anyone can take a look at them - I can't make out what they mean. One points to watchdog,which seems to be a windows file. The others point to nvlddkm,sys or ntoskrnl.sys which are proprietary of Nvidia , ie my graphics card, and Windows NT Kernel..

Hard stuff.. Might there be any errors with the graphics card? Its age is about 8 -10 months..

 

[x BlueRobot]

[COLOR="Red"]BugCheck 10E[/COLOR], {1f, fffff8a014cebe50, 6, 4a3d9}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+ce )

Usual causes:  Video driver, Video memory

1. Download Driver
2. Start rb: Type: Device Manager
3. Expand Display Adapters
4. Right-Click Driver Name, Uninstall
5. Reboot
6. Run Driver Sweeper
7. Reboot
8. Install Downloaded Driver

Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

Driver Sweeper:

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

The latest nVidia driver is dated as January 29th 2013.

• http://www.sevenforums.com/graphic-cards/602-latest-nvidia-forceware-video-drivers-windows-7-a.html

 

[catch22]

Done! Latest drivers were from Jan 5th though, unless you're talking about beta drivers. Let's see if problem persists ..

 

[x BlueRobot]

I meant the Beta drivers, but if you have installed the latest WHQL certified driver, then that may be the better option since it has been tested by Windows.