Different random BSOD, ntoskrnl.exe
Hello
Brett
Two different causes. First and foremost your Kaspersky. I would like to delete and replace it with MSE
http://support.Kaspersky.com/downloads/utils/kavremover10.zip
http://www.Microsoft.com/security_essentials/
Second is related to keyscrambler.sys KeyScrambler keyboard driver. I remove if not required or update to the latest if it is.
Tags: Windows
Similar Questions
-
Frequent and random of ntoskrnl.exe BSOD / wdf01000.sys
Hello
I get a lot of crashes BSOD recently, through many different programs, apparently at random. BlueScreenView told me it's on ntoskrnl.exe / wdf01000.sys almost every time, but googleing it does not give me an answer. Can anyone help me with any idea what these are, or correct?Windows 7 64-bit, here's a link to my most recent minidumps...https://DL.dropbox.com/u/14709604/minidump.7z
Thank youLukeLuke
This driver is dated 2004
ctgame.sys Port enumerator creative play Creative Technology Ltd.This driver may very probably be updated, but the exact model is required to identify the right driver
Ralink 802.11 USB Wireless netr7364.sys adapt Driver Ralink Technology -
BSOD ntoskrnl.exe + 72 0x0000009f DRIVER_POWER_STATE_FAILURE has 40
I almost brand new HP ProBOOK 450 G2 with Windows 7 Enterprise, just noticed today the first Memory Dump, thought then to ask... like the laptop is under warranty... laptop computer is on battery power and the battery is dead so saw the light flashing 'orange' and he got the memory dump and he came down, the battery was finished It happened... but its still not the right way to go then... I have through the app "BlueScreenView" about something, but he could not say exactly... searched thing many error BSOD here in the office, but none had the same error, sharing so if someone is kind enough to help.
Dump file 050415-21028 - 01.dmp
Time of the accident 04/05/2015-11:01:32
Bug Check String DRIVER_POWER_STATE_FAILURE
Bug check code 0x0000009f
Parameter 1 00000000'00000003
Parameter 2 fffffa80'07f37a10
Parameter 3 fffff800'048943 d 8
Parameter 4 fffffa80'08da0010
Caused by the driver Ntoskrnl.exe
Caused by the address ntoskrnl.exe + 72 has 40DMP file: http://1drv.ms/1K9FKRC
Thanks in advance
ONE
This phenomenon was related to rtlane.sys NDIS Driver of Realtek Semiconductor Corporation. I remove the current driver and install the latest driver available.
-
Please help me solve this BSOD ntoskrnl.exe, ntkrnlmp.exe
Hello
I have problems with my new computer since I bought it, it started giving problems. Now this BSOD. I am totally frustrated with it. Please help me get rid of this questions.Here is the link of the minidump file:https://SkyDrive.live.com/redir?RESID=1F218460C89B0917%21114I guess that the culprit is wireless driver. With the old version of the wireless driver, I got another BSOD, so I uninstalled and installed the most recent version. Still problem persists.With whoCrashed, I found this information:Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
CPU: GenuineIntel Intel (r) Core i7-3610QM CPU @ 2.30 GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8469991424 total
VM: 2147352576, free: 1902690304Crash Dump Analysis
Crash dump directory: C:\Windows\MinidumpDumps are enabled on your computer.
Tuesday, December 23, 13 9:36:04 CEST your computer crashed
crash dump file: C:\Windows\Minidump\122313-27736-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0 x 72680)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8007539060, 0xFFFFF80000B9C3D8, 0xFFFFFA800FE606B0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Tuesday, December 23, 13 9:36:04 CEST your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8007539060, 0xFFFFF80000B9C3D8, 0xFFFFFA800FE606B0)
Error: DRIVER_POWER_STATE_FAILURE
Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Please help me. Thanks in advance.Apvmz
This phenomenon was related to the device driver wireless Extensible athrx.sys of Atheros Communications, Inc. Yours is almost 2 years so not the most recent.
I would like to re - install the latest driver available
-
Windows 7 BSOD - ntoskrnl.exe (nt + 0x7F1C0)
I have this problem since April, 2012
HP support suggested that I should reinstall windows 7. I did some time at the beginning of August, but the problem persists.Help, please! Otherwise, I'll keep change the OS with a Microsoft OS No.Here are the dumps:(Local) information system
computer name: RADU-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
CPU: GenuineIntel Intel (r) Core i5 CPU M 520 @ 2.40 GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4145868800 total
VM: 2147352576, free: 1943330816Crash Dump Analysis
Crash dump directory: C:\Windows\MinidumpDumps are enabled on your computer.
Sat 29-Sep-12 12:56:36 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092912-34632-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003344E30, 0xFFFFF8800AEE8C70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Sat 29-Sep-12 12:56:36 GMT crashed your computer
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: bcm42rly.sys (BCM42RLY + 0 x 1280)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003344E30, 0xFFFFF8800AEE8C70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\bcm42rly.sys
product: Broadcom iLine10 (TM) PCI network card
company: Broadcom Corporation
Description: Broadcom iLine10 (TM) PCI network adapter Proxy Protocol Driver
Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: bcm42rly.sys (Broadcom iLine10 (TM) PCI network adapter Proxy Protocol Driver, Broadcom Corporation).
Google search: bcm42rly.sys Broadcom Corporation SYSTEM_SERVICE_EXCEPTIONSat 29-Sep-12 12:47:59 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092912-34772-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003347E30, 0xFFFFF8800BCDCC70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Sat 29-Sep-12 12:39:07 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092912-35552-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000333CE30, 0xFFFFF88008D9CC70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Fri 28-Sept-12 07:30:24 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092812-35630-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003389E30, 0xFFFFF8800C0C5C70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Fri 28-Sept-12 07:20:56 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092812-58531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003349E30, 0xFFFFF8800ACA9C70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Play 27 Sept - 12 22:01:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092712-21606-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x1A (0xFFFFFA8000532F50, 41790, 0 x 0 x 0, 0xFFFF)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that an error occurred serious memory management.
This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Play 27 Sept - 12 09:26:28 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092712-30108-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x19 (0 x 22, 0 x 20000000000000, 0x0, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that a pool header is corrupt.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.The sea 26-Sept-12 07:12:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092612-19734-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs + 0x5A88)
Verification of error code: 0 x 24 (0xFFFFF8800996BAE8, 0xFFFFF8800996B340, 0x1904FB, 0xFFFFF88001231A74)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT file system driver
Bug control description: This indicates there is a problem in the NTFS file system.
The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.Mar 25 - Sep - 12 20:55:48 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092612-22354-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x7A (0xFFFFFFFFC0000005, 0xFFFFFA8004646060, 0x1, 0xFFFFF680000B1000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: this bug check indicates that the data page of the kernel of the required paging file cannot be read into memory.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.The game 20-Sept-12 15:08:27 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092012-53929-01.dmp
This was probably caused by the following module: win32k.sys (win32k + 0xC6A12)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000116A12, 0xFFFFF8800AC5B130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: Multi-User Win32 Driver
Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.Wednesday, August 7, 12 10:29:53 GMT crashed your computer
crash dump file: C:\Windows\Minidump\080712-41917-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x71F00)
Verification of error code: 0 x 50 (0x0, 0xFFFFF8000311445B, 0xFFFFF8A00B2DF000, 0 x 2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that invalid system memory was referenced.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Wednesday, August 7, 12 10:08:21 GMT crashed your computer
crash dump file: C:\Windows\Minidump\080712-53305-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x1A50F3)
Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002DBB0F3, 0xFFFFF880031A18B8, 0xFFFFF880031A1110)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.We need the DMP file because it contains the single record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.
If you are overclocking STOP
You may be able to get the DMP files without crashing by booting in SafeMode (F8) with networking.
Please follow these instructions to collect data against crashes and upload them here, to your Skydrive or a service such as Rapidshare file sharing.
http://www.SysNative.com/forums/showthread.php/68-blue-screen-of-death-%28BSOD%29-posting-instructions-Windows-8-7-amp-Vista?p=303&viewfull=1#post303
http://SysNative.com/0x8/BSOD_Windows7_Vista_v2.64_jcgriff2_.exe
To allow us to help you with symptoms BSOD on your computer, download the contents of your folder "\Windows\Minidump".
The procedure:
* Copy the contents of \Windows\Minidump to another location (temporary) somewhere on your machine.
* Zip up the contents of this folder
Please, upload to skydrive or a file sharing service and put a link to them in your next post.Go to start > search/run > cmd > msinfo32 and include it in the upload
To ensure the minidumps are enabled:
* Click Start, in the search box, type: sysdm.cpl, press ENTER.
* On the Advanced tab, click Startup and recovery... Settings button.
* Make sure that automatically restart is unchecked.
* Under the writing debugging information header, select image partial memory (256 KB) in the list box drop-down (varies from 256kb).
* Ensure to that small Dump Directory is listed as % systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.http://www.SysNative.com/forums/showthread.php/325-BSODs-but-no-dump-files
http://www.osronline.com/article.cfm?article=545
Please also go to start > run > msinfo32 and record the results. Send it with the DMP files, thank you.
-
Windows 8 unexpected Kernel Mode trap BSOD (ntoskrnl.exe)
Hello, I got the blue screen that gives me the error code: UNEXPECTED_KERNEL_MODE_TRAP (ntoskrnl.exe). I have had this problem since I got my computer, but it happens that all the other day. I tested my RAM with memtest and everything was good. I also use on all drivers updated. I recently installed "WhoCrashed" hoping to get more information as to what was causing this error. Here's the report;
Thursday, June 26, 2014 6:31:37 PM GMT crashed your computer
crash dump file: C:\WINDOWS\Minidump\062614-28703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x153FA0)
Bugcheck code: 0x7F (0 x 8, 0xFFFFF802935ABE70, 0xFFFFF80293592FF0, 0xFFFFF80291C5AB6E)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: this bug check indicates that the Intel CPU generated a trap and the kernel could not catch this trap.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Any help will be much appreciated.
Thank you
Ryan
Ryan
The DMP was inconclusive pointing to memory. My gut says it's Symantec. I would like to do two things. Run the driver verifier and remove Symantec and use the built in Defender.
These accidents were related to the corruption of memory (probably caused by a driver).Please run these tests to check your memory and find which driver is causing the problem.
If you're overclocking (pushing components beyond their design) return you to default at least until the crash is resolved. If you don't know what it is that you're probably not overclocking.
Since then, it is more likely to be a pilot run everything first.1-Driver Verifier (for full instructions, see our wiki here)
If the auditor does not have the issue we move to it.2-Memtest. (You can learn more about running memtest here)
If you cannot start after you have enabled the auditor reboot in safe modeIn Vista & victory (F8)
Co-written by JMH3143.
-
BSOD - ntoskrnl.exe Critical_process_died 0x000000ef
Got BSOD problems on windows 2012 R2 server, Viewer bliuescreen points to critical_process_dies - ntpskrnl.exe
DMP file is linked here https://onedrive.live.com/redir?resid=CE9C8B0A89BD1546! 111 & authkey =! ABWSymb0WgE6tJA & ithint = the file % 2cdmp
Please notify
These accidents were related to the corruption of memory (probably caused by a driver).If you are overclocking anything reset by default before running these tests.In other words STOP! If you don't know what it means that you're probably not
1-Driver Verifier (for full instructions, see our wiki here)2-Memtest. (You can learn more about running memtest here) -
Windows 7 BSOD ntoskrnl.exe question
Hello. I'm having the same problem as the next person - http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/ntoskrnlexe-1040b-e58d2-6d5be/ea3a3e93-69bd-47c7-9f31-ddb723120912. I ran Driver Verifier and then encountered the problem of not being able to access my laptop normally. I disabled the driver verifier now.
I redid my laptop about 3 times in the hope of solving my BSOD problem, but it is ongoing.
Any help is appreciated.
David Martinez
THE
They are related to your video driver. I would like to begin by updating to the latest driver that yours is ~ 1 year.
Microsoft (R) Windows debug 6.3.9600.17029 AMD64 Version
Copyright (c) Microsoft Corporation. All rights reserved.Loading dump file [C:\Users\Ken\Desktop\052814-20592-01.dmp]
The mini kernel dump file: only registers and the trace of the stack are availableSymbol of validation of the path summary *.
Location of response time (ms)
Deferred SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) free x 64
Product: WinNt, suite: TerminalServer SingleUserTS
By: 7601.18409.amd64fre.win7sp1_gdr.140303 - 2144
Computer name:
Kernel base = 0xfffff800'02e63000 PsLoadedModuleList = 0xfffff800'030 was 6890
The debugging session: 14:44:02.483 Wed 28 may 2014 (UTC - 04:00)
System Uptime: 0 days 0:02:46.482
Loading the kernel symbols
...............................................................
................................................................
..................................................
Loading user symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck analysis *.
* *
*******************************************************************************Use! analyze - v to obtain detailed debugging information.
BugCheck C4, {c0, fffffa800a546340, f6, fffff8800f2b9879}
WARNING: Unable to verify timestamp for nvlddmkm.sys
ERROR: Module load completed but symbols can be loaded for nvlddmkm.sys
Probably caused by: nvlddmkm.sys (nvlddmkm + 9a 879)Follow-up: MachineOwner
---------2: kd >! analyze - v
*******************************************************************************
* *
* Bugcheck analysis *.
* *
*******************************************************************************DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has taken. It comes
because the driver was specified in the registry as being suspect (by the)
Administrator) and the kernel has allowed substantial control of this driver.
If the pilot attempts to corrupt the system, looking for bugs, 0xC4, 0xC1, and 0xA
Be one of the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, handle user SEO as the core.
Arg2: 00000000000000c 0, the value of Handle referenced.
Arg3: fffffa800a546340, address of the current process.
Arg4: fffff8800f2b9879, address inside the pilot making the incorrect reference.Debugging information:
------------------BUGCHECK_STR: 0xc4_f6
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
Nom_processus: rundll32.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers (dbg). 140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff800033654ec to fffff80002ed8bc0
STACK_TEXT:
"" fffff880 ' 0 c 315308 fffff800 ' 033654ec: 00000000 ' 000000 c 4 00000000' 000000f6 00000000'000000 c 0 fffffa80 ' a 0, 546340: nt! KeBugCheckEx
"" fffff880 ' 0 c 315310 fffff800 ' 0337abf4: 00000000 ' 000000 c 0 fffffa80 ' 0a 546340 00000000'00000004 fffff880'0 c 317000: nt! VerifierBugCheckIfAppropriate + 0x3c
fffff880 ' 0 c 315350 fffff800' 03132890: fffff8a0 '000016-0 fffff880' 0c3155a0 fffff880 '0 c 315700 fffff880' 0c 315930: nt! VfCheckUserHandle + 0x1b4
"fffff880 ' 0 c 315430 fffff800 ' 031a95b5: 00000000 '00000000 fffff880' 00000001 fffffa80 '06067f30 fffff8a0' 05c08a00: nt! : NNGAKEGL: 'string' + 0x2027e
"fffff880 ' 0 c 315500 fffff800 ' 02ed7e53: fffffa80 '0aa1e060 fffff880' 0c3158b8 00000000'00000002 00000000'00000000: nt! NtQueryValueKey + 0 x 115
"" fffff880 ' 0 c 315690 fffff800 ' 02ed4410: fffff800 ' 03369 d 96 fffff880 ' 0f2b9879 fffff880 '0 c 315930 fffff880' 0c 315928: nt! KiSystemServiceCopyEnd + 0x13
fffff880 '0 c 315898 fffff800' 03369d 96: fffff880 ' 0f2b9879 fffff880 '0 c 315930 fffff880' 0c 315928 fffff800 ' 02ed4410: nt! KiServiceLinkage
"fffff880 '0c3158a0 fffff880' 0f2b9879: fffff880 ' 0c3168ca fffff880 ' 0 c 315970 fffff880 ' 0c3168b8 fffffa80 ' 0591ff18: nt! VfZwQueryValueKey + 0 x 76
fffff880 '0c3158f0 fffff880' 0c3168ca: fffff880' 0591ff18 fffff880 '0c3168b8 fffffa80' 0 c 315970 00000000 00000000': nvlddmkm + 0x9a879
fffff880'0c3158f8 fffff880'0 c 315970: fffff880 '0c3168b8 fffffa80' 0591ff18 00000000 00000000' fffff880 0'c 315920: 0xfffff880'0c3168ca
"fffff880 ' 0 c 315900 fffff880 ' 0c3168b8: fffffa80'0591ff18 00000000 00000000' fffff880 ' 0 c 315920 fffff980' 00000000: 0xfffff880'0 c 315970
"fffff880 ' 0 c 315908 fffffa80 ' 0591ff18: 00000000 '00000000 '0c 315920 fffff980'00000000 00000000 fffff880' 000000 c 0: 0xfffff880'0c3168b8
fffff880'0 c 315910 00000000 00000000': fffff880 '0 c 315920 fffff980' c 0 00000000 00000000'000000 ' 00280026 fffffa80: 0xfffffa80'0591ff18STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm + 9 has 879
fffff880'0f2b9879 3d340000c0 cmp eax, 0C0000034hSYMBOL_STACK_INDEX: 8
SYMBOL_NAME: nvlddmkm + 9 has 879
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
Nom_image: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5280da75
FAILURE_BUCKET_ID: X64_0xc4_f6_nvlddmkm + 9 has 879
BUCKET_ID: X64_0xc4_f6_nvlddmkm + 9 has 879
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xc4_f6_nvlddmkm + 9 has 879
FAILURE_ID_HASH: {0c031110-986a-b405-c565-3ead8c9b6e45}
Follow-up: MachineOwner
--------- -
After sleep ntoskrnl.exe error 0x0000009f DRIVER_POWER_STATE_FAILURE
DRIVER_POWER_STATE_FAILURE after sleep
When I put my laptop to sleep by closing the lid or choosing sleep from the beginning, I get a bsod (ntoskrnl.exe 0x0000009f DRIVER_POWER_STATE_FAILURE) when the recovery.BlueScreenView report:http://dl.dropbox.com/u/12993257/bsod.htmEmpty the file: http://dl.dropbox.com/u/12993257/091211-34538-01.zipAlso, for some reason that I do not get the bsod when it puts itself in standby (IE after expire) but I understand when it hibernate itself.Any help is appreciated!PhilHi chubble10,
Method 1
I suggest you try the steps from the following links:Stop error when you upgrade a computer that is running Windows 7 or Windows Server 2008 R2 standby or into hibernation, or when you restart the computer: "0x9F".
http://support.Microsoft.com/kb/975599stop "0x0000009F" error message when a computer enters and fate of putting into hibernation in Windows 7 or Windows Server 2008 R2
http://support.Microsoft.com/kb/981848Method 2
This issue could be due to corruption of the graphics card driver. I suggest you to update the graphics card drivers.Updated a hardware driver that is not working properly
http://Windows.Microsoft.com/en-in/Windows7/update-a-driver-for-hardware-that-isn ' t-work correctly -
Ntoskrnl.exe BSOD at random
I get a BSOD caused by ntoskrnl.exe or ntfs.sys, with a lot of different bugs 0x0f and 0x0A 0x01E. I used WhoCrashed to help me find what it was, but in no avai.
Here at random, take a few minutes to a few hours.
Here are the logs of WhoCrashedThursday, November 10, 2011 2:48:45 AM GMT crashed your computer
crash dump file: C:\Windows\Minidump\110911-26130-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs + 0x213D8)
Verification of error code: 0 x 24 (0xFFFFF88009D8C348, 0xFFFFF88009D8BBB0, 0x1904FB, 0xFFFFF80002EE2EEA)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT file system driver
Bug control description: This indicates there is a problem in the NTFS file system.
The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.Thursday, November 10, 2011 2:48:45 AM GMT crashed your computer
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs + 0x213D8)
Verification of error code: 0 x 24 (0xFFFFF88009D8C348, 0xFFFFF88009D8BBB0, 0x1904FB, 0xFFFFF80002EE2EEA)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT file system driver
Bug control description: This indicates there is a problem in the NTFS file system.
The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.Thursday, November 10, 2011 2:18:09 AM GMT crashed your computer
crash dump file: C:\Windows\Minidump\110911-19515-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs + 0x212A3)
Verification of error code: 0 x 24 (0xFFFFF88008DD4708, 0xFFFFF88008DD3F70, 0 x 190477, 0xFFFFF80002EA5C84)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT file system driver
Bug control description: This indicates there is a problem in the NTFS file system.
The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.Thursday, November 10, 2011 2:05:19 AM GMT crashed your computer
crash dump file: C:\Windows\Minidump\110911-22682-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0 x 70590)
Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
Error: "KMODE_EXCEPTION_NOT_HANDLED"
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Wednesday, November 9, 2011 11:39:15 PM GMT crashed your computer
crash dump file: C:\Windows\Minidump\110911-20638-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x705C0)
Bugcheck code: 0xA (0xFFFFF880029ED988, 0xFFFFF80002D205F1, 0x2, 0x0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Thursday, October 27, 2011 7:49:38 AM GMT crashed your computer
crash dump file: C:\Windows\Minidump\110911-25162-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x705C0)
Bugcheck code: 0xD1 (0xFFFFF8808327B1DA, 0xFFFFF880042A41EA, 0x2, 0 x 1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that a kernel-mode driver attempted to access pageable memory with a high IRQL.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Thursday, October 27, 2011 3:11:46 AM GMT crashed your computer
crash dump file: C:\Windows\Minidump\102611-21106-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0 x 70600)
Bugcheck code: 0x3B (0xC0000005, 0x1, 0x0, 0xFFFFF88009B94300)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.Let me know if I need to download the DPM
Hello
Doubt that its windows for millions would have the same questions.
If you think that your Windows installation disc is damaged, try these as a test.
This will give you a method to make and install from another disk as a test.
Windows 7 Enterprise - 90 day trial
http://TechNet.Microsoft.com/en-us/evalcenter/cc442495.aspxThey will help make you the ERD that are bootable.
If you need to repair disks - these help repair Windows not re-install.
Often an ERD will help you when the recovery disk does not work.Download Windows 7 system recovery discs - charge now $9.75 for ISO
images to make the discs.
http://NeoSmart.net/blog/2009/Windows-7-system-repair-discs/How to create a Windows 7 - free system repair disc
http://www.SevenForums.com/tutorials/2083-system-repair-disc-create.html========================================
These make it bootable Linux disks with many public services:
Hiren Boot CD
http://www.hirensbootcd.org/Rescue Kit Trinity
http://trinityhome.org/home/index.php?wpid=1&front_id=12System Rescue CD
http://www.SysRescCd.org/Main_PageKnoppix
http://www.Knoppix.NET/Scan a Windows PC for viruses from a Ubuntu Live CD
http://www.howtogeek.com/HOWTO/14434/scan-a-Windows-PC-for-viruses-from-a-Ubuntu-Live-CD/Use Ubuntu Live CD to backup files from your Windows computer dead
http://www.howtogeek.com/HOWTO/Windows-Vista/use-Ubuntu-Live-CD-to-backup-files-from-your-dead-Windows-computerI hope this helps.
Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle="" -="" mark="" twain="" said="" it="">->
-
I don't know why this is happening, but I'm getting random BSOD now and then. I tried to point out my system to see if it generates a BSOD, but multitasking 3d and photoshop programs and what's not stress, then when I least expect, BANG! BSOD.
The last of them, that I had now was in the middle of the night with almost no programs running. The system had worked for some time (one or two days), but nothing was he pointing out at the same time.What I think happened was: our microwave shorted out and caused a fuse to blow. But it was on another grid in our House (I hope I make myself clear, because I'm not used to talk about stuff like this in English!) so it should not affect my computer. But at the same time my microwave said "Thank you for everything!" my computer would BSOD. The thing is that my modem, my switch, my router and my NAS is connected to the electric network and my short circuted of switch. And my computer is connected to the switch cable.
This effect possible that excess tension (or something) has short circuted my switch and 'jumped' power to the switch and on the cable and sending there is a shock to my computer? Or am I just paranoid? Laughing out loudI know that the controllers are pushed to the limit of the memory and therefor tolerate very little when it comes to electricity. I ran MemTest4.00 14 passes but I came with nothing. But memtest that tests memory, not the controllers, right? I am watching a fried motherboard?
I did a windb, but I don't understand what he says. Could someone please translate this for me and give me your opinion?
In addition, when you run windb, it's tell me am I wrong symbols. -What this means, and where can I get the symbols he wants? And what symbols?Microsoft (R) Windows debug 6.12.0002.633 AMD64 Version
Copyright (c) Microsoft Corporation. All rights reserved.Loading dump file [C:\Windows\Minidump\Mini042910-01.dmp]
The mini kernel dump file: only registers and the trace of the stack are availableSymbol search path is: * invalid *.
****************************************************************************
* Loading of the symbol may be unreliable without a symbol search path. *
* Use .symfix to get the debugger to choose a symbol path. *
* After adjusting your path to symbols, use .reload to refresh the locations of symbols. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols cannot be loaded because the path is not initialized. *
* *
* The symbol path can be defined: *.
* using the _NT_SYMBOL_PATH environment variable. *
* with the help of thethere when you start the debugger argument. *.
* using the .sympath and .sympath + *.
*********************************************************************
Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack2) MP (4 procs) free x 64
Product: WinNt, suite: TerminalServer SingleUserTS
Computer name:
Kernel base = 0xfffff800 '02c4c000 PsLoadedModuleList = 0xfffff800' 02e10dd0
The debugging session: 23:43:16.368 Thursday, April 29, 2010 (UTC + 02:00)
System Uptime: 3 days 5:21:50.657
*********************************************************************
* Symbols cannot be loaded because the path is not initialized. *
* *
* The symbol path can be defined: *.
* using the _NT_SYMBOL_PATH environment variable. *
* with the help of thethere when you start the debugger argument. *.
* using the .sympath and .sympath + *.
*********************************************************************
Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Loading the kernel symbols
...............................................................
................................................................
................................................
Loading user symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck analysis *.
* *
*******************************************************************************Use! analyze - v to obtain detailed debugging information.
Bugcheck A, {fffffa7fffffffea, 2, 0, fffff80002c5a95c}
The kernel symbols are FALSE. Correct symbols to do the analysis.
*************************************************************************
*** ***
*** ***
Your debugger is not using the appropriate symbols *.
*** ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _KPRCB *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Your debugger is not using the appropriate symbols *.
*** ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _KPRCB *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Your debugger is not using the appropriate symbols *.
*** ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _KPRCB *.
*** ***
*************************************************************************
Probably caused by: ntoskrnl.exe (nt + e95c)Follow-up: MachineOwner
---------0: kd >! analyze - v
*******************************************************************************
* *
* Bugcheck analysis *.
* *
*******************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access an address pageable (or completely invalid) to a
application interrupt level (IRQL) that is too high. It is usually
caused by drivers using a wrong address.
If a kernel debugger is available, download the stack trace.
Arguments:
Arg1: fffffa7fffffffea, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bit field:
bit 0: value 0 = read operation, 1 = write operation
bit 3: value 0 = not an enforcement operation, 1 = performance operation (only on chips that support this level of State)
Arg4: fffff80002c5a95c, address memoryDebugging information:
------------------The kernel symbols are FALSE. Correct symbols to do the analysis.
*************************************************************************
*** ***
*** ***
Your debugger is not using the appropriate symbols *.
*** ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _KPRCB *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Your debugger is not using the appropriate symbols *.
*** ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _KPRCB *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Your debugger is not using the appropriate symbols *.
*** ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete. ***
*** ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information. The contact group that *.
you provided with these symbols, if you need this command for *.
work. ***
*** ***
Type referenced: nt! _KPRCB *.
*** ***
*************************************************************************ADDITIONAL_DEBUG_TEXT:
Use '! findthebuild' command to search for the generation of target information.
If the build information is available, run '! findthebuild s; .reload ' to set the symbol path and of loading symbols.MODULE_NAME: nt
FAULTING_MODULE: fffff80002c4c000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4b7d238f
READ_ADDRESS: could not get nt! MmSpecialPoolStart
Unable to get nt! MmSpecialPoolEnd
Unable to get nt! MmPoolCodeStart
Unable to get nt! MmPoolCodeEnd
fffffa7fffffffeaCURRENT_IRQL: 0
FAULTING_IP:
NT + e95c
fffff800'02c5a95c? ???CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0XA
LAST_CONTROL_TRANSFER: from fffff80002ca626e to fffff80002ca64d0
STACK_TEXT:
fffffa60 '01bde688 fffff800' 02ca626e: 00000000' 0000000 a fffffa7f ' ffffffea 00000000'00000002 00000000'00000000: nt + 0x5a4d0
fffffa60 '01bde690 00000000' 0000000-a: fffffa7f 'ffffffea 00000000'00000002 00000000'00000000 fffff800' 02c5a95c: nt + 0x5a26e
fffffa60 '01bde698 fffffa7f' ffffffea: 00000000'00000002 00000000'00000000 fffff800 '02c5a95c fffffa60' 04dbf8b0: 0xa
fffffa60 '01bde6a0 00000000' 00000002: 00000000 00000000' fffff800 '02c5a95c fffffa60' 04dbf8b0 00000000' 00000000: 0xfffffa7f'ffffffea
fffffa60'01bde6a8 00000000' 00000000: fffff800 '02c5a95c fffffa60' 04dbf8b0 00000000'00000000 00000000'00000000: 0 x 2STACK_COMMAND: .bugcheck; Ko
FOLLOWUP_IP:
NT + e95c
fffff800'02c5a95c? ???SYMBOL_NAME: nt + e95c
FOLLOWUP_NAME: MachineOwner
Nom_image: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Follow-up: MachineOwner
---------I'm grateful for any help I can get in that case.
My system is: AMD 9950BE CPU, motherboard ASUS Crosshair II Formula, 4 x 2 giga OCZ 1066 mhz memory, Vista Ultimate 64 bit, ASUS 295GTX GPU
Postal salvation,
I think you're in luck. It chances are you are one of those rare cases where the BSOD may not be hardware related. In addition, it is actually pretty rare to have so many errors after a sfc... Wow. I think that alone has helped reduce the risk of an another BSOD and was good insurance against other problems.
Do you have a chance to check the hard drive? Now, I would like to check the hard drive to see if there may be potential damage to the hard drive as well to help explain this number of errors (return to the material again).
Here's how to new:
http://Windows.Microsoft.com/en-us/Windows-Vista/check-your-hard-disk-for-errors
I think that advice on the anti-virus scanning are also actually still relevant today. I have a scan of one of the two groups below as soon as you can and let us know the result if you can.
virus/malware programs:
Symantec:
Works in Safe Mode and free:
_ http://security.symantec.com/sscv6/WelcomePage.asp
Trend Micro
_ http://housecall.trendmicro.com/
Ad-ware/spyware:
Ad-aware
Spybot Search and Destroy
http://www.safer-networking.org/
* It is an excellent versatile tool as it will both spyware and malware and has also a small footprint.
See you soon,.
Steve <> Microsoft Partner
-
Several BSOD with error different ntoskrnl.exe + 75c00 involving most of the messages
I am running Windows 7 64 bit on a homemade pc with the Asus motherboard, 8 GB of ram and a quad-core processor amd; If you need more specific information please ask. Most of the Bluescreens have different error messages, but all except one have been
Ntoskrnl.exe "caused by the driver" and "caused by the address. Most occurred when playing computer games. in the middle of the test I have updated my graphics card drivers and a few various other and I checked the ram to find errors although I should probably give him a half-dozen more going on.I will try to download a few zippers of depressed on skydrive. bear with me, I never did this before. NOPE, I can't. I can't even * find * skydrive. Someone please care to direct me to how it works yet? * edit *-it won't let me zip minidumps anyway. I give up. I'm about to perform technical support on this thing with his sledgehammer.
I tried to analyze the accident using windbg, but it fails to load the symbols for ntoskrnl. Here are some summaries of crash as recovered by the blue screen:
062713-13478 - 01.dmp 27/06/2013-21:31
KMODE_EXCEPTION_NOT_HANDLED
0x0000001E
FFFFFFFF "c0000005
fffff800'02e86d9c
00000000 00000000'
FFFFFFFF'ffffffff
Ntoskrnl.exe ntoskrnl.exe + 75c00 NT Kernel & System Microsoft® Windows® operating system Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318 - 1533) x 64 ntoskrnl.exe + 75c00 C:\Windows\Minidump\062713-13478-01.dmp 4 15 7601 276 080 6/27/2013 21:31:51
062913-14024 - 01.dmp 29/06/2013-07:34:23
KMODE_EXCEPTION_NOT_HANDLED
0x0000001E
FFFFFFFF "c0000005
fffff800'03159 cd 0
00000000 00000000'
FFFFFFFF'ffffffff
CLASSPNP. CLASSPNP SYS. SYS + 1901 x 64 ntoskrnl.exe + 75c00 C:\Windows\Minidump\062913-14024-01.dmp 4 15 7601 276 080 29/6/2013 07:35:21
062913-13384 - 01.dmp 29/06/2013 18:54:47
IRQL_NOT_LESS_OR_EQUAL
0x0000000A ffffba80'09f27a60
00000000'00000002
00000000 00000000'
fffff800'02f31c5f
Ntoskrnl.exe ntoskrnl.exe + 75c00
NT kernel & system Microsoft® Windows® operating system Microsoft Corporation
6.1.7601.18113 (win7sp1_gdr.130318 - 1533) x 64 ntoskrnl.exe + 75c00 C:\Windows\Minidump\062913-13384-01.dmp 4 15 7601 276 080 29/6/2013 18:55:47
062913-13962 - 01.dmp 29/06/2013-01:30:16
PM MEMORY_MANAGEMENT
0x0000001A
00000000'00041284
fffff680'0012 d 001
00000000'00000250
fffff700'01080000
Ntoskrnl.exe ntoskrnl.exe + 75c00 NT Kernel & System Microsoft® Windows® operating system Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318 - 1533) x 64 ntoskrnl.exe + 75c00 C:\Windows\Minidump\062913-13962-01.dmp 4 15 7601 276 080 29/6/2013 13:31:17
No specific information but if you look at the history of BIOS updated between your BIOS Setup and the last BIOS available you would appreciate that a number of improvements have been made.
You cannot count any error report when you have detected a faulty RAM. RAM corrupt system files, making it unreliable reports. When you installed the replacement RAM you run the System File Checker.
http://support.Microsoft.com/kb/929833I won't say there is no risk of update the BIOS, but if the instructions are followed carefully you shouldn't encounter any problem. The caveat is that you should not threatened the data files which can easily be saved on an external. You can't replace family photos and others.
-
BSoD, which is related to ntoskrnl.exe error
Hello. I've known a few occasional BSODS, all associated with ntoskrnl.exe. Two of them were 0 x 124, while the most recent is a 0 x 101. I already ran Ccleaner in case it was a registry problem, but I doubt it. I also did a BIOS update for a couple of months. My specs are:
Windows 7 x 64
CPU: AMD FX-6300
GPU: AMD Radeon HD 7750
Motherboard: Asus M5A78L-M LX3
Bluescreenview ran, so I'll post the reports here. Thanks for your help.
==================================================
Dump file: 111614-47096 - 01.dmp
Crash time: 15/11/2014 19:37:06
Bug Check String:
Bug check code: 0 x 00000101
Parameter 1: 00000000'00000021
Parameter 2: 00000000'00000000
Parameter 3: fffff880'02f65180
Parameter 4: 00000000'00000002
Caused by the driver: ntoskrnl.exe
Caused by the address: ntoskrnl.exe + 75bc0
File description: NT kernel & system
Product name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File version: 6.1.7601.18526 (win7sp1_gdr.140706 - 1506)
CPU: x 64
Plant address: ntoskrnl.exe + 75bc0
Stack address 1:
The stack address 2:
Address 3 the battery:
Computer name:
Full path: C:\Windows\Minidump\111614-47096-01.dmp
Number of processors: 6
Main version: 15
Minor Version: 7601
Size of the dump file: 275 608
Dump of file time: 16/11/2014-09:36:27
====================================================================================================
Dump file: 111314-38657 - 01.dmp
Crash time: 13/11/2014-18:35:27
Bug Check String:
Bug check code: 0 x 00000124
Parameter 1: 00000000'00000000
Parameter 2: fffffa80'07fa3038
Parameter 3: 00000000'00000000
Parameter 4: 00000000'00000000
Caused by the driver: ntoskrnl.exe
Caused by the address: ntoskrnl.exe + 4adb5c
File description: NT kernel & system
Product name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File version: 6.1.7601.18526 (win7sp1_gdr.140706 - 1506)
CPU: x 64
Plant address: ntoskrnl.exe + 4adb5c
Stack address 1:
The stack address 2:
Address 3 the battery:
Computer name:
Full path: C:\Windows\Minidump\111314-38657-01.dmp
Number of processors: 6
Main version: 15
Minor Version: 7601
Size of the dump file: 262 144
Dump of file time: 13/11/2014-18:35:49
====================================================================================================
Dump file: 110514-33540 - 01.dmp
Crash time: 11/05/2014-19:49:30
Bug Check String:
Bug check code: 0 x 00000124
Parameter 1: 00000000'00000000
Parameter 2: fffffa80'07f7e6c8
Parameter 3: 00000000'00000000
Parameter 4: 00000000'00000000
Caused by the driver: ntoskrnl.exe
Caused by the address: ntoskrnl.exe + 4adb5c
File description: NT kernel & system
Product name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File version: 6.1.7601.18526 (win7sp1_gdr.140706 - 1506)
CPU: x 64
Plant address: ntoskrnl.exe + 4adb5c
Stack address 1:
The stack address 2:
Address 3 the battery:
Computer name:
Full path: C:\Windows\Minidump\110514-33540-01.dmp
Number of processors: 6
Main version: 15
Minor Version: 7601
Size of the dump file: 262 144
Dump of file time: 11/05/2014-19:49:52
==================================================GT
Both have been BCC124 two materials
Stop 0 x 124 is a hardware errorIf you are overclocking try to reset your settings to standard processor and see if that helps.If you keep getting the BSOD here are things more than you may want.
This is usually hardware related, defective heat, memory or processor even if it is "possible" he is associated (rare) driver.
Stop 0 x 124 - what it means and what to try
Synopsis:
A "stop 0 x 124" is fundamentally different from many other types of bluescreens because it arises from a complaint of material.
Stop 0 x 124 minidumps contain very little concrete information, and it is therefore necessary to address the problem as a case of material in an unknown state of distress.Generic troubleshooting ' Stop 0 x 124 ":
1) to ensure that none of the hardware components are overclocked. Material which is pushed beyond its design specifications - by overclocking - may malfunction in unpredictable ways.
(2) ensure that the machine is sufficiently cooled.
If there is doubt, open the side of the case (be aware of all the relevant conditions guaranteed!) PC and direct an electric fan squarely to the motherboard. Who will rule on most cooling problems (lack of).
3) update all drivers related to materials: video, sound, RAID (if applicable), NIC... anything that interacts with a piece of hardware.
It is best to run the latest drivers anyway.
(4) update the BIOS of your motherboard according to the manufacturer's instructions and clear CMOS.
Their website should provide detailed instructions on the brand and model-specific procedure.
(5) rarely, bugs in the operating system may cause "false positives" 0 x 124 events where the hardware wasn't complaining, but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 does not have to suffer from a defect, but it is nevertheless important to keep Windows up-to-date.
6) trying (stress) test these hardware components that can be put to the test artificially.
The most obvious examples are the RAM and HDD (s).
For the RAM, use the 3 rd-party memtest86 utility to run several hours a test value. (6-8 passes to stress the ram)
For hard drives, verify if CHKDSK /R finds any problems on (s), including "bad sectors".
Unreliable RAM, in particular, is mortal, as well as software, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result the diagnostic utilities does not guarantee that the RAM is free of any defect - only that none have been encountered during the test passes.
7) as the last of the non-invasive troubleshooting steps, perform a "Vanilla" Windows reinstallation: just the OS itself without additional applications, games, utilities, updates, new drivers - or ANYTHING that does not come from the Windows 7 disc.
Who stops working mitigate the problem of the 0 x 124, jump to the next step.
If you run the "Vanilla" installation long enough to convince yourself that not a single 0 x 124 accident occurred, start installing applications and updates slowly, always stopping between successive additions long enough to get an idea of the question if the machine is still free of 0 x 124 breaks down.
Smash back, obviously the latest addition of software may be somehow connected to the root cause.
If the stop error 0 x 124 persist despite the above steps, and the equipment is under warranty, consider to go back and ask for a replacement that does not suffer periodic MCE events.
Be aware that want to perform the subsequent hardware troubleshooting steps can, in some cases, void your warranty:
(8) clean and carefully remove the dust inside the machine.
Reinstall all memory modules and connectors.
Use a can of compressed air to clean the RAM DIMM supports as much as possible.
(9) If all else fails, start removing items of hardware one by one in the hope that the culprit is something non-essential that can be eliminated.
Obviously, this type of testing is much easier if you have access to equivalent components in order to perform swaps.If you are in the situation to have completed all the steps above without a resolution of the symptom, unfortunately the most likely reason is that the error message is literally correct - something is fundamentally wrong with the hardware of the machine.
More advanced reading can be found here from a MS MVP IT PRO -
I get lots of BSOD. I installed "WhoCrashed" and analyze the dump files. Here's what he said:
Saturday, October 3, 14 17:29:30 GMT PM your computer crashed
crash dump file: C:\Windows\Minidump\031014-15147-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B80)
Bugcheck code: 0x4E (0 x 0x2007E, 0 x 2, 0 20075, 99)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that the page frame number (PFN) list is corrupted.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.I have this problem for a long time. I've updated the drivers, windows updates, no effect. But, for some reason, he did not seem since February. But Monday, I used MiniCygwin_GOptimize_v1.34.02 to compress files apk android. He uses a lot of CPU. And after that the BSOD began to reappear. I downloaded the Minidump file and Information System if someone wants to check.
Let me know the reason for these BSOD and how can I solve this problem.
Hello
We have many bug different controls:
PFN_LIST_CORRUPT (4th)
This indicates that the page frame number (PFN) list is corrupted.
This error is usually caused by a driver passing a list of descriptor of bad memory. For example, the pilot could call MmUnlockPages twice with the same list.
MEMORY_MANAGEMENT (1A)
This indicates that an error occurred serious memory management.
Error checking 1A, {5003, fffff780c0000000, 6933, 64ba0002d266}
-1 setting of the bug check is 5003 which lists free work is corrupt. It is probably a hardware error.
We also have another 1st parameter:
Error checking 1 a, {fffff6800005cf40, eab00001beb34867,403, fffff6fc00df59a0}
- Parameter 1 of the bug check is 403 which indicates the page table and NFPs are out of sync. It is also probably a clerical error.
^^ Pointed out that both of the above can still be caused by a driver causing corruption, but it is generally unlikely.
And another...
Error checking 1A, {41284, 159a0e001, 104 d 57, fffff70001080000}
-1 setting of the bug check is 41284 indicating a PTE or the fixed work list is corrupted.
BAD_POOL_HEADER (19)
This indicates that a pool header is corrupt.
Error checking 19, {20, fffff8a00b91df40, fffff8a00b91e020, 50e040c}
6: kd >! pool fffff8a00b91df40
Pool page fffff8a00b91df40 region is unknown
fffff8a00b91d000 size: 4 d 0 previous size: 0 Ntff (allocated)
fffff8a00b91d4d0 size: 30 size: 4 d 0 PfFK (allocated)
fffff8a00b91d500 size: 30 size: 30 PfFK (allocated)
fffff8a00b91d530 size: 10 previous size: 30 (free) NtfE
fffff8a00b91d540 size: 30 size: 10 Ntf0 (allocated)
fffff8a00b91d570 size: size previous 10:30 (free) Nbmc
fffff8a00b91d580 size: 40 previous size: 10 DxgK (allocated)
fffff8a00b91d5c0 size: c0 size previous: AfdX (protected) process (allocated) 40: fffffa801098c7f0
fffff8a00b91d680 size: 170 previous size: c0 MPsc (allocated)
fffff8a00b91d7f0 size: size previous c0: 170 FIcs (allocated)
fffff8a00b91d8b0 size: 40 size: c0 (allocated) NtFs
fffff8a00b91d8f0 size: 30 size: 40 (allocated) PfFK
fffff8a00b91d920 size: 30 size: 30 Ntf0 (allocated)
fffff8a00b91d950 size: 150 size: 30 FMfn (allocated)
fffff8a00b91daa0 size: size 160: 150 FMfn (allocated)
fffff8a00b91dc00 size: 40 size: 160 (allocated) MmSm
fffff8a00b91dc40 size: c0 size previous: 40 FIcs (allocated)
fffff8a00b91dd00 size: 10 size: c0 sect (free)
fffff8a00b91dd10 size: 170 previous size: 10 MPsc (allocated)
fffff8a00b91de80 size: size previous c0: 170 (allocated) NtFs
* fffff8a00b91df40 size: size previous e0: c0 (free) * FIcs
PoolTag FIcs: Context of FileInfo FS-Filter binary stream: fileinfo.sys^^ Block of pool who looked in the page pool belongs to the context of FileInfo FS-Filter flow. This is related to the file system.
6: kd >! poolval fffff8a00b91df40
Pool page fffff8a00b91df40 region is unknownValidation of the headers of pool the pool page: fffff8a00b91df40
[Fffff8a00b91d000] page pool is __inVALID.
System_service_exception (3B)
This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
This error has been linked to the excessive use of expanded memory and resulting from user mode graphics drivers enjambment and passing data incorrect of the kernel code.2: kd > fffff960000a874f ln
(fffff960'000 a 8720) win32k! NextOwnedWindow + 0x2f | (fffff960'000 a 8770) win32k! xxxRemoveDeleteMenuHelper^^ The exception is produced in win32k! NextOwnedWindow.
-----------------------
Overall, this looks like the faulty RAM. It's not like there is a foul-smelling waters driver causing memory corruption here, but it is possible. The reason I mention this is because I see it in the crash dumps after dumping the! v
OVERLAPPED_MODULE: Address overlap 'WinUsb' and 'ssudbus.sys'.
^^ WinUsb.sys - pilot class USB Windows system, it is a part of Windows. ssudbus.sys-
SAMSUNG USB Composite Device Driver. Probably a part of Samsung Kies. Uninstall everything that you can find this topic.
-----------------------
Please run Memtest for NOT LESS than 8 ~ (several hours):
Memtest86 +:
Download Memtest86 + here:
Which should I download?
You can either download the ISO pre-built you want to burn to a CD and then boot from the CD, or you can download the automatic installer of the USB. What this will do is format your USB drive, make a boot device and then install the necessary files. Both do the same job, it's just you that you choose, or you have available (be it CD or USB).
Note that some older generation motherboards do not support USB boot, your only option is CD (or floppy if you really wanted to).
How Memtest works:
Memtest86 writes a series of test patterns for most of the addresses of memory, reads the written data and compares it to find errors.
The default pass is 9 different tests, varying in the modes of access and test data. A tenth test, bland, is selectable in the menu. He wrote all the memory with zeros, then sleeps 90 minutes before checking to see if the bits have changed (perhaps because of refresh problems). This is repeated with all those for a total time of 3 hours by pass.
Many chipsets can report RAM speed and timings by SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclockee, Memtest86 can test that memory is free of error with these faster settings.
Some hardware is able to report the status of the "PAT" (PAT: active or PAT: disabled). This is a reference to the Intel performance acceleration technology; There may be the BIOS settings that affect this aspect of memory synchronization.
This information, if it is available for the program, can be displayed via a menu option.
Other questions, they can most likely be answered by reading this excellent guide here:
http://Forum.canardpc.com/threads/28864-FAQ-please-read-before-posting
Kind regards
Patrick
-
BSOD help (ntoskrnl.exe)
I recently built a new computer for the first time and I am constantly a BSOD. After consulting the minidump via the blue screen view files, it refers to the ntoskrnl.exe as the cause, but I suspect that maybe it's a corrupt driver (I could be wrong but). Due to my lack of experience on this subject, however, I have no idea on how to identify the guilty and so need help. As a result, I posted a link below containing the minidump files created by my computer and wish for some assistance on the interruption of information (any help would be greatly appreciated).
http://www.mediafire.com/download/khtsg34cxn75t41/minidump.zip
Thank you
WildThing0079Great, thank you very much.
We have various bug different controls:
PFN_LIST_CORRUPT (4th)
This indicates that the page frame number (PFN) list is corrupted.
This error is usually caused by a driver passing a list of descriptor of bad memory. For example, the pilot could call MmUnlockPages twice with the same list. However, this bug control seems as frequently when there is a defective material, most often RAM or HARD disk.
MEMORY_MANAGEMENT (1A)
This indicates that an error occurred serious memory management.
Error checking 1 a, {41287, 0, 0, 0}
-1 setting of the bug check is 41287 indicating an illegal page fault occurred while now fixed synchronization of work.
* Addition 41287, we have also the 1st parameter is 403 which indicates the table of page and NFPs are out of sync. It is probably a hardware error, although the device driver causing corruption is possible as well.
PAGE_FAULT_IN_NONPAGED_AREA (50)
This indicates that invalid system memory was referenced.
Bug control 0 x 50 usually occurs after the installation of a faulty hardware or installation failure of material (usually associated with defective RAM, either main memory, L2 RAM or RAM video cache).
Another common cause is a defective system service installation.
Antivirus software can also cause this error, as a corrupted NTFS volume can do him.
System_service_exception (3B)
This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
This error has been linked to the excessive use of expanded memory and resulting from user mode graphics drivers enjambment and passing data incorrect of the kernel code.-----------------------
1. AppleCharger.sys is listed and loaded, this is the driver GIGABYTE on / off Charge. See here for more information - http://www.gigabyte.us/MicroSite/185/on-off-charge.htm
He is well known to cause BSOD, so please delete it as soon as POSSIBLE.
2 even with gdrv.sys, which is the easy profit from Gigabyte - mobo utility power driver. Remove as soon as possible.
3 remove and reinstall Kaspersky with temporary Microsoft Security Essentials for troubleshooting purposes:
Kaspersky - remove http://support.Kaspersky.com/common/service.aspx?El=1464
MSE - http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download
Kind regards
Patrick
Maybe you are looking for
-
My books purchased on iPad are not available on iPhone
Hi guys,. I use mini iPad and iPhone 5 c. I downloaded a few hundred pounds of the iBooks app on my iPad for a few years and used to be able to open the books on my iPhone (I don't re - download, they appeared in the iBooks on the phone automatically
-
Firefox asks me if I want to save my password
I just bought a new computer, downloaded the latest firefox (did not import information from my old computer firefox yet), and although I've seen the guest waited to save a password when you enter a site once (I don't not saved it at the time), the p
-
Windows vitual PC / XPM on Satellite L30-105
Hello I'm running Windows 7 on my Satellite L30 - 105. And it works very well. Now I would like to install Windows Virtual PC to run Windows XP virtual Mode. But the laptophardware does not supporta virtual pc. Is there a solution for this problem? T
-
You can use NI 9237 for the LVDT readings
Dear comrades, I wonder if I can use NI 9237 and NI 9945 to get the reading of an LVDT. The interest is to measure the movement using Solartron DC Miniature LVDT. In our laboratory, we have NI 9237 and NI 9945 and I would get your advisor if it would
-
I get a message when trying to connect it says windows cannot access specified device.you may not have permissions appropriate to access them on my laptop