KMODE_EXCEPTION_NOT_HANDLED in Windows 8.1
I recently downloaded an official copy of Windows 8.1 from my school's official Dreamspark partnership. After installing Windows 8.1 and following the steps fully I had no issues for about half a day, however after I put my MacBook Pro to sleep I could not "awaken" my MacBook Pro. I know the computer is still on since the caps lock LED still turns on/off but my screen is entirely blank. I've tried restarting my MacBook Pro several times and it will load Boot Camp but once it enters Window's circular dot loading screen it will "load" for a couple of seconds then flash a grey screen then go to a black screen. I've only gotten it to show KMODE_EXCEPTION_NOT_HANDLED once but aside from that every other restart will result in the same black screen. There is nothing wrong with my version of OS X Yosemite though, as that is my main partition so every restart will automatically load into OS X.
As of now, I have found that if I have Boot Camp use Windows 8.1 as it's main partition, then it seems to have no issues running. However, I am uncertain about the stability of running Windows as my primary OS and I only use Windows only to run a single of Windows-only program (Altera Quartus).
My specs are:
MacBook Pro with Retina (late 2013)
Intel Core i7 @ 2.80 Ghz
8.00 GB RAM
512 GB SSD
OS X Yosemite
it's actually looking for an executable file... so what you can do is to install the linksys wlan monitor first...
if you want you can download the updated driver from the website, uninstall everything first on your computer.. reinstall the adapter starting from the software. just explore the file then open the utility folder and double click on set-up and follow through the installation process...
after installing, the computer will prompt you to restart the PC, just restart the PC, it will prompt you with a found new hardware installtion window.. just click next until finish... it should be fixed
"a helping hand in a community makes the world a universe"
Similar Messages
-
Windows 7 Blue Screen - Random Shut Down
I'm having problem with my Toshiba Satellite L505 which randomly shows a blue screen prior to shutting down and restarting. I have use my system recovery disk to return my computer back to it's original state. The computer worked fine for a couple of month but has crashed again. Below is a sample of the blue screen messages prior to shutting down:
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
KMODE_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x0000001e (0xffffffffc0000005, 0xfffff800032a526b, 0x0000000000000000,
0x000000007efa0000)
*** ntoskrnl.exe - Address 0xfffff800032c4c40 base at 0xfffff8000324f000 DateStamp
0x50e79935
2nd blue screen crash message
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: PCIIDEX.SYS
KMODE_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x0000001e (0xffffffffc0000005, 0xfffff800033c6cda, 0x0000000000000001,
0x0000000000000018)
*** PCIIDEX.SYS - Address 0xfffff88000e879d4 base at 0xfffff88000e86000 DateStamp
0x4a5bc114
Does anyone know what this means and would be able to help.Hiya
Run a full computer scan with your antivirus software. virus Backdoor.NTHack. may be the problem, and it runs Dl.bat in folder InetPub\Scripts.When you boot up the computer, go to task menager (CTRL+ALT+Delete), look if you have this runned: Firedaemon.exe, Sud.exe, Os2srv.exe, Mmtask.exe.
2. If you have a CARD READER than go to bios "Integrated Peripherals" and set Legacy USB storage detect to DISABLED
Let me know if you get any more problems -
Windows 8.1 crashing/rebooting
My windows 8.1 is rebooting multiple times per day. I've uploaded all the dmp files to my skydrive.
Here's the output/report for WhoCrashed. I'm not sure how to troubleshoot from here.
computer name:
P6X58D-FLL
windows version: Windows 8 , 6.2, build: 9200
windows dir:
C:\Windows
Hardware: ASUSTeK Computer INC., P6X58D PREMIUM
CPU:
GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz Intel586, level: 6
8
logical processors, active mask: 255
RAM: 12875546624 total
VM:
2147352576, free: 1922887680
Crash Dump Analysis
Crash dump
directory: C:\Windows\Minidump
Crash dumps are enabled on your
computer.
On
Tue 2/11/2014 7:05:24 AM GMT your computer crashed
crash dump file:
C:\Windows\Minidump\021114-6703-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1A
(0x41287, 0x76C55701, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path:
C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &
System
Bug check description: This indicates that a severe memory management
error occurred.
This might be a case of memory corruption. More often memory
corruption happens because of software errors in buggy drivers, not because of
faulty RAM modules.
The crash took place in the Windows kernel. Possibly
this problem is caused by another driver that cannot be identified at this time.
On
Tue 2/11/2014 7:05:24 AM GMT 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:
0x1A (0x41287, 0x76C55701, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This
indicates that a severe memory management error occurred.
This might be a
case of memory corruption. More often memory corruption happens because of
software errors in buggy drivers, not because of faulty RAM modules.
The
crash took place in the Windows kernel. Possibly this problem is caused by
another driver that cannot be identified at this time.
On
Mon 2/10/2014 10:56:58 PM GMT your computer crashed
crash dump file:
C:\Windows\Minidump\021014-5953-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B
(0xC0000005, 0xFFFFF80164C5A430, 0xFFFFD00023127FC0, 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 check description: This indicates that an exception happened while
executing a routine that transitions from non-privileged code to privileged
code.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver that cannot be identified at
this time.
On Mon 2/10/2014 10:27:14 PM GMT your computer
crashed
crash dump file: C:\Windows\Minidump\021014-6234-01.dmp
This
was probably caused by the following module:
ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x20001
(0x11, 0x220FBC, 0x1005, 0xFFFFE80005268B20)
Error: HYPERVISOR_ERROR
file path:
C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &
System
Bug check description: The hypervisor has encountered a fatal
error.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver that cannot be identified at this time.
On
Sat 2/8/2014 6:49:56 PM GMT your computer crashed
crash dump file:
C:\Windows\Minidump\020814-6140-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xA
(0xFFFFFA7FFFFFFFD0, 0x2, 0x0, 0xFFFFF800CDBA353D)
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 check description: This indicates that Microsoft Windows or a
kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This
appears to be a typical software driver bug and is not likely to be caused by a
hardware problem.
The crash took place in the Windows kernel. Possibly this
problem is caused by another driver that cannot be identified at this time.
On
Fri 2/7/2014 3:23:35 PM GMT your computer crashed
crash dump file:
C:\Windows\Minidump\020714-6171-01.dmp
This was probably caused by the
following module: usbport.sys (USBPORT+0x14B5)
Bugcheck code: 0x1E
(0xFFFFFFFFC0000005, 0xFFFFF80002AAB4B5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error:
KMODE_EXCEPTION_NOT_HANDLED
file path:
C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0
Port Driver
Bug check description: This indicates that a kernel-mode program
generated an exception which the error handler did not catch.
This appears to
be a typical software driver bug and is not likely to be caused by a hardware
problem.
The crash took place in a standard Microsoft module. Your system
configuration may be incorrect. Possibly this problem is caused by another
driver on your system that cannot be identified at this time.
On
Thu 2/6/2014 4:51:43 PM GMT your computer crashed
crash dump file:
C:\Windows\Minidump\020614-6984-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B
(0xC0000005, 0xFFFFF803AE557929, 0xFFFFD00028C58AA0, 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 check description: This indicates that an exception happened while
executing a routine that transitions from non-privileged code to privileged
code.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver that cannot be identified at
this time.
On Sat 1/25/2014 12:43:17 PM GMT your computer
crashed
crash dump file: C:\Windows\Minidump\012514-6031-01.dmp
This
was probably caused by the following module:
ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1A
(0x8886, 0xFFFFFA80073DCC70, 0xFFFFFA8006D1E3E0, 0x201)
Error: MEMORY_MANAGEMENT
file path:
C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &
System
Bug check description: This indicates that a severe memory management
error occurred.
This might be a case of memory corruption. More often memory
corruption happens because of software errors in buggy drivers, not because of
faulty RAM modules.
The crash took place in the Windows kernel. Possibly
this problem is caused by another driver that cannot be identified at this time.
On
Fri 1/24/2014 4:38:48 PM GMT your computer crashed
crash dump file:
C:\Windows\Minidump\012414-8156-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E
(0xFFFFFFFFC000001D, 0xFFFFF800F5E676A7, 0xFFFFE0000A0A2880, 0x0)
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 check description: This indicates that a kernel-mode program
generated an exception which the error handler did not catch.
This appears to
be a typical software driver bug and is not likely to be caused by a hardware
problem.
The crash took place in the Windows kernel. Possibly this problem
is caused by another driver that cannot be identified at this time.
On
Sun 1/12/2014 9:50:53 AM GMT your computer crashed
crash dump file:
C:\Windows\Minidump\011214-6531-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1A
(0x3300, 0xFFFFC00003CD9000, 0xC080000015C17963, 0x0)
Error: MEMORY_MANAGEMENT
file path:
C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &
System
Bug check description: This indicates that a severe memory management
error occurred.
This might be a case of memory corruption. More often memory
corruption happens because of software errors in buggy drivers, not because of
faulty RAM modules.
The crash took place in the Windows kernel. Possibly
this problem is caused by another driver that cannot be identified at this time.
Conclusion
11 crash dumps
have been found and analyzed. Only 10 are included in this report. No offending
third party drivers have been found. Consider using WhoCrashed Professional
which offers more detailed analysis using symbol resolution. Also configuring
your system to produce a full memory dump may help you.
Read the
topic
general suggestions for troubleshooting system crashes for
more information.
Note that it's not always possible to state with
certainty whether a reported driver is actually responsible for crashing your
system or that the root cause is in another module. Nonetheless it's suggested
you look for updates for the products that these drivers belong to and regularly
visit Windows update or enable automatic updates for Windows. In case a piece of
malfunctioning hardware is causing trouble, a search with Google on the bug
check errors together with the model name and brand of your computer may help
you investigate this further.We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
We prefer at least 2 DMP files to spot trends and confirm the cause.
Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
If you have any questions about the procedure please ask
Wanikiya and Dyami--Team Zigzag -
Blue Screen of Death of multiple Windows Multipoint Servers at the same time in NUServer64.sys
Hi, we are running
Windows MultiPoint Server 2011 on 4 Dell 9010 machines and 45 Wyse E02 clients connected by 4 switches. Every week we got 2 or 3 random BSoD for all servers at the same time. Memory dump for server 2,3,4 show that the exception is from NUServer64.sys.
Please check below for the system event logs and memory dump analysis output. Any help would be appreciated!
server1:
Warning 11/17/2013 8:55:52 PM
e1cexpress 27
None
Critical 11/17/2013 8:55:48 PM
Kernel-Power 41
(63)
Error 11/17/2013 8:56:08 PM
BugCheck 1001
None
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0x0000000000000000, 0x0000000000000008, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111813-19765-01.
Error 11/17/2013 8:56:03 PM
EventLog 6008
None
The previous system shutdown at 12:53:40 on 2013/11/18 was unexpected.
Error 11/17/2013 6:55:49 PM
Disk 11
None
The driver detected a controller error on \Device\Harddisk2\DR2.
Error 11/17/2013 6:55:48 PM
Disk 11
None
The driver detected a controller error on \Device\Harddisk2\DR2.
Warning 11/17/2013 3:42:08 PM
Microsoft-Windows-TerminalServices-Licensing
18 None
server2:
Warning 11/17/2013 8:55:39 PM
e1cexpress 27
None
Critical 11/17/2013 8:55:31 PM
Kernel-Power 41
(63)
Error 11/17/2013 8:55:52 PM
BugCheck 1001
None
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80002c80166, 0xfffff880023397e8, 0xfffff88002339040). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111813-17518-01.
Error 11/17/2013 8:55:44 PM
EventLog 6008
None
The previous system shutdown at 12:53:53 on 2013/11/18 was unexpected.
Warning 11/17/2013 7:16:07 PM
NUServer64 3
None
server3:
Warning 11/17/2013 8:55:38 PM
Microsoft-Windows-TerminalServices-Licensing
18 None
Error 11/17/2013 8:55:31 PM
BugCheck 1001
None
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x000000000000009a, 0x0000000000417c94, 0x0000000000000006, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111813-9937-01.
Warning 11/17/2013 8:55:24 PM
e1cexpress 27
None
Critical 11/17/2013 8:55:21 PM
Kernel-Power 41
(63)
Error 11/17/2013 8:55:27 PM
EventLog 6008
None
The previous system shutdown at 12:53:49 on 2013/11/18 was unexpected.
server4:
Warning 11/17/2013 8:55:33 PM
Microsoft-Windows-TerminalServices-Licensing
18 None
Warning 11/17/2013 8:55:09 PM
e1cexpress 27
None
Critical 11/17/2013 8:55:05 PM
Kernel-Power 41
(63)
Error 11/17/2013 8:55:25 PM
BugCheck 1001
None
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000100000001, 0x0000000000000002, 0x0000000000000001, 0xfffff8000328abe6). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111813-14055-01.
Error 11/17/2013 8:55:14 PM
EventLog 6008
None
The previous system shutdown at 12:53:21 on 2013/11/18 was unexpected.
Error 11/17/2013 8:51:47 PM
NUServer64 4
None
\Device\NUServer_995D6600
<995D6600_3> Disconnect fail.
Error 11/17/2013 8:51:47 PM
NUServer64 4
None
\Device\NUServer_995D6600
<995D6600_3> Connect fail.
Warning 11/17/2013 8:51:47 PM
NUServer64 3
None
\Device\NUServer_995D6600
<995D6600_3> Connect time-out.
Warning 11/17/2013 8:50:00 PM
NUServer64 3
None
\Device\NUServer_995B9000
<995B9000_3> Hi-Perf socket active clear.
Error 11/17/2013 8:49:25 PM
NUServer64 4
None
\Device\NUServer_995D6600
<995D6600_3> Disconnect fail.
Error 11/17/2013 8:49:25 PM
NUServer64 4
None
\Device\NUServer_995D6600
<995D6600_3> Connect fail.
Warning 11/17/2013 8:49:25 PM
NUServer64 3
None
\Device\NUServer_995D6600
<995D6600_3> Connect time-out.Memory dumps:
server1:
2: kd> !analyze -v
* Bugcheck Analysis *
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+3031623733386137
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000008
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: 0000000000000000
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR: 0x1E_c0000005
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800c744860 -- (.trap 0xfffff8800c744860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff8800c7449f0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000f44 r10=fffff80003602000
r11=0000000000000358 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
00000000`00000000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800036c2738 to fffff80003677bc0
STACK_TEXT:
fffff880`0c743fd8 fffff800`036c2738 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
fffff880`0c743fe0 fffff800`03677242 : fffff880`0c7447b8 00000000`00000030 fffff880`0c744860 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`0c744680 fffff800`03675dba : 00000000`00000008 00000000`00000000 00000009`00000000 00000000`00000030 : nt!KiExceptionDispatch+0xc2
fffff880`0c744860 00000000`00000000 : 00000000`00000030 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+487ed
fffff800`036c2738 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+487ed
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035
FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+487ed
BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+487ed
Followup: MachineOwner
server2:
0: kd> !analyze -v
* Bugcheck Analysis *
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c80166, The address that the exception occurred at
Arg3: fffff880023397e8, Exception Record Address
Arg4: fffff88002339040, Context Record Address
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!KeSetEvent+16
fffff800`02c80166 f6037f test byte ptr [rbx],7Fh
EXCEPTION_RECORD: fffff880023397e8 -- (.exr 0xfffff880023397e8)
ExceptionAddress: fffff80002c80166 (nt!KeSetEvent+0x0000000000000016)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000010f7f0a50
Attempt to read from address 000000010f7f0a50
CONTEXT: fffff88002339040 -- (.cxr 0xfffff88002339040)
rax=0000000000000000 rbx=000000010f7f0a50 rcx=0000000000000001
rdx=0000000000000000 rsi=fffffa800f7ec050 rdi=fffffa800f7ec1a0
rip=fffff80002c80166 rsp=fffff88002339a20 rbp=000000010f7f0a50
r8=0000000000000000 r9=0000000000000150 r10=fffff80002c06000
r11=fffff88002339a30 r12=0000000000000000 r13=fffffa800de82220
r14=fffffa800f7f0ae0 r15=0000000000000002
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!KeSetEvent+0x16:
fffff800`02c80166 f6037f test byte ptr [rbx],7Fh ds:002b:00000001`0f7f0a50=??
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 000000010f7f0a50
READ_ADDRESS: 000000010f7f0a50
FOLLOWUP_IP:
NUServer64+65f1
fffff880`0ab8c5f1 488b6c2448 mov rbp,qword ptr [rsp+48h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8800ab8c5f1 to fffff80002c80166
STACK_TEXT:
fffff880`02339a20 fffff880`0ab8c5f1 : 00000000`000003f0 00000001`00000000 fffffa80`0f7ec000 00000000`00000500 : nt!KeSetEvent+0x16
fffff880`02339a90 fffff880`0ab8c8aa : fffffa80`0f7ec1a0 fffffa80`0f7eeb0c fffffa80`0f7ee2c8 00000000`00000002 : NUServer64+0x65f1
fffff880`02339ad0 fffff800`02f721d3 : fffffa80`0f7f0ae0 fffffa80`0f7ec260 fffffa80`0f7ec050 fffffa80`0c72e040 : NUServer64+0x68aa
fffff880`02339b40 fffff800`02c85261 : fffff800`02e21200 fffff800`02f72101 fffffa80`0c72e000 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`02339b70 fffff800`02f182ea : 501a7d4d`a14dcd79 fffffa80`0c72e040 00000000`00000080 fffffa80`0c70b6f0 : nt!ExpWorkerThread+0x111
fffff880`02339c00 fffff800`02c6c8e6 : fffff880`01f42180 fffffa80`0c72e040 fffff880`01f4d0c0 9ae0ec34`00b81aae : nt!PspSystemThreadStartup+0x5a
fffff880`02339c40 00000000`00000000 : fffff880`0233a000 fffff880`02334000 fffff880`02339370 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: NUServer64+65f1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NUServer64
IMAGE_NAME: NUServer64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f66a064
STACK_COMMAND: .cxr 0xfffff88002339040 ; kb
FAILURE_BUCKET_ID: X64_0x7E_NUServer64+65f1
BUCKET_ID: X64_0x7E_NUServer64+65f1
Followup: MachineOwner
server3:
0: kd> !analyze -v
* Bugcheck Analysis *
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 000000000000009a,
Arg2: 0000000000417c94
Arg3: 0000000000000006
Arg4: 0000000000000002
Debugging Details:
BUGCHECK_STR: 0x4E_9a
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002d629ef to fffff80002cd3bc0
STACK_TEXT:
fffff880`14417968 fffff800`02d629ef : 00000000`0000004e 00000000`0000009a 00000000`00417c94 00000000`00000006 : nt!KeBugCheckEx
fffff880`14417970 fffff800`02e0403b : fffff880`14417a08 fffffa80`10cd1b88 fffff880`144179e0 00000000`000005a0 : nt!MiBadRefCount+0x4f
fffff880`144179b0 fffff800`02e078a7 : fffffa80`12894000 00000000`00000000 fffff6fb`7ea004a0 fffff800`00000001 : nt!MiFreePoolPages+0xa8b
fffff880`14417ac0 fffff880`0ad8d07a : 00000000`00000003 fffffa80`0f4471a0 fffffa80`36747345 fffffa80`00000000 : nt!ExFreePoolWithTag+0x7c7
fffff880`14417b70 fffff800`02f702ea : fffffa80`10cd1a80 00000000`00000080 fffffa80`0c70a740 003f005c`005c0000 : NUServer64+0x1707a
fffff880`14417c00 fffff800`02cc48e6 : fffff800`02e4ee80 fffffa80`10cd1a80 fffff800`02e5ccc0 00310026`00330023 : nt!PspSystemThreadStartup+0x5a
fffff880`14417c40 00000000`00000000 : fffff880`14418000 fffff880`14412000 fffff880`144174b0 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
NUServer64+1707a
fffff880`0ad8d07a 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: NUServer64+1707a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NUServer64
IMAGE_NAME: NUServer64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f66a064
FAILURE_BUCKET_ID: X64_0x4E_9a_NUServer64+1707a
BUCKET_ID: X64_0x4E_9a_NUServer64+1707a
Followup: MachineOwner -
Blue Screen Of Death on Windows 7 64bit
Hi, My computer crashing again after update some windows update, I updated almost all the drivers but still
got problem. Below is my dump file.
https://www.dropbox.com/s/0wak2x4mkrg3zd3/miniDump.zip
any help would be much appreciated!
Regards,
VyHi,
The latest attached DMP file is of the KMODE_EXCEPTION_NOT_HANDLED (1e) bug check.
This indicates that a kernel-mode program generated an exception which the error handler did not catch.
1: kd> k
Child-SP RetAddr Call Site
fffff880`03119fb8 fffff800`0346d5be nt!KeBugCheck
fffff880`03119fc0 fffff800`034a075d nt!KiKernelCalloutExceptionHandler+0xe
fffff880`03119ff0 fffff800`0349f535 nt!RtlpExecuteHandlerForException+0xd
fffff880`0311a020 fffff800`034b04c1 nt!RtlDispatchException+0x415
fffff880`0311a700 fffff800`03475242 nt!KiDispatchException+0x135
fffff880`0311ada0 fffff800`03473dba nt!KiExceptionDispatch+0xc2
fffff880`0311af80 fffff800`035aa1e7 nt!KiPageFault+0x23a
fffff880`0311b110 fffff880`054884c0 nt!ExAllocatePoolWithTag+0x5d7
fffff880`0311b200 fffff880`05484645 usbccgp!UsbcIncrementPendingCount+0x60
fffff880`0311b250 fffff880`0548497e usbccgp!DispatchPdoUrb+0x69
fffff880`0311b290 fffff880`0548272e usbccgp!DispatchPdoInternalDeviceControl+0x17a
fffff880`0311b2c0 fffff880`0252e967 usbccgp!USBC_Dispatch+0x2de
fffff880`0311b340 fffffa80`0f8081f0 SAlpham64+0x2967
fffff880`0311b348 fffffa80`0f824201 0xfffffa80`0f8081f0
fffff880`0311b350 00000000`00000000 0xfffffa80`0f824201
SAlpham64.sys is the SteelSeries Engine HID driver, it's causing an exception.
1. Update your SteelSeries drivers ASAP -
http://steelseries.com/support/downloads
2. Uninstall ISO Drive ASAP.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama -
Windows Update Crashing my Tablet
I have a Samsung Ativ that I have had problems with since I got it. I get the "KMODE_EXCEPTION_NOT_HANDLED "
error when I update the tablet. I was able to get it into Windows 8.1 but I can't plug it in and run windows without the error. I am on my fifth time of refreshing the tablet and I am down to 19 updates and not sure which update my tablet
doesn't like. Help!Hi,
Please know that this update is to revoke noncompliant UEFI boot loader modules.
To avoid the issue of crashing your system, we recommend that you apply this update after you remove noncompliant UEFI modules from your system to make sure that the system can successfully start, and consider upgrading to compliant UEFI modules if they
are available.
Detailed information, you can refer to this KB article:
Microsoft security advisory: Update to revoke noncompliant UEFI boot loader modules
http://support.microsoft.com/kb/2871690
Kate Li
TechNet Community Support -
Surface Pro 3 BSOD KMODE_EXCEPTION_NOT_HANDLED mrxsmb20.sys
Hi
Have been having repeated BSOD's on my vanilla Surface Pro 3 i5 256 GB:
KMODE_EXCEPTION_NOT_HANDLED mrxsmb20.sys
They only appear to happen when I am on the docking station.
I have done a clean "Recovery" from preserving user files once, and most recently a clean recovery of the device.
Windows Updates have been installed, and the November driver pack was downloaded (today) and installed for good measure.
I am using BlueScreenView from NirSoft but I can't see any other driver that might be causing the problem.
Advice much appreciated.
Thanks
DavidHi Hunter Group ,
I wonder if there is any luck that this issue has been resolved.
According to your description, please tell us dose this issue persist after you installed all updates of November packs?
Please make sure you have installed last update of your surface firmware for good measure:
https://www.microsoft.com/en-in/download/details.aspx?id=38826
In most cases, you will experience mrxsmb20.sys blue screen errors after you’ve installed new hardware or software.
Mrxsmb20.sys blue screen errors can be caused by a variety of hardware, firmware, driver, or software issues such like
Incorrectly configured, corrupted Windows device drivers, Virus or malware infection, hardware related to mrxsmb20.sys, Damaged or removed system files, damaged hard disk and memory (RAM) corruption.
Since this issue can be caused by installed third party software, the first thing to do is perform a clean boot see if the issue disappears.
Then You could conduct a Full Malware Scan of Your PC and run Windows System File Checker ("Dism /Online /Cleanup-Image /RestoreHealth") in Command Prompt with administrator permission. If no Virus or malware infection and the
Component Integrity is fine. Please check for Hard Drive Corruption ("chkdsk /f").
How to run “chkdsk” (Windows XP, Vista, 7, and 8):
1. Click the Start button.
2. Type "cmd" in the search box... hit ENTER
3. A black box will open with a blinking cursor.
4. Type "chkdsk /f" and hit ENTER.
5."chkdsk" will begin scanning for hard disk corruption that could be causing mrxsmb20.sys STOP errors.
6. Follow the on-screen commands.
If the issue persists you could check or upload your DMP log to help us find corrupt or incompatible drivers or where the memory corruption happens.
About more information about “Dism /Online /Cleanup-Image /RestoreHealth”:
http://technet.microsoft.com/en-us/library/hh824869.aspx
Regards -
Windows 8.1 Pro Bluescreen on Asus K53SC I bought on Amazon for 3D Modeling.
I got this Asus K53SC with an Intel Core i5 and a dedicated GeForce 520MX with Optimus. New Hard Drive with Fresh Windows 8.1 Pro Install. The problem is that even with Windows 7 Professional it would give me a Blue screen. I downloaded a Blue screen Viewer
and got this info from the dmp. Any help since I don't want to mess around opening it just to make sure it is a hardware issue, Thanks in advance.
==================================================
Dump File : 052114-22203-01.dmp
Crash Time : 5/21/2014 7:14:23 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff800`7d78d207
Parameter 3 : ffffd000`4710c2c0
Parameter 4 : 0000000d`0f2ba272
Caused By Driver : intelppm.sys
Caused By Address : intelppm.sys+2207
File Description : Processor Device Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.16384 (winblue_rtm.130821-1623)
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052114-22203-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 294,088
Dump File Time : 5/21/2014 7:15:36 AM
==================================================
==================================================
Dump File : 052114-40250-01.dmp
Crash Time : 5/21/2014 7:06:30 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff801`e9dbd207
Parameter 3 : ffffd000`5e7b22c0
Parameter 4 : 000001e1`1a75320b
Caused By Driver : intelppm.sys
Caused By Address : intelppm.sys+2207
File Description : Processor Device Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.16384 (winblue_rtm.130821-1623)
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052114-40250-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 297,696
Dump File Time : 5/21/2014 7:11:31 AM
==================================================
==================================================
Dump File : 052114-32203-01.dmp
Crash Time : 5/21/2014 5:56:58 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff800`5dfae207
Parameter 3 : ffffd001`dd10c2c0
Parameter 4 : 00000372`923eee4d
Caused By Driver : intelppm.sys
Caused By Address : intelppm.sys+2207
File Description : Processor Device Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.16384 (winblue_rtm.130821-1623)
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052114-32203-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 303,168
Dump File Time : 5/21/2014 6:23:56 AM
==================================================
==================================================
Dump File : 052114-22468-01.dmp
Crash Time : 5/21/2014 3:29:55 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000096
Parameter 2 : fffff801`16dcd240
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : intelppm.sys
Caused By Address : intelppm.sys+2240
File Description : Processor Device Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.16384 (winblue_rtm.130821-1623)
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052114-22468-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 286,752
Dump File Time : 5/21/2014 3:31:48 AM
==================================================
==================================================
Dump File : 052114-25531-01.dmp
Crash Time : 5/21/2014 12:02:04 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff800`b99a1207
Parameter 3 : fffff802`49561a00
Parameter 4 : 00000041`21c68e88
Caused By Driver : intelppm.sys
Caused By Address : intelppm.sys+2207
File Description : Processor Device Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.16384 (winblue_rtm.130821-1623)
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052114-25531-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 286,808
Dump File Time : 5/21/2014 12:03:04 AM
==================================================
==================================================
Dump File : 052014-36562-01.dmp
Crash Time : 5/20/2014 11:32:21 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff800`f2b69207
Parameter 3 : ffffd001`c39b22c0
Parameter 4 : 00000218`cca47f3e
Caused By Driver : intelppm.sys
Caused By Address : intelppm.sys+2207
File Description : Processor Device Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.16384 (winblue_rtm.130821-1623)
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052014-36562-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 298,872
Dump File Time : 5/20/2014 11:34:00 PM
==================================================
==================================================
Dump File : 052014-28484-01.dmp
Crash Time : 5/20/2014 9:46:02 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff800`52e8a207
Parameter 3 : fffff800`24f53a00
Parameter 4 : 00000007`b9324414
Caused By Driver : intelppm.sys
Caused By Address : intelppm.sys+2207
File Description : Processor Device Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.16384 (winblue_rtm.130821-1623)
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052014-28484-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 295,416
Dump File Time : 5/20/2014 9:47:20 PM
==================================================
==================================================
Dump File : 051814-82281-01.dmp
Crash Time : 5/18/2014 11:14:03 AM
Bug Check String :
Bug Check Code : 0x00020001
Parameter 1 : 00000000`00000011
Parameter 2 : 00000000`0026b139
Parameter 3 : 00000000`00001003
Parameter 4 : ffffe800`05220de0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+153fa0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.17041 (winblue_gdr.140305-1710)
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\051814-82281-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 324,352
Dump File Time : 5/18/2014 11:24:45 AM
==================================================
==================================================
Dump File : 050714-28531-01.dmp
Crash Time : 5/7/2014 6:54:15 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff800`029ad207
Parameter 3 : ffffd000`201fb240
Parameter 4 : 00000029`e1993ac5
Caused By Driver : intelppm.sys
Caused By Address : intelppm.sys+2207
File Description : Processor Device Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.16384 (winblue_rtm.130821-1623)
Processor : x64
Crash Address : ntoskrnl.exe+14dca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\050714-28531-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 282,376
Dump File Time : 5/7/2014 6:55:19 PM
==================================================intelppm.sys is intel processor driver or chipset driver
I suggest go to intel site and autodetect if there is updated driver for your PC
but its seems odd, when I check at Asus site, there is no specific driver for Windows 8.1 for this model. I suggest you contact Asus as well regarding this Windows 8.1 installed in your PC
tips: don't use more than 1 antivirus, MSE good enough for Windows8.1
remove or disable temporary tools like deamon tools or any HDD virtualization -
BSOD in Win 10 build 9879 is with bug check 0x1e. Wof.sys is a file that is in Win 8.1. HP g7-1310us (refurbished) laptop has been having BSOD's even when it had Win 7 installed. Checked RAM, hardware, and SATA disk but there is no specific lead to why BSOD's
happen routinely. Interestingly, there were no problems while this laptop was running Ubuntu 14. Any details on what Windows Overlay Filter driver named wof.sys does? Also, could this error be caused by faulty CPU? It has an Intel i3-2350M CPU @2.3Ghz, x64
based processor.
==================================================
Dump File : 121114-22984-01.dmp
Crash Time : 12/11/2014 5:23:05 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000008
Parameter 4 : 00000000`00000000
Caused By Driver : Wof.sys
Caused By Address : Wof.sys+1e40
File Description : Windows Overlay Filter
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.4.9879.0 (fbl_release.141103-1722)
Processor : x64
Crash Address : ntoskrnl.exe+161109
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\121114-22984-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9879
Dump File Size : 282,776
Dump File Time : 12/11/2014 5:26:16 PM
==================================================
Gilda SanchezHere is the CPU data:
Intel(R) Processor Identification Utility
Version: 5.01.20140910
Time Stamp: 2014/12/11 19:28:20
Operating System: 6.2-9200-
Number of processors in system: 1
Current processor: #1
Active cores per processor: 2
Disabled cores per processor: 0
Processor Name: Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz
Type: 0
Family: 6
Model: 2A
Stepping: 7
Revision: 29
Maximum CPUID Level: D
L1 Instruction Cache: 2 x 32 KB
L1 Data Cache: 2 x 32 KB
L2 Cache: 2 x 256 KB
L3 Cache: 3 MB
Packaging: µPGA/BGA
Enhanced Intel SpeedStep(R) Technology: Yes
MMX(TM): Yes
Intel(R) SSE: Yes
Intel(R) SSE2: Yes
Intel(R) SSE3: Yes
Intel(R) SSE4: Yes
Intel(R) AES-NI: No
Intel(R) AVX: Yes
Enhanced Halt State: Yes
Execute Disable Bit: Yes
Gilda Sanchez -
BSOD KMODE_EXCEPTION_NOT_HANDLED on 10041 in KVM with OVMF
First, the crash dumps: http://1drv.ms/1GJxoRC (sorry about the non-English (Swedish) in there)
In my admittedly experimental setup that has so far been working unexpectedly well and stably, I started getting BSODs on launching a number of applications once I had updated to 10041. It is 100% reproducible and says KMODE_EXCEPTION_NOT_HANDLED*.
Every time I start Spotify (latest version), the crash happens instantly. In fact, I even get the blue screen when I try to uninstall it or download and run the installer (simple way of reproducing). This is by no means isolated to Spotify. Dark Souls II always
crashes the same way about one second into the first screen, often with visual distortion, making the BSOD unreadable. I reinstalled Windows Preview to another partition, and experience exactly the same behavior. On build 9926 everything is perfectly fine,
but once I upgraded that to 10041, the problems were back. I then reverted the update, and it's all good. But I can go back and test things, as one of the partitions i still on 10041.
Anyway, unless those crash dumps have all the info one could need, some context on my setup might be useful. I run the preview in a VM, using KVM on Linux, with OVMF (essentially turns the VM into a UEFI machine). I've been using GPU pass-through,
passing my Radeon HD 6970 over to windows, plus a few USB devices. I thought that might have been the problem, but I've tried running the VM without passing it through, and the same thing happens anyway. Maybe that's not enough to rule it out...
The VM uses a physical SSD rather than a disk image, so I can actually boot straight into it when I boot up the computer! When I do that, I don't experience the blue screens.
* There's been one occurrence of SYSTEM_SERVICE_EXCEPTION, when starting Dark Souls II, but I don't have the dump from that.Alright, never mind. 10049 fixed it! So thanks for the impossibly quick support, hehe!
-
PC Crash with Labview 7 and windows 2000
Problem:
the PC does reboot without any prompt when a LV 7 vi is running; the reboot seems to occur randomly (no time dependent); sometimes instead of rebooting, the PC switches to the blue screen with the following message:
Stop: 0x0000001E (0xC0000002, 0x80419292, 0x00000000, 0x00000000)
KMODE_EXCEPTION_NOT_HANDLED
Xxx Address 80419292 base at 80400000, date stamp 3EE6C002-ntoskrnl.exe
Starting memory download
Configuration:
Intel Pentium IV - 2.66 GHz - RAM 1 Gbyte - Video chipset Intel 82865G;
OS: Windows 2000
DAQ Board: PCI MIO 16 E1;
Labview 7 express - NIDAQ 7.1
Note:
The VI that causes the reboot uses the DAQMX to generate an Analog Output with analog trigger.> The VI that causes the reboot uses the DAQMX to generate an Analog
> Output with analog trigger.
You probably want to post this problem to the DAQ message board as well
since LV itself really can't cause either of these problems on a
protected OS. Be sure to be very explicit about what HW boards and what
DaqMX calls you are making along with which version of the driver you have.
Greg McKaskle -
Hello ThinkPad fans,
About one year I turn to ThinkPad T500...
Unfortunately I am not contented!
After T61 I feel very very big difference... (to the worse)
Originally is comes with Windows Vista, one week ago I upgraded OS up to Windows 7 (Seven).
BUT! Bugs and blue screens quantity become more and more....
CLICK HERE: http://proservice.ge/crash/
note: It's not my primary PC, totaly work hour will be about 20Hr... or less...
Anybody help me... Is some patch or update for more stability??
CHANGED HDD from HITACHI To FUJITSU
CHANGED OS
AND PROBLEM STAYING............Dear Mark,
File Version 6.1.7600.16385 (win7_rtm.090713-1255) 6.1.7600.16385 (win7_rtm.090713-1255) 6.1.7600.16385 (win7_rtm.090713-1255) 6.1.7600.16385 (win7_rtm.090713-1255) 6.1.7600.16385 (win7_rtm.090713-1255)
Full Path C:\Windows\minidump\111709-52884-01.dmp C:\Windows\minidump\111709-60075-01.dmp C:\Windows\minidump\111709-77345-01.dmp C:\Windows\minidump\111409-60809-01.dmp C:\Windows\minidump\111409-50201-01.dmp C:\Windows\minidump\111309-48001-01.dmp C:\Windows\minidump\111309-48282-01.dmp C:\Windows\minidump\111209-51059-01.dmp C:\Windows\minidump\111109-37175-01.dmp
Bug Check Code 0x0000000a 0x000000d1 0x0000000a 0x0000000a 0x0000001e 0x0000000a 0x00000050 0x00000050 0x000000d1
Bug Check String IRQL_NOT_LESS_OR_EQUAL DRIVER_IRQL_NOT_LESS_OR_EQUAL IRQL_NOT_LESS_OR_EQUAL IRQL_NOT_LESS_OR_EQUAL KMODE_EXCEPTION_NOT_HANDLED IRQL_NOT_LESS_OR_EQUAL PAGE_FAULT_IN_NONPAGED_AREA PAGE_FAULT_IN_NONPAGED_AREA
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Parameter 1 fffff683`ff7f3588 00000000`00000022 00000000`000021dc fffff680`003bebc8 00000000`00000000 00000000`08585430 fffff880`0279fba0 fffff880`085bd408 00000000`00000000
Parameter 2 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000002
Parameter 3 00000000`00000000 00000000`00000008 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 fffff800`02d646e5 fffff880`058c1718 00000000`00000008
Parameter 4 fffff800`02aacdbc 00000000`00000022 fffff800`02ace6e9 fffff800`02aefdbc 00000000`00000000 fffff800`02a97b75 00000000`00000000 00000000`00000001 00000000`00000000
Sorry but forum can't see HTML table......
>>Did you upgrade or do a clean install of Windows 7?
>>Did you download all the appropriate Windows 7 drivers from the Lenovo website, either manually, or by first >>installing TVSU version 4.0 and then running that?
>>Have you updated the BIOS on the system to the latest level?
Mark, OS was cleaned and re-install in Lenovo Partner Service Center T'bilisi.
I tried all versions of BIOS-is.... : (
Same problems in vista..... more problems in Windows 7.... FROM 1ST DAY!...... -
Crash every time Windows refreshes policy
We have a Windows Server 2008 R2 box that is blue screening and crashing every time it refreshes group policy.
Computer starts up, gets to "Applying Registry policy" for a minute or so, then crashes.
I unplugged the computer from the network during startup and, without a DC to grab GP from, I get to the Ctrl-Alt-Del screen
Plugging the computer back into the network, then logging on with a domain user, we again get to "Applying Registry policy" and then crash
If I leave it unplugged from the network and THEN log in, or log in with a local user account, I can get in
When plugged back in, the computer will then reboot within a short time, presumably when the background GP refresh occurs
To test, I made a new OU, blocked inheritance on it, and moved the computer account into it
Now I can start up successfully while plugged into the network, however a domain user will still cause a crash because the user account does not have the GPs blocked
Moving the user account into the new OU also removes the crash
With no GPOs applied, the computer also doesn't crash when the background refresh applies
Disabling all startup items in msconfig doesn't affect the issue
With all of the above, I'm confident that this only occurs when Windows attempts to apply group policy. I verified that no GPOs have been changed in over a month. No other machine (server or PC) is having this issue. Restoring the registry to a version from
a few weeks back didn't help. So far, Microsoft phone support hasn't figured it out. Obviously, leaving the computer account in the test OU with inheritance blocked can't be our long-term solution. I'm at a loss over what to do next short of wiping the machine
and restoring. This is an Exchange server so I'm not looking forward to restoring that.Hi,
For Bug Check 0x1E, it indicates that a kernel-mode program generated an exception which the error handler did not catch. For more details, please refer to following article and check if can
help you.
Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED
Meanwhile, please refer to following KB and check if help you to troubleshoot the
Stop error code 0x0000001E
issue.
How to troubleshoot a "Stop error code 0x0000001E (KMODE_EXCEPTION_NOT_HANDLED)" error message
àI actually haven't been able to get Windows to generate a crash dump.
When you receive a STOP error message or a fatal system error message, a Memory.dmp file may not be created. Please refer to following KB and check if help you to generate the dump file.
Windows does not save memory dump file after a crash
By the way, for this kind of kernel crash issue, if this issues is a state of emergency for you. Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated
Support Professional can assist with your request.
To obtain the phone numbers for specific technology request, please refer to the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Windows rebooted from a bug check..
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000048, 0x0000000000000002, 0x0000000000000001, 0xfffff8026303b73e).
Hello! I've been having bluescreens for about 2 months now. I thought it was my graphic card so I bought a new one and that did not work. I've formatted 4 times - running Windows 8.1 w/ all updates. Any deciphering of the bug check would be great, thanks
for your time.KMODE_EXCEPTION_NOT_HANDLED (1e)
This indicates that a kernel-mode program generated an exception which the error handler did not catch.
BugCheck 1E, {ffffffffc0000005, fffff80307127fd8, 0, ffffffffffffffff}
1: kd> ln fffff80307127fd8
(fffff803`07127ad0) nt!MiResolveProtoPteFault+0x508 | (fffff803`071283e0) nt!MiCompleteProtoPteFault
The exception occurred in nt!MiResolveProtoPteFault+0x508.
1: kd> kv
Child-SP RetAddr : Args to Child : Call Site
ffffd000`22e9ed88 fffff803`07219d47 : 00000000`0000001e ffffffff`c0000005 fffff803`07127fd8 00000000`00000000 : nt!KeBugCheckEx
ffffd000`22e9ed90 fffff803`071dabc2 : 00000000`c64430c0 fffff803`07332420 00000000`0000007d ffffe000`c5ada638 : nt! ?? ::FNODOBFM::`string'+0x3a897
ffffd000`22e9f480 fffff803`071d90fe : 00000000`0000043d 00007ffb`890e3001 ffff0000`00000001 0000ffff`fffff000 : nt!KiExceptionDispatch+0xc2
ffffd000`22e9f660 fffff803`07127fd8 : ffffe000`c9361dd8 00007ffb`890e3e88 00000001`60c4f021 ffffe000`c9361dd8 : nt!KiGeneralProtectionFault+0xfe (TrapFrame @ ffffd000`22e9f660)
ffffd000`22e9f7f0 fffff803`0712638d : fffff6e0`00da6610 00007ffb`8901a13c fffff6bf`fdc480d0 ffffe000`c9361dd8 : nt!MiResolveProtoPteFault+0x508
ffffd000`22e9f890 fffff803`070e258a : ffffe000`c94b1880 00007ffb`8901a13c ffffe000`c94b1880 ffffe000`00000000 : nt!MiDispatchFault+0x29d
ffffd000`22e9f9c0 fffff803`071d922f : 00000000`00000008 00000000`037cfb30 ffffe000`c94b1801 ffffd000`22e9fb00 : nt!MmAccessFault+0x36a
ffffd000`22e9fb00 00007ffb`8901a13c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f (TrapFrame @ ffffd000`22e9fb00)
00000000`206fda78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`8901a13c
1: kd> .trap ffffd000`22e9f660
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000073752860 rbx=0000000000000000 rcx=e000c93bf5780460
rdx=0000000000165396 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80307127fd8 rsp=ffffd00022e9f7f0 rbp=0000000000000000
r8=0000058000000000 r9=ffffe000c9361dd8 r10=ffffd00022e9fb00
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiResolveProtoPteFault+0x508:
fffff803`07127fd8 488b3f mov rdi,qword ptr [rdi] ds:00000000`00000000=????????????????
1: kd> u @rip
nt!MiResolveProtoPteFault+0x508:
fffff803`07127fd8 488b3f mov rdi,qword ptr [rdi]
fffff803`07127fdb 4885ff test rdi,rdi
fffff803`07127fde 0f841efcffff je nt!MiResolveProtoPteFault+0x132 (fffff803`07127c02)
fffff803`07127fe4 488bc7 mov rax,rdi
fffff803`07127fe7 4883e0f8 and rax,0FFFFFFFFFFFFFFF8h
fffff803`07127feb 4883f808 cmp rax,8
fffff803`07127fef 0f840dfcffff je nt!MiResolveProtoPteFault+0x132 (fffff803`07127c02)
fffff803`07127ff5 400fb6c7 movzx eax,dil
fffff803`07127d12 0f84f0020000 je nt!MiResolveProtoPteFault+0x538 (fffff803`07128008)
fffff803`07127d18 480fbae708 bt rdi,8
fffff803`07127d1d 0f82f0020000 jb nt!MiResolveProtoPteFault+0x543 (fffff803`07128013)
fffff803`07127d23 4c8bc3 mov r8,rbx
fffff803`07127d26 49c1e805 shr r8,5
fffff803`07127d2a 4183e01f and r8d,1Fh
fffff803`07127d2e 4184d9 test r9b,bl
fffff803`07127d31 0f857c370e00 jne nt! ?? ::FNODOBFM::`string'+0x2c003 (fffff803`0720b4b3)
fffff803`07127d37 488b442448 mov rax,qword ptr [rsp+48h]
fffff803`07127d3c 488d0dade1f5ff lea rcx,[nt!MiReadWrite (fffff803`07085ef0)]
Verify Flags Level 0x0002092b
STANDARD FLAGS:
[X] (0x00000000) Automatic Checks
[X] (0x00000001) Special pool
[X] (0x00000002) Force IRQL checking
[X] (0x00000008) Pool tracking
[ ] (0x00000010) I/O verification
[X] (0x00000020) Deadlock detection
[ ] (0x00000080) DMA checking
[X] (0x00000100) Security checks
[X] (0x00000800) Miscellaneous checks
[X] (0x00020000) DDI compliance checking
We have Driver Verifier enabled at the time of the crash, yet we have a ton of memory related stuff going on, and an exception occurring in one as well. Although Memtest failed, at this point I am going to say we're either not catching a problematic low-level
driver causing corruption, or we have a RAM/motherboard problem despite Memtest passing.
1. Uninstall any/all Asus bloatware (AI Suite, PC Probe, etc... whatever you have).
2. Uninstall/disable the nVidia Streaming Service ASAP.
3. If the above fails, faulty RAM and/or motherboard. Although before definitely concluding this, I'd try a BIOS update if available.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama -
Problems on G40-70 Windows 8.1
I just got my loptop yesterday and when I was booting it up it suddenly had a BSOD error ( Blue screen of Death w/ sad face) I had a bad feeling about it. But I countinued using it for a while at home and after and hour I got really alot of problems many different BSOD error occured may 4-6 diff errors and I don't know how to deal with them, And today I wish to update my loptop and facing update errors... I cant bare with this anymore since it's just a day old loptop im not expecting things like this pls help...
BOSD Errors that I've remember
Memory_Management
Kernel_date_inpage
Header something
KMODE_EXCEPTION_NOT_HANDLED
PAGE_FAULT_IN_NONPAGE_AREA
Winsys32 error
I've already Updated my bios but still getting Bsod /w sad face errors plus restarts my loptop everytime it shows up and many more... help thank you in Advance!!!hi there,
I checked the BSOD dump file and most of the errors are related to the Windows system files (which should be solved by installing all the critical Windows updates).
Sample bugcheck analysis using Windows Debugger:
Spoiler (Highlight to read)
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\XXX\Downloads\G40-70 DMP\043015-17343-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
Machine Name:
Kernel base = 0xfffff802`1ae07000 PsLoadedModuleList = 0xfffff802`1b0cb990
Debug session time: Thu Apr 30 15:55:34.509 2015 (UTC + 8:00)
System Uptime: 0 days 0:19:37.429
Loading Kernel Symbols
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8021af5b1ea, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!KiIpiInterruptSubDispatch+3a )
Followup: MachineOwner
0: kd> !analyze -v
* Bugcheck Analysis *
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8021af5b1ea, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8021b154150
GetUlongFromAddress: unable to read from fffff8021b154208
ffffffffffffffff
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!KiIpiInterruptSubDispatch+3a
fffff802`1af5b1ea 49014048 add qword ptr [r8+48h],rax
EXCEPTION_PARAMETER2: ffffffffffffffff
BUGCHECK_STR: 0x1E_c0000005_R
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
TRAP_FRAME: ffffd0002705f830 -- (.trap 0xffffd0002705f830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffffffffffce7 rbx=0000000000000000 rcx=ffffd0002705f982
rdx=ffffd0002705f570 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8021af5b1ea rsp=ffffd0002705fbc0 rbp=ffffd0002705fb80
r8=0200000000000200 r9=000000000000021f r10=fffff78000000208
r11=ffffd0002705fb70 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di ng nz ac po cy
nt!KiIpiInterruptSubDispatch+0x3a:
fffff802`1af5b1ea 49014048 add qword ptr [r8+48h],rax ds:02000000`00000248=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8021af9d45d to fffff8021af54ca0
STACK_TEXT:
ffffd000`2705ef58 fffff802`1af9d45d : 00000000`0000001e ffffffff`c0000005 fffff802`1af5b1ea 00000000`00000000 : nt!KeBugCheckEx
ffffd000`2705ef60 fffff802`1af608c2 : 00000000`01000001 5046504d`00000006 00000200`00080201 0035007b`000002b0 : nt! ?? ::FNODOBFM::`string'+0x382cd
ffffd000`2705f650 fffff802`1af5effe : 00000000`00000000 00000000`00000200 00000001`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffd000`2705f830 00000000`00000200 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x1fe
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x200
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!KiIpiInterruptSubDispatch+3a
fffff802`1af5b1ea 49014048 add qword ptr [r8+48h],rax
SYMBOL_NAME: nt!KiIpiInterruptSubDispatch+3a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 52341cf4
IMAGE_VERSION: 6.3.9600.16404
BUCKET_ID_FUNC_OFFSET: 3a
FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!KiIpiInterruptSubDispatch
BUCKET_ID: 0x1E_c0000005_R_nt!KiIpiInterruptSubDispatch
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_nt!kiipiinterruptsubdispatch
FAILURE_ID_HASH: {d1270e15-fab6-00a5-b8c2-9ba6d7d3d4b9}
Followup: MachineOwner
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\XXX\Downloads\G40-70 DMP\043015-17343-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Symbol Path validation summary **************Response Time (ms) LocationDeferred srv*c:\symbols*http://msdl.microsoft.com/download/symbolsSymbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 8 Kernel Version 9600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9600.16404.amd64fre.winblue_gdr.130913-2141Machine Name:Kernel base = 0xfffff802`1ae07000 PsLoadedModuleList = 0xfffff802`1b0cb990Debug session time: Thu Apr 30 15:55:34.509 2015 (UTC + 8:00)System Uptime: 0 days 0:19:37.429Loading Kernel Symbols.Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.Run !sym noisy before .reload to track down problems loading symbols...............................................................................................................................................................Loading User SymbolsLoading unloaded module list....................******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1E, {ffffffffc0000005, fffff8021af5b1ea, 0, ffffffffffffffff}Probably caused by : ntkrnlmp.exe ( nt!KiIpiInterruptSubDispatch+3a )Followup: MachineOwner---------0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KMODE_EXCEPTION_NOT_HANDLED (1e)This is a very common bugcheck. Usually the exception address pinpointsthe driver/function that caused the problem. Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff8021af5b1ea, The address that the exception occurred atArg3: 0000000000000000, Parameter 0 of the exceptionArg4: ffffffffffffffff, Parameter 1 of the exceptionDebugging Details:------------------READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8021b154150GetUlongFromAddress: unable to read from fffff8021b154208 ffffffffffffffff EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.FAULTING_IP: nt!KiIpiInterruptSubDispatch+3afffff802`1af5b1ea 49014048 add qword ptr [r8+48h],raxEXCEPTION_PARAMETER2: ffffffffffffffffBUGCHECK_STR: 0x1E_c0000005_RCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULTPROCESS_NAME: svchost.exeCURRENT_IRQL: 2ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64freTRAP_FRAME: ffffd0002705f830 -- (.trap 0xffffd0002705f830)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=fffffffffffffce7 rbx=0000000000000000 rcx=ffffd0002705f982rdx=ffffd0002705f570 rsi=0000000000000000 rdi=0000000000000000rip=fffff8021af5b1ea rsp=ffffd0002705fbc0 rbp=ffffd0002705fb80 r8=0200000000000200 r9=000000000000021f r10=fffff78000000208r11=ffffd0002705fb70 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up di ng nz ac po cynt!KiIpiInterruptSubDispatch+0x3a:fffff802`1af5b1ea 49014048 add qword ptr [r8+48h],rax ds:02000000`00000248=????????????????Resetting default scopeLAST_CONTROL_TRANSFER: from fffff8021af9d45d to fffff8021af54ca0STACK_TEXT: ffffd000`2705ef58 fffff802`1af9d45d : 00000000`0000001e ffffffff`c0000005 fffff802`1af5b1ea 00000000`00000000 : nt!KeBugCheckExffffd000`2705ef60 fffff802`1af608c2 : 00000000`01000001 5046504d`00000006 00000200`00080201 0035007b`000002b0 : nt! ?? ::FNODOBFM::`string'+0x382cdffffd000`2705f650 fffff802`1af5effe : 00000000`00000000 00000000`00000200 00000001`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2ffffd000`2705f830 00000000`00000200 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x1fe00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x200STACK_COMMAND: .bugcheck ; kbFOLLOWUP_IP: nt!KiIpiInterruptSubDispatch+3afffff802`1af5b1ea 49014048 add qword ptr [r8+48h],raxSYMBOL_NAME: nt!KiIpiInterruptSubDispatch+3aFOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP: 52341cf4IMAGE_VERSION: 6.3.9600.16404BUCKET_ID_FUNC_OFFSET: 3aFAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!KiIpiInterruptSubDispatchBUCKET_ID: 0x1E_c0000005_R_nt!KiIpiInterruptSubDispatchANALYSIS_SOURCE: KMFAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_nt!kiipiinterruptsubdispatchFAILURE_ID_HASH: {d1270e15-fab6-00a5-b8c2-9ba6d7d3d4b9}Followup: MachineOwner---------
As for the unknown device error in the image, can you follow this guide on how to identify the device and find the correct driver for it.:
The memory diagnostics error: http://i.imgur.com/wAnJ4Bd.png seems to be the culprit here. Have you considered contacting lenovo (for service) or the place of purchase (if it's still possible to get a replacement unit) ? It looks like you may need to get a replacement RAM.
Regards
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!
Maybe you are looking for
-
Is it possible to use Lightroom/Photoshop directly from a external hard drive?
As a beginner at Lightroom and Photoshop and still having a large amount of old photos I want to work with, can I leave them on the external hard drive or do I have to import them to work on them? My constraint of course is space. Thanks, Wyndon
-
Random screen saver and iPhoto
I use the random screen saver function but would really prefer that it not use images from iPhoto. I have hunted through the screen saver panel and through iPhoto prefs looking for a way to stop the screen saver function from using iPhoto data, but c
-
Why does photoshop (cs5) 'hang/stall' when saving as jpeg?
i've been noticing that the program has seemed to run slower than it was a few months ago - taking longer to load up, buttons being unresponsive for a few seconds, etc. recently i noticed if i'm saving my psd file as a jpeg it will 'hang' for severa
-
When I try to open a game in my Game Center, they won't open. I just updated my iPad to the newest version of iOS and won't open my games anymore. Any suggestions
-
How to add commandLink attribute programmatically
Hi, I have command Link: af:commandLink text="save" actionListener="#{myBean.method}" partialSubmit="true"> <f:attribute name="name" value="#{emp.name}"/> </af:commandLink> If i use above code in jsf and get the attribute name it gives me the value l