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
Run these two tests to check your memory and find which driver is causing the problem. Launch auditor. You don't need to run memtest again unless the auditor is not the cause, or you want to.
Tags: Windows
Similar Questions
-
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
-
Different random BSOD, ntoskrnl.exe
Hello
I am getting random BSOD in ntoskrnl.exe + 75c00Can occur at any time and not necessarily in charge. I tried testing my ram, hard drives to find errors & ran sfc/scannow without error.I downloaded the minidumps on skydrive @ https://skydrive.live.com/#cid=539E2424E35481DA&id=539E2424E35481DA%21105A big thank you to all those who can help.Brett
Two different causes. First and foremost your Kaspersky. I would like to delete and replace it with MSE
Kaspersky is a common cause of BSOD.
I remove and replace it with Microsoft Security Essentials at LEAST FOR TESTER.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.
-
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.
-
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 -
BSOD - Server 2008 R2 - ntoskrnl.exe
I had a problem recently with a BSOD that passes several times during the day. I newspapers DMP and used BlueScreenView to obtain some basic information (I know that it is also useful that it doesn't help) which seems to show that ntoskrnl.exe is at the origin of accidents. There are 6 Server, 1 is used by the LATTER and does not seem to have had this problem while the other 5 are part of a balanced load environment and have been seen this problem in some cases, 5 times a day. Here are the servers from RD.
The servers were all working perfectly well until our company has purchased and installed a piece of software called screwdriver. This software seems to be the cause of accidents and I contacted their support in this regard. But while I'm waiting I think it is perhaps a good idea to ask if the DMP files might actually provide more information as to what specifically is causing accidents.
For those who don't know, the screwdriver is a utility to help you with printing (printing from the Desktop server remotely to the workstation using the screwdriver driverless driver) and I wonder if there is a specific model of printer causing accidents or a driver side specific workstation or if its just one or a few users who cause accidents. Obviously BlueScreenView is not giving any information good but if the DMP file contains more information that might help I understand that it is worth looking into.
The BSOD error is below:
Signature of the problem:
Problem event name: BlueScreen
OS version: 6.1.7601.2.1.0.18.10
Locale ID: 1033
More information about the problem:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA801CCD9060
BCP3: FFFFFA801CCD9340
BCP4: FFFFF80001D85270
OS version: 6_1_7601
Service Pack: 1_0
Product: 18_3
Files helping to describe the problem:
C:\Windows\Minidump\112414-48500-01.dmp
C:\Users\***\AppData\Local\Temp\17\WER-2765148-0.SysData.XML
Read our privacy statement online:
http://go.Microsoft.com/fwlink/?LinkId=104288&clcid=0x0409
If the online privacy statement is not available, please read our offline privacy statement:
C:\Windows\system32\en-US\erofflps.txt
Any help is appreciated.
Thank you
Ryan
Ryan
You should also put this on Technet and I will increase it there as well.
-
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
-
I get the BSOD with f9 code and I do not understand what is? Could you please advice what may cause this? I'm not sure,
It happen when I stop or restart (15 minutes with him saying to stop) followed by BSOD (pilot State power failure).
Once I'm back I can see that Windows has recovered from unexpected shutdown down. Using BlueScreenView tells me that ntoskrnl.exe is the cause.
I was wondering if it has something to do with the USB Ports, because it won't work as a plug-and-Play (need to reboot USB is plugged).I reinstall all the USB drivers.
My system:
ASUS Z170A
nVIDIA GTX 980ti850 M2 OF EVO 250 GB SSD
Intel Core i7 - 4700 k
32 GB of RAM (4 sticks 8 GB)
Windows 7 64 bitAll up to date.
==================================================
Name of the file: ntoskrnl.exe
Address of stack: ntoskrnl.exe + e23f0
Address: Fffff800'0325e000
Address: Fffff800'03844000
Size: 0x005e6000
Time stamp: 0x5708972e
Time string: 09/04/2016 13:46:22
Product name: Microsoft® Windows® Operating System
File description: NT kernel & system
File version: 6.1.7601.23418 (win7sp1_ldr.160408 - 2045)
Company: Microsoft Corporation
Full path: C:\Windows\system32\ntoskrnl.exe
==================================================
==================================================
Dump file: 081316-13447 - 01.dmp
Crash time: 13/08/2016-12:46:05
Bug Check String: DRIVER_POWER_STATE_FAILURE
Bug check code: 0x0000009f
Parameter 1: 00000000'00000003
Parameter 2: fffffa80'1a0f1060
Parameter 3: fffff800'052373 d 8
Parameter 4: fffffa80'1f739c60
Caused by the driver: ntoskrnl.exe
Caused by the address: ntoskrnl.exe + 6f400
File description: NT kernel & system
Product name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File version: 6.1.7601.23418 (win7sp1_ldr.160408 - 2045)
CPU: x 64
Plant address: ntoskrnl.exe + 6f400
Stack address 1:
The stack address 2:
Address 3 the battery:
Computer name:
Full path: C:\Windows\Minidump\081316-13447-01.dmp
Number of processors: 8
Main version: 15
Minor Version: 7601
Size of the dump file: 1 250 528
Dump of file time: 13/08/2016-12:47
==================================================Hello
There is a possibility that there is a problem with a driver on your PC. Here are a few things to try:- If you know which driver is causing the problem, update.
- Make sure your hardware drivers are updated.
Please keep us updated.
Kind regards.
-
Serscan.sys ntoskrnl.exe BSOD
I started having BSOD pointing to ntoskrnl.exe and serscan.sys. Before the accident, the system gets very insensitive. The Task Manager displays all the information Resource Monitor gets even worse. When I reboot I get BSOD. After a few resets the system up live. I scanned for malware and found nothing. Antivirus shows as well clean. HD Tune says Spin Retry count slightly exceeds threshold and an unknown attribute of a same drive on another more transferred sector Count. There is more than one drive, but HD Tune does not show health is probably that it is 2 TB. It would then be memory or maybe something else? BSOD SkyDrive here
The accident was reported as being caused by DISK_HARDWARE_ERROR: a closer examination gives us a clue.
Process of own fffffa800b83b380 Image: RapportService
0: kd >! THREAD
GetPointerFromAddress: unable to read from fffff800036ff000
WIRE fffffa800a968640 Teb 13c8.1678 Cid: 00000000fff9e000 Win32Thread: 0000000000000000 PROCESSOR 0
Borrow not identity
GetUlongFromAddress: cannot read fffff8000363dbf0
Owning process fffffa800b83b380 Image: RapportService
Joint process s/o Image: n/a
fffff78000000000: cannot get shared data
Wait start TickCount 1985375You could do either of two things. Completely uninstall 'Trusteer report' and wait to see if the system crashes again, or you can force a crash by running the Driver Verifier, to help locate the faulty module, then post a link to the dump file here, resulting in the body of your next post.
Driver Verifier - stalking a bad driver to behave.
-
BSOD issue with ntoskrnl.exe
Hello friends,
IM currently having the BSOD "IRQL_NOT_LESS_OR_EQUAL" With Driver crash "ntoskrnl.exe" error
Here's the minidump file.
https://onedrive.live.com/redir?RESID=373FE6B42355D2CD! 1304 & authkey =! AMPX4Szxm7ffhyE & ithint = the file % 2cdmp
Specifications of the computer:
System manufacturer: BIOSTAR Group
System model: TZ68K +.Operating system: Windows 7 Home Premium 64 - bit (6.1, Build 7601) Service Pack 1
Card name: NVIDIA GeForce GTX 560
Processor: Intel Core i7 - 2600K CPU @ 3.40 GHz (8 CPUs), ~3.4GHz
BIOS: BIOS Date: 15/12/11 18:26:05 worm: 04.06.04
Very respectfully,.
AJ
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) -
BSOD on shutdown associated ntoskrnl.exe
Hello, today I got the BSOD when stop twice. I used the blue screen and it showed that this problem related to ntoskrnl.exe. I here enclose the direction in the dump file. Please help me solve this problem. https://onedrive.live.com/redir?RESID=7B7FCCC78623B4E2%21153
The unknown device below, is your laptop free fall sensor driver. Please install the driver using the link below.
[Peripheral problem]
Error code of device device PNP ID
Not available ACPI\SMO8810\1 the drivers for this device are not installed.ST Microelectronics free fall sensor driver.
Uninstall Bitdefender, using the uninstall program following the link. Install Microsoft Security Essentials, at least temporarily, until what stabilize us your system.
Uninstall tools for Bitdefender products.
http://www.BitDefender.com/uninstall/
Microsoft Security Essentials.
http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download
Then,.
You sometimes have a GoFlex, FreeAgent or OneTouch Seagate external drive attached to this system. Please make sure that the drivers for this device are installed correctly, if you do.
Installing software FreeAgent GoFlex, or OneTouch does not start automatically in Windows.
-
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
Maybe you are looking for
-
When I press on toward the bottom in the lower left corner of the screen of my iPhone 6 it made a poping sound. I think to send my phone to Apple. How much would it cost to to drop? And is there a way for me to fix it myself? Initially, I posted this
-
I tried to re-indexing and dragging, but nothing happens. I also tried tweaking permissions, removing .txt in the apple loops index file - as other solutions I've read in the Apple community, but still no loops in the browser. Someone had this proble
-
It's been a year I am using Lenovo p500. It works fine, but recently, the start was very slow. Sometimes it takes about 3-4 minutes. Is it possible to improvise the performance? "Bios Update" help the problem?
-
VI main and void / execution of vi
I'm fighting a lot with my hand vi and Subvi execution problems a lot! I have a complicated system. To explain this, I create a simple main vi and 2 subvis. Please take a look at the attachment. It works as expected. The Boolean button in main vi is
-
An error has occurred by ejecting ' DVD RW drive (e :))
When I try to burn a disc from a file, the burn starts and then freezes.As I try to eject the disc, nothing happens except the above Windows error.Can anyone help? Brian