• Home   /  
  • Archive by category "1"

Ntoskrnl.Exe Bsod Windows 7 Solved Assignment

By Sophie Luoin Blue Screen ErrorTags: BSOD

If you’re on Windows 7, and you’re seeing this horrifying blue screen telling you that your problem seems to be caused by ntoskrnl.exe, no need to panic about it, many Windows 7 users are reporting it, and the best of all, it’s possible to fix. 

How do I fix the ntoskrnl.exe blue screen of death error? 

Here are 3 solutions for you to try. You may not have to try them all; just work your way down the top and find the one works for you. 

Method 1: Update Drivers
Method 2: Reset Overclocking Settings
Method 3: Perform a Memtest 

What is ntoskrnl.exe? 

Ntoskrnl.exe is the kernel of the operating system. Without it, Windows just won’t work. If this file is at fault, your computer is very likely to have frequent blue screen of deaths and have more problems other than BSOD. 

1: Update Drivers 

Outdated or faulty drivers is one of the reasons for this blue screen of death error. You should verify that all your devices have the right driver, and update those that don’t. 

If you don’t have the time, patience or computer skills to update your drivers manually, you can do it automatically with Driver Easy

Driver Easy will automatically recognize your system and find the correct drivers for it. You don’t need to know exactly what system your computer is running, you don’t need to risk downloading and installing the wrong driver, and you don’t need to worry about making a mistake when installing.

You can update your drivers automatically with either the FREE or the Pro version of Driver Easy. But with the Pro version it takes just 2 clicks (and you get full support and a 30-day money back guarantee):

1)Downloadand install Driver Easy.

2) Run Driver Easy and click the Scan Nowbutton. Driver Easy will then scan your computer and detect any problem drivers.

3) Click theUpdate button next to all flagged devices to automatically download and install the correct version of their drivers (you can do this with the FREE version).

Or clickUpdate All to automatically download and install the correct version ofallthe drivers that are missing or out of date on your system (this requires the Pro version – you’ll be prompted to upgrade when you click Update All). 

2: Reset Overclocking Settings

One of the reasons for this blue screen of death error is overclocking drivers. If you have a trusted software to help you change the overclock in BIOS, use it. 

If not, follow the instructions below to help you clear the CMOS from within the BIOS menu and reset your BIOS settings back to their factory default state. 

Note: The following instructions are for Windows 7. The procedure is different if you’re ob Windows 8, 8.1 or 10 operating system. 

1) Press and hold the power button for about 10 seconds, or until your system completely shut down. 

2) Power on the system. As soon as the first logo screen appears, immediately press F1F2, F10, ESC or Delete for desktops to enter the BIOS.

NOTE: Sometimes you might need to press the combinations such as CTRL+ ALT+ ESC or CTRL+ALT+DEL if you are using a rather old machine. The keys to press differ from computers of different manufacturers and different models. You might need to choose the correct key to press according to what you see on the notification. 

3) Use the arrow key to go to Exit and then move down to Load Setup Defaults. (Your computer might be different, but you should be able to see the option Load Setup Default.) 



4) Then press the Enter key. You might be able to see notification like this. Use the arrow key to select Yes and then press Enter again.

5) Exit Saving Changes should be highlighted now. Press Enter and then press Enter again to save configuration change. 

You computer will restart. 

Again, the information showing on your computer may be different from mine and you should do the settings accordingly. If you’re not sure how you could perform certain moves, please go to the official support webpage of the manufacturer of your computer and ask for help. 

 

3: Perform a Memtest

The ntoskrnl. exe BSOD is usually related to memory, possibly caused by a faulty driver. It’s suggested that you run the following memory test to verify your memory and find out which driver is causing the problem. 

Note: If you’re over-clocking anything, please shut them down first before you run the tests. You will need to reboot your computer to perform the test. During the test, you won’t be able to use your computer. 

1) On your keyboard, clcik the Start button, then type WindowsMemory Diagnostic and press Enter

2) Click Restart now and check for problems(recommended). Be sure to save your work first because your computer will start immediately. 

3) Your computer will restart and the Windows Memory Diagnostic Tool screen will appear.  

The test could take some time to finish. You’ll see the test result after you log on. 

If the test result indicates that something is off with your software or hardware, feel free to leave a comment and we’ll see what we can do to help. 

jimjamrockshard

For a while, I've been experiencing many crashes specifically when playing games such as project cars, assassin's creed and watchdogs. For some reason if I lower the graphics settings, some games seem to be just fine, and don't crash untill I bump up the settings, like Rainbow six siege. What happens when my pc crashes is that the screen instantly goes black, and doesn't show an actual BSOD but my graphics card fans blast to the max for a few seconds followed by an automatic reboot. Once rebooted, a windows message pops up showing that it was caused by a BSOD. This first occured when I had a faulty molex to 6-pin pcie cable, which i replaced and it fixed it, but now it's just happening all over again. (Note that my power supply doesn't have a 6-pin pcie cable, and was pretty cheap, I'm thinking this to be the culpret)

----------------------------------------------------------------------------------------------------
My System Specs:
Geforce GTX 1060 3GB
AMD FX-4300
16GB DDR3 RAM
WD 1TB Hard Drive
ASUS M5A78L-M LX3 Micro ATX Motherboard
----------------------------------------------------------------------------------------------------

Minidump For Crash:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\022518-29655-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
Machine Name:
Kernel base = 0xfffff800`04401000 PsLoadedModuleList = 0xfffff800`04643750
Debug session time: Sun Feb 25 10:09:01.766 2018 (UTC + 0:00)
System Uptime: 0 days 0:00:10.828
Loading Kernel Symbols
....................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800e012038, 0, 0}

Probably caused by : hardware

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

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800e012038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`031c45b0 fffff800`046c0cd9 : fffffa80`0e012010 fffffa80`0cc33b50 fffffa80`00000006 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031c4ad0 fffff800`045a05e7 : fffffa80`0e012010 fffff800`0461a2f8 fffffa80`0cc33b50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031c4b00 fffff800`04507ee5 : fffff800`0467cbc0 00000000`00000001 fffffa80`0dbd6960 fffffa80`0cc33b50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031c4b40 fffff800`0447c085 : fffff880`00e6ee00 fffff800`04507ec0 fffffa80`0cc33b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031c4b70 fffff800`0470c622 : 160a1b19`0a1e1a0b fffffa80`0cc33b50 00000000`00000080 fffffa80`0cbe9870 : nt!ExpWorkerThread+0x111
fffff880`031c4c00 fffff800`04463da6 : fffff880`02fd7180 fffffa80`0cc33b50 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031c4c40 00000000`00000000 : fffff880`031c5000 fffff880`031bf000 fffff880`031c3c40 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

2: kd> lmvm hardware
start end module name
Mini Kernel Dump does not contain unloaded driver list

-------------------------------------------------------------------------------------------------------

I know it says 'Probably caused by: Hardware' But i'm not sure what exactly could be causing it. If anyone could help me it would be much appreciated!

One thought on “Ntoskrnl.Exe Bsod Windows 7 Solved Assignment

Leave a comment

L'indirizzo email non verrà pubblicato. I campi obbligatori sono contrassegnati *