cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
MikeeWalker
Fanfold Paper
Posts: 6
Registered: ‎03-14-2016
Location: Nottinghamshire
Views: 835
Message 1 of 10

M92p BSOD Caused by ntoskrnl.exe

Hey,

 

I've tried all over Google and this forum to find an answer to this.

 

I recenlty bought a this M92p Desktop computer from work and they were getting rid of them.

 

I've reinstalled Windows 7 using the Recovery Disc that my workplace had. This all went fine and then I upgraded to Windows 10 straight after. The computer ran fine for about 2 weeks. Now all of a sudden I'm getting the BSOD everytime I run the computer at least once! So far fingers crossed its not happened tonight yet, but probably will before I finish writing this.

 

I've looked at the DMP file and everytime it says ntoskrnl.exe has caused the crash.

 

Link to BluescreenViiew Screenshot

 

BSOD I get!

 

I've tried all the Memory Test and they come back with Passes. I've tried monitor programs to see if anything is overheating but they aren't. The computer can be idleing and it will happen.

 

I don't know what else to do.

 

I have one device in the manager that has no drivers but I don;t know what this is? Update Driver brings up no suggestions???

 

Device Manager

 

Any suggestions would be much appreiciated thank you Smiley Happy

 

Mikee.

MikeeWalker
Fanfold Paper
Posts: 6
Registered: ‎03-14-2016
Location: Nottinghamshire
Views: 825
Message 2 of 10

Re: M92p BSOD Caused by ntoskrnl.exe

As suspected 7 minutes later my computer blue screened!

 

About ready to give up!!!

JDGillis
Bit Torrent
Posts: 2,716
Registered: ‎12-11-2015
Location: US
Views: 813
Message 3 of 10

Re: M92p BSOD Caused by ntoskrnl.exe

Without tha actual .dmp file, it is hard to say what driver is causing the crash.   You might want to use the online tool linked below to analyze the .dmp a bit more closely.    It usually can point you to the driver in the stack at the time of the crash, and hopefully you can get to the bottom of your BSOD.

 

OSROnline Instant Crash analyser

http://www.osronline.com/page.cfm?name=Analyze

MikeeWalker
Fanfold Paper
Posts: 6
Registered: ‎03-14-2016
Location: Nottinghamshire
Views: 797
Message 4 of 10

Re: M92p BSOD Caused by ntoskrnl.exe

Just got this.... Windows 8 Driver Fault??? Im on windows 10 haha

 

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.103.amd64fre.th2_release.160126-1819
Machine Name:
Kernel base = 0xfffff803`e5274000 PsLoadedModuleList = 0xfffff803`e5552cf0
Debug session time: Fri Feb 26 09:53:47.616 2016 (UTC - 4:00)
System Uptime: 0 days 4:32:42.294
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a00f58b461b830, Reserved
Arg2: b3b71bdf06e36159, Reserved
Arg3: 00000000000001a0, Failure type dependent information
Arg4: 0000000000000007, Type of corrupted region, can be
	0 : A generic data region
	1 : Modification of a function or .pdata
	2 : A processor IDT
	3 : A processor GDT
	4 : Type 1 process list corruption
	5 : Type 2 process list corruption
	6 : Debug routine modification
	7 : Critical MSR modification

Debugging Details:
------------------


BUGCHECK_STR:  0x109

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff803e53b6480

STACK_TEXT:  
ffffd001`92c680b8 00000000`00000000 : 00000000`00000109 a3a00f58`b461b830 b3b71bdf`06e36159 00000000`000001a0 : nt!KeBugCheckEx


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  BAD_STACK

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

 

JDGillis
Bit Torrent
Posts: 2,716
Registered: ‎12-11-2015
Location: US
Views: 777
Message 5 of 10

Re: M92p BSOD Caused by ntoskrnl.exe

Yeah, OSR needs to update their report, but Kernel Version 10586 is Windows 10 so not to worry.

 

I would start by Updating Drivers, especially your Intel Chipset (both the AMT Chipset drivres) and remove and reinstall your video driver.

 

Intel Chipset Drivers for M92p running windows 10

http://support.lenovo.com/us/en/products/desktops-and-all-in-ones/thinkcentre-m-series-desktops/thin...

 

Sometimes video drivers get corrupt, so download the latest video driver to your system, then from Device Manager, select your video card, right click and select uninstall making sure to check the box to "permanently delete driver software".    Once complete, install the new updated driver and reboot if needed.

 

If that fails, I would run the System File Checker to check for corrupted System files and replace them from the Window's cached files.

 

How to run System File Checker

 

  1. Right Click on the Start Menu and select Command Prompt (Admin)
  2. In the Administrator Command Prompt window, type:   

sfc /scannow

 

Note: Let the System File Check scan run until it completes: even if it appears to hang at about 20%.  It will eventually complete, but may take up to an hour to finish depending on the system.

 

Once it completes, it will give one of the following results:

 

  • "Windows Resource Protection did not find any integrity violations"  (If you get this message, then system file corruption was likely not your problem)
  • "Windows Resource Protection found corrupt files and successfully repaired them Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log"  (If you get this message, then your problem might have been corrupted system  files, and the problem may be fixed)
  • "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log"  (If you get this message, see below on how to run DISM to fix a corrupt Windows Component Store, and then run the SFC scan again)

Note:  If you get the message "Windows Resource Protection could not perform the requested operation"  you will need to run the System File Checker scan in safe mode, but before doing so, make sure that the PendingDeletes and PendingRenames folders exist under %WinDir%\WinSxS\Temp (normally C:\Windows\WinSxS\Temp), and if not, create them.

 

How to start your PC in safe mode in Windows 10

http://windows.microsoft.com/en-us/windows-10/start-your-pc-in-safe-mode

 

 

If the SFC scan fails to fix all the corrupt files, there is another tool you can use called the Deployment Imaging and Servicing Management (DISM) tool to download and fix Windows Component Store corruption.    This is needed when the sfc/scannow  command is unable to repair corrupted or modified system files because the Windows Component Store (source) itself is corrupted.

 

To run DISM

 

  1. Make sure you are connected to the internet, and close all programs
  2. Right Click on the Start Menu and select Command Prompt (Admin)
  3. In the Administrator Command Prompt window, type:

Dism /Online /Cleanup-Image /RestoreHealth

 

Note: After running the DISM utility successfully, you must run the System File Checker again to fix any corrupted system files left unrepaired earlier..

MikeeWalker
Fanfold Paper
Posts: 6
Registered: ‎03-14-2016
Location: Nottinghamshire
Views: 766
Message 6 of 10

Re: M92p BSOD Caused by ntoskrnl.exe

Thank you for the detailed reply.

 

I've Installed the Intel Chipset drivers all ok. I noticed on my GPU that it was installed via windows. So I went onto AMD and got the drivers my self, which updated it from v15 to v16.

 

I've run the SFC test and it came back with the second result

 

"Windows Resource Protection found corrupt files and successfully repaired them Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log"  (If you get this message, then your problem might have been corrupted system  files, and the problem may be fixed)

 

Do I just leave it now and see it it happens again?

 

JDGillis
Bit Torrent
Posts: 2,716
Registered: ‎12-11-2015
Location: US
Views: 760
Message 7 of 10

Re: M92p BSOD Caused by ntoskrnl.exe

Good news,    

 

Hopefully the new drivers and repaired system files will make the BSOS's a thing of the past.

 

 

You might run a quick Windows CheckDisk just to be sure that the Hard Drives structure is good too, but that may not be necessary.

 

I like to run Check Disk first in read only mode from a Admin Command Prompt by typing chkdsk and pressing return.

 

If it finds any errors, then from the same Admin Command Prompt, run it again, only this time type chkdsk /f  press return, and then reboot.

 

The /f switch will run CheckDisk before Windows loads so any errors can be repaired.

 

 

Note:  If you are curious about what files were fixed by the SFC scan, type the following into a Admin Command Prompt, and it will put the details in a text file called sfcdetails.txt on the root of your Hard Drive, or C:\

 

 

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >C:\sfcdetails.txt

 

Take Care,

MikeeWalker
Fanfold Paper
Posts: 6
Registered: ‎03-14-2016
Location: Nottinghamshire
Views: 739
Message 8 of 10

Re: M92p BSOD Caused by ntoskrnl.exe

Hey, 

 

Well after doing all that last night I ran the computer for about 4-5 hours with no problems. I've turned it on today and 20 minutes into running it BSOD again, I was just browseing eBay. I've noticed this happens everytime I switch the computer on in the first 30mintues. Then after a restart the computer will run fine for hours!!.

 

I've scanned the DMP file and its tha same as the one above. I'm now running chkdsk to see what that comes up with.

 

Its just finished with "Errors Found". So gonna chkdsk /f and let it do its work.

 

Update: So I've run chkdsk /f and restarted the pc. Once finished and restarted I ran it again with the OS loaded. It can back with no problems found this time. Fingers crossed it stops blue screen now!

 

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.103.amd64fre.th2_release.160126-1819
Machine Name:
Kernel base = 0xfffff803`e5274000 PsLoadedModuleList = 0xfffff803`e5552cf0
Debug session time: Fri Feb 26 09:53:47.616 2016 (UTC - 4:00)
System Uptime: 0 days 4:32:42.294
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a00f58b461b830, Reserved
Arg2: b3b71bdf06e36159, Reserved
Arg3: 00000000000001a0, Failure type dependent information
Arg4: 0000000000000007, Type of corrupted region, can be
	0 : A generic data region
	1 : Modification of a function or .pdata
	2 : A processor IDT
	3 : A processor GDT
	4 : Type 1 process list corruption
	5 : Type 2 process list corruption
	6 : Debug routine modification
	7 : Critical MSR modification

Debugging Details:
------------------


BUGCHECK_STR:  0x109

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff803e53b6480

STACK_TEXT:  
ffffd001`92c680b8 00000000`00000000 : 00000000`00000109 a3a00f58`b461b830 b3b71bdf`06e36159 00000000`000001a0 : nt!KeBugCheckEx


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  BAD_STACK

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


JDGillis
Bit Torrent
Posts: 2,716
Registered: ‎12-11-2015
Location: US
Views: 716
Message 9 of 10

Re: M92p BSOD Caused by ntoskrnl.exe

Hopefully your problem has ceased, but if not you might try the following.

 

Run a malware scan using a free program called malwarebytes from malwarebytes.org.    Note that it will prompt you to start a trial of the full version, which runs in the background all the time (and I believe it will also ask if you want to automatically check for updates), both of which are not needed right now, so just install the free manual scanner.   

 

Once installed, open the Malwarebytes program and from the Settings menu at the top, select "Detection and Protection" from the left side and check the box "Scan for Rootkits".    

 

Malwarebytes does a good job of checking for adware/spyware that is sometimes missed by normal AntiVirus programs, and its rootkit scan is pretty good too.

 

If nothing is found, then you might do some sluething using the "Programs and Features: Control Panel to see if you installed any programs prior to the BSOD's starting, and if so, remove them, and them reinstall one at a time until you find the culprit.

 

 

 

MikeeWalker
Fanfold Paper
Posts: 6
Registered: ‎03-14-2016
Location: Nottinghamshire
Views: 629
Message 10 of 10

Re: M92p BSOD Caused by ntoskrnl.exe

Hello,

 

Still no better of??

 

I've tried everything you suggested and I even went out and bought a new GPU as I had a slight feeling it was that causing it (Radeon HD6870 upgraded to GTX 670) but no luck.

 

Blue Screen View

 

As you can see from BlueScreenView, the computer crases near on everyday! But only once. Like I said in previous posts. The computer boots and runs for about 20-30 minutes, then the BSOD happens. Once its rebooted by itself it runs fine for hours! I wouldn't have to much of a problem with this as I now expect it to happen. So in the first half hour I'll make sure I'm not doing anything that requires saving just so I don't lose it.

 

I've also noticed if I run a game, the blue screen doesn't happen.

 

It must be something to do with that Windows Kernal exe. But all scans come back find.

 

Is there and contacts in Lenovo or Windows that will look into this problem?

 

Thanks for all your help so far JDGillis!

Check out current deals!


Shop current deals

Top Kudoed Authors