Several BSOD's, most linking back to ntoskrnl.exe

Hi Optics,

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error. enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
______________________________________________________________________________________

Code:

BugCheck A, {fffff680003cf2b0, 0, 0, fffff8000319f396}

Probably caused by : memory_corruption ( nt!MiGetWorkingSetInfo+286 )

Followup: MachineOwner
-------------------------------------------------------------------------------------------
BugCheck 4E, {99, 1b46ea, 0, a7c6a}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
-------------------------------------------------------------------------------------------
BugCheck 1A, {41201, fffff683ff76d5e8, a0900001e0988025, fffffa8006ef0700}

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

Followup: MachineOwner
---------

I've been running memtest all day, just got home and it's 7 pass 0 errors so far. I guess I'll have start that driver verifier next. Thanks for the tips. Does it look like only a memory or driver issue that's causing these?


Edit-Including a SS of my memtest, let me know if anything is out of place.





Edit #2

Ran Driver Verifier, immediately on rebot it BS'd, apparantly my Razer Lycosa keyboard driver was bad. Disabled verifier, updated, ran again. This time I made it past reboot, running in background now and will see if any further crashes happen in the next 24 hours.

Thanks again, and seems unlikely but hopefully all these BSOD's were from the keyboard driver, if not I guess we'll see what else causes a crash.

Yes, the latest BSOD is not very specific, but it also says that the Razer driver is out of date, and old Razer drivers are supposed to cause BSODs.

Try to update it: Razer Support
Razer Support

Then disable driver verifier and let us know how the computer is running.
___________________________________________________________________________________________________

Code:

fffff880`066c6000 fffff880`066cd100   Lycosa     (deferred)             
    Image path: \SystemRoot\system32\drivers\Lycosa.sys
    Image name: Lycosa.sys
    Timestamp:        Wed Sep 08 08:31:26 2010 (4C86FC86)
    CheckSum:         0001462D
    ImageSize:        00007100
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Now run the computer without Driver Verifier enabled :)