BSOD error due to ntoskrnl.exe
Greetings,
Recently I have been facing some problems due to BSOD.
I have used the BlueScreenView and found out that the reason is ntoskrnl.exe, and to my knowledge I think it cannot be upgraded.
Could you please tell me what is the issue.
MY Minidumps are here
http://clip2net.com/s/1uDb2
Same file text version:
==================================================
Dump File : 011712-21793-01.dmp
Crash Time : 1/17/2012 1:05:51 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000058
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`0312f770
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\011712-21793-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 275,304
==================================================
My system specs are
AMD Phenom II x4 945
Asus M5a78l-mlx
ATI HD Radeon 4670
DDR3 1333mhz 4+2 = 6GB
Thank you for your support.
Solutions to the Problem BSOD error due to ntoskrnl.exe
Download SmartPCFixer to Fix It (Free)
TEMPORARILY uninstall Daemon Tools and ZoneAlarm.
If it stops the BSOD's, then you know what you've gotta do.
You don't have Daemon Tools, it's Alcohol 120% that has the offending sptd.sys driver
AMD OverDrive is also a possible BSOD cause. Disable it in the AMD Control Center in order to test it.
Differing memory dumps in the WER section of MSINFO32 are suggestive of a hardware problem. Please try the free diagnostics at this link:
http://www.carrona.org/hwdiag.html
Boot in Safe Mode:
- Open Run command as previously described
- Type MSConfig
- Click on Boot tab
- Tick Safe boot in Boot option
- Select Network
- Click Apply and OK
- Reboot your system
Your system will boot in Safe mode with Networking. You may now try and open Windows Store and should not see any errors.
Recommended Method to Repair the Problem: BSOD error due to ntoskrnl.exe:
How to Fix BSOD error due to ntoskrnl.exe with SmartPCFixer?
1. Download Error Fixer. Install it on your system.
2. After the scan is finished, you can see the errors and problems which need to be fixed.
3. The Fixing part is finished, the speed of your computer will be much higher than before and the errors have been removed.
Related: How to Download Toshiba Portege R500 HDD/SSD Alert Utility v.2.2.0.0 driver,Way to Update & Download Toshiba Satellite A355-S69403 Motorola Modem Region Select Utility v.2.2.3.0 driver,Where to Download Toshiba Satellite L305-S5926 HW Setup Utility v.2.00.11 driver,[Solved] Download Toshiba Satellite L675-S7115 Laptop Checkup v.2.0.6.22 driver,Method to Download Toshiba Satellite M645-S4080 Media Controller v.1.1.88.1 driver,Best Way to Download NVidia GeForce 6100 VGA Driver v.304.51 Certified,How Can You Update & Download NVidia GeForce 9300/nForce 730i VGA Driver v.310.19 Certified,Method to Download NVidia GeForce GT 330M Driver v.340.65,How Can I Update & Download NVidia GeForce GTX 590 Driver v.280.26 WHQL,Method to Download NVidia Tesla C2050 Driver v.319.17
Read More: BSOD tcpip.sys -- I've tried many recommendations to resolve this, still no luck [Solved],Solution to Error: BOINC Install Error 1325.boinc_data is not a valid short file name\",Tech Support: Brand new computer with Windows 7, Wireless connection working, still no internet?,Fast Solution to Problem: BSOD when i start pc or close lid for a while,Bold plus character style [Solved],All diagnostic tools give 0x800700C1, troubleshooting wizard can't continue,all files try to open with adobe,all icons on desktop have changed to Adobe icon and won't open,All functions of my outlook are working except it will not let me "REPLY" or start a "NEW" email,all f1-f12 shortcuts not work
No comments:
Post a Comment