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: Several BSOD's, most linking back to ntoskrnl.exe

09 Jan 2014   #1
Optics

Win 7 Ultimate x64
 
 
Several BSOD's, most linking back to ntoskrnl.exe

The past week i've been getting random blue screens, almost always with different errors. After checking with the bluescreeview program it appears most are tied to ntoskrnl.exe. They're all seemingly random, either while idle or in the middle of forum browsing or gaming. Any help would be greatly appreciated. I'm not sure where to even begin fixing the kernel and would really love to not have to do a clean install. I've followed the instructions for the diagnostic tool and am including it in this post.

Thank you so much in advance!


My System SpecsSystem Spec
.
09 Jan 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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

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
---------
My System SpecsSystem Spec
09 Jan 2014   #3
Optics

Win 7 Ultimate x64
 
 

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.
My System SpecsSystem Spec
.

10 Jan 2014   #4
Optics

Win 7 Ultimate x64
 
 

Well my first blue screen since the lycosa driver after having driver verifier running overnight. Looks like the same type from the start of all of this. IRQL_NOT_LESS_OR_EQUAL (ntoskrnl.exe)

Here is an updated dump file
My System SpecsSystem Spec
11 Jan 2014   #5
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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
My System SpecsSystem Spec
11 Jan 2014   #6
Optics

Win 7 Ultimate x64
 
 

I had already updated the razer driver. The string of BSOD before the last (irq less than equal) were what led me to that. Odd though the driver from razers site was the same I already had. 8.002 or something. I found an updated one on techspot for 8.003. After updating that, driver verifier stopped blue screening on startup.

Should I be using that cloud based configurator in the link? If so that's new to me but can give it a shot.
My System SpecsSystem Spec
11 Jan 2014   #7
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Now run the computer without Driver Verifier enabled
My System SpecsSystem Spec
Reply

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




Thread Tools




Similar help and support threads
Thread Forum
Random BSOD error driver ntoskrnl.exe (address ntoskrnl.exe+74ec0)
Hey guys so I've been getting some random BSOD errors every few days or so. I usually leave my computer on when I am at work or sleep and either when I come home or wake up my computer is off. So I turn it on and it says that the computer didn't shut down properly when I start up. I downloaded...
BSOD Help and Support
Random BSOD--Several different codes back to back. New computer.
Computer seems stable and then will randomly BSOD-- Doesnt seem to be consistent with what im doing. A few of the BSOD's came after a 'error memory reference line' or something like that. Computer is new, I installed drivers with supplied disks from motherboard manufacturer (asus). At first I...
BSOD Help and Support
Linking computer to TV
He there, New to the forum and need basic information. I am trying to link my windows 7 computer to my Sony Bravia television. I have bought ethernet cables for my TV and router. I can get you tube on the TV so the link with the router seems to be OK. My computer is wi fi to the router. How do I...
Music, Pictures & Video
Linking to other sites
If forum rules restrict linking how does one provide updates or improvments without linking, as in Drivers
Chillout Room
Linking computer to TV
I do not think this is the forum for the question but here goes. I am looking for advice on the following: I am an old pensioner in poor health and spend a lot of time in my bedroom on the internet. I have a satellite connection coming in to my bedroom and I am going to purchase a flat screen...
Media Center


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:48.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App