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: BSOD from ntoskrnl when explorer.exe is open

07 Nov 2013   #11
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Update the display driver to the latest.

And, Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark


My System SpecsSystem Spec
.
17 Feb 2014   #12
Coherent

Windows 7 Home Premium 64bit
 
 

PC's recently started doing crazy things again!

I've got the most recent driver and stress testing seems to be ok.
I thought it coincided with installed IE11 but I've been using chrome recently and it still seems to have issues.

Many thanks for any advice as always!

Ben
My System SpecsSystem Spec
18 Feb 2014   #13
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Various different BSODs head to head.

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 memtest 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 1A, {41284, 7379001, 5469, fffff70001080000}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

Followup: MachineOwner
---------------------------------------------------------
BugCheck 24, {1904fb, fffff8800db19ce8, fffff8800db19540, fffff880012a8317}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )

Followup: MachineOwner
---------------------------------------------------------
BugCheck 3B, {c0000005, fffff960002ff016, fffff88009847c90, 0}

Probably caused by : win32k.sys ( win32k!RBRUSH::vRemoveRef+12 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
.

08 Mar 2014   #14
Coherent

Windows 7 Home Premium 64bit
 
 

Right, my PC's been doing some odd things which seem to coincide with turning driver verifier on. (been on for a while now because I forgot it was on!! )
Hopefully it will point to the culprate!!!
I've got a feeling it will point to the graphics card again though, the errors don't cause a BSOD but the effect is similar, that horrible glitchy audio of a PC in pain but my screen goes unreadable and wont reset until I restart.

Many thanks for any advice (as always!).
Ben
My System SpecsSystem Spec
08 Mar 2014   #15
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Before checking the dumps, I will ask for the result of memtest 86+.

Because DV applies here only if memtest did not show any error.
My System SpecsSystem Spec
10 Mar 2014   #16
Coherent

Windows 7 Home Premium 64bit
 
 

Hi arc,

I ran memtest a few time and it didn't show any errors.

Thanks
Ben
My System SpecsSystem Spec
10 Mar 2014   #17
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Checked the BSODs of 17/02 .... they all nor not providing any sufficient information, rather than some hints of memory corruption. Though the memory corruption can be caused by some misbehaving drivers too.

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.
My System SpecsSystem Spec
21 Mar 2014   #18
Coherent

Windows 7 Home Premium 64bit
 
 

Ran verifier for a few days and got the same weird glitch screen but without the crash dumps.
Had a couple of crashes this evening which I think point to graphics again, I've double check and the drivers are definitely up to date.
There's one that looks like it may be caused by my work VPN software so I've now uninstalled that.
Not sure what else to try.
Could this be faulty/incompatible hardware?
My System SpecsSystem Spec
21 Mar 2014   #19
Thedoctor44

 

I very much doubt it's hardware from what you and Arc have described; it sound like a driver related issue. Mainly because when you've changed a driver version or any other software change it seems to fix it for a while. If it was hardware related it then software changes wouldn't really help, it would also be fairly consistent.
I'm not saying it's definitely not hardware but it seems unlikely.
My System SpecsSystem Spec
22 Mar 2014   #20
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

So when you enabled Driver Verifier, it did not cause any BSOD at all? And you noticed screen glitches only?

Your last three crash dumps are all different within a very small period.
Code:
BugCheck 4E, {99, 35b4aa, 0, fffffa800a11dfe0}

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

Followup: MachineOwner
---------
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff8800f1ab151, fffff880059b3ef8, fffff880059b3750}

Probably caused by : atikmdag.sys ( atikmdag+110151 )

Followup: MachineOwner
---------
Code:
BugCheck 1A, {41284, ef20001, 1d669, fffff70001080000}

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

Followup: MachineOwner
---------
Uninstall your installed latest version of the display driver.
Then clean up any possible leftover.
Then install version 13.9 WHQL only.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

How many passes you ran memtest? Run memtest again. Let us see a camera snap of the computer screen when it is completing 8 passes.
My System SpecsSystem Spec
Reply

 BSOD from ntoskrnl when explorer.exe is open




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
0x00000124 ntoskrnl.exe ntoskrnl.exe+4a63cc BSOD Error runninganygame
i keep getting BSOD when playing game new graphics i dont know where to start when its comes to BSOD stuff 110414-10576-01.dmp 11/4/2014 10:48:39 PM 0x00000124 00000000`00000000 fffffa80`0af318f8 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+4a63cc ...
BSOD Help and Support
BSOD Address:ntoskrnl.exe+75bc0; dxgmms1.sys,ntoskrnl.exe,Ntfs.sys
Hi, to make things easier for you,below is the Bug Check String, Driver, and crash address SYSTEM_SERVICE_EXCEPTION___dxgmms1.sys___ntoskrnl.exe+75bc0 MEMORY_MANAGEMENT_______ntoskrnl.exe____ntoskrnl.exe+75bc0 SYSTEM_SERVICE_EXCEPTION___ntoskrnl.exe____ntoskrnl.exe+75bc0...
BSOD Help and Support
BSOD when idling with network open / ntoskrnl.exe+75169
any ides driver are all up to date and win7 install is less thin 1 month. no fragmentation on drives. custom pc with stock clocks on all hardware nvidia gtx 560 2gb supper clocked evga 16 (4x4) gb 1300 ram asus saber tooth 990FX amd 8120 FX
BSOD Help and Support
BSOD ntoskrnl.exe , All the Time !! Crash Address ntoskrnl.exe+80640
Jan 2014 //------------------------------------------- How to Solve : 1- I've uninstalled my windows and recover my laptop with recovery DVD to it's original factory state.(original windows :)) 2- Never installed Norton internet security again , I'm using Microsoft Security Essentials now. 3-...
BSOD Help and Support
Random BSOD Reporting ntoskrnl.exe+75c40 & ntoskrnl.exe+7efc0
I'm getting random Blue Screens and can't figure out why. I'm not running any hardcore programs. I'm mostly just using Microsoft Office and Firefox. The BSOD's seem to happen when I'm in Outlook, Excel or Firefox. Haven't been able to determine exactly which at the time as I'm moving back and...
BSOD Help and Support
BSOD error ntoskrnl.exe+7f1c0 - lots of Chrome browser tabs open
Windows 7 Pro x64 original installed OS OEM hardware is 2.5 years old original installation of OS Thanks for your help!!!
BSOD Help and Support


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 19:43.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App