blue screen error 0x000000E1

Possible out of date driver:

Code:

SCDEmu	fffff880`03d5b000	fffff880`03d74000	Sun Mar 15 04:30:00 2009 (49bcd8a8)	0001b43b		SCDEmu.SYS

SCDEmu.SYS

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\KiLLuA\Windows_NT6_BSOD_jcgriff2\031212-26192-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0300d000 PsLoadedModuleList = 0xfffff800`03252670
Debug session time: Mon Mar 12 07:07:58.873 2012 (UTC - 6:00)
System Uptime: 0 days 2:24:01.028
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffffa80094ebb60, 2, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4977d )

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

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: ffffffffc000001d, The exception code that was not handled
Arg2: fffffa80094ebb60, The address that the exception occurred at
Arg3: 0000000000000002, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
+3062636335343237
fffffa80`094ebb60 06              ???

EXCEPTION_PARAMETER1:  0000000000000002

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

BUGCHECK_STR:  0x1E_c000001d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SBotR_1.0.5.ex

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800030d5588 to fffff80003089c40

FAILED_INSTRUCTION_ADDRESS: 
+3062636335343237
fffffa80`094ebb60 06              ???

STACK_TEXT:  
fffff880`07f9df98 fffff800`030d5588 : 00000000`0000001e ffffffff`c000001d fffffa80`094ebb60 00000000`00000002 : nt!KeBugCheckEx
fffff880`07f9dfa0 fffff800`030892c2 : fffff880`07f9e778 fffff800`0308eedc fffff880`07f9e820 fffffa80`094ebc20 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`07f9e640 fffff800`0308741f : fffff880`07f9e820 fffff800`0308c802 fffff880`00000000 fffffa80`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`07f9e820 fffffa80`094ebb60 : fffffa80`094ebb60 00000000`00000000 00000000`00000002 00000000`0d02fd20 : nt!KiInvalidOpcodeFault+0x11f
fffff880`07f9e9b8 fffffa80`094ebb60 : 00000000`00000000 00000000`00000002 00000000`0d02fd20 00000000`7ef56000 : 0xfffffa80`094ebb60
fffff880`07f9e9c0 00000000`00000000 : 00000000`00000002 00000000`0d02fd20 00000000`7ef56000 fffffa80`08c31000 : 0xfffffa80`094ebb60


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4977d
fffff800`030d5588 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4977d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_c000001d_BAD_IP_nt!_??_::FNODOBFM::_string_+4977d

BUCKET_ID:  X64_0x1E_c000001d_BAD_IP_nt!_??_::FNODOBFM::_string_+4977d

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

Loading Dump File [D:\Kingston\BSODDmpFiles\KiLLuA\Windows_NT6_BSOD_jcgriff2\031112-19952-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e14000 PsLoadedModuleList = 0xfffff800`03059670
Debug session time: Sun Mar 11 09:32:52.794 2012 (UTC - 6:00)
System Uptime: 0 days 2:17:45.934
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {f, 2, 1, fffff80002e96d81}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : hardware ( dxgmms1!VidSchiProcessCompletedQueuePacketInternal+3dc )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000000000000f, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e96d81, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c3100
 000000000000000f 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiDeferredReadyThread+c1
fffff800`02e96d81 0000            add     byte ptr [rax],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  fffff88002f227d0 -- (.trap 0xfffff88002f227d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000f rbx=0000000000000000 rcx=000000000000000f
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e96d81 rsp=fffff88002f22960 rbp=fffffa80066d7040
 r8=000000000000000f  r9=fffffa800904ea58 r10=fffff80002e14000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!KiDeferredReadyThread+0xc1:
fffff800`02e96d81 0000            add     byte ptr [rax],al ds:00000000`0000000f=??
Resetting default scope

MISALIGNED_IP: 
nt!KiDeferredReadyThread+c1
fffff800`02e96d81 0000            add     byte ptr [rax],al

LAST_CONTROL_TRANSFER:  from fffff80002e901e9 to fffff80002e90c40

STACK_TEXT:  
fffff880`02f22688 fffff800`02e901e9 : 00000000`0000000a 00000000`0000000f 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f22690 fffff800`02e8ee60 : 00000000`00000000 ffffbeb6`4c0b22b9 fffff880`009eb180 00000000`00000004 : nt!KiBugCheckDispatch+0x69
fffff880`02f227d0 fffff800`02e96d81 : fffff880`030fb180 fffffa80`08e91770 fffff800`02e9ccec 00000000`00000011 : nt!KiPageFault+0x260
fffff880`02f22960 fffff800`02e94d30 : 00000000`00000002 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KiDeferredReadyThread+0xc1
fffff880`02f229e0 fffff880`0400a304 : fffffa80`00000000 fffffa80`00000000 fffffa80`08fe8000 fffffa80`08e91878 : nt!KeSetEvent+0x190
fffff880`02f22a50 fffff880`040097da : fffffa80`00000000 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x3dc
fffff880`02f22b10 fffff880`04008e00 : 00000000`00000000 fffffa80`0904e410 00000000`00000000 fffffa80`079d2010 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
fffff880`02f22bb0 fffff880`04008c4c : 00000000`00000510 fffffa80`0904e410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`02f22c00 fffff880`040e21cf : fffffa80`07d05280 fffff880`1115c3cf 00000000`00000022 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02f22c50 fffff880`110fb98c : fffffa80`0800c000 fffffa80`0800c000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`02f22c80 fffffa80`0800c000 : fffffa80`0800c000 00000000`00000000 00000000`00000000 fffff880`110fb91f : nvlddmkm+0xdc98c
fffff880`02f22c88 fffffa80`0800c000 : 00000000`00000000 00000000`00000000 fffff880`110fb91f fffffa80`0800c000 : 0xfffffa80`0800c000
fffff880`02f22c90 00000000`00000000 : 00000000`00000000 fffff880`110fb91f fffffa80`0800c000 00000000`00000000 : 0xfffffa80`0800c000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiProcessCompletedQueuePacketInternal+3dc
fffff880`0400a304 f6434001        test    byte ptr [rbx+40h],1

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  dxgmms1!VidSchiProcessCompletedQueuePacketInternal+3dc

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

1. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
   Thanks to JMH for helping with my understanding of this crash.
2. Appears to be related to DirectX/Graphics Card/Graphics Card Drivers... Other possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.

• If you are overclocking any hardware, please stop.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
  
  
• Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.
  
  Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
  
  
  1. Download the latest drivers for your display card(s)
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Expand Display adapters
  7. Do the following for each adapter (in case you have multiple display cards)
     
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  8. Restart your computer after uninstalling drivers for all display cards
  9. Install the latest driver for the display cards once Windows starts
  
  
  Alternatively:
  
  1. Login as an adminstrative user
  2. Download the latest drivers for your display card(s)
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Expand Display adapters
  8. Do the following for each adapter (in case you have multiple display cards)
     
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  9. Restart your computer after uninstalling drivers for all display cards
  10. Install the latest driver for the display cards once Windows starts
  
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. Run Driver Verifier and in step 3, only select Standard settings. Do not select the other two settings in the red boxes.
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

not all all its working perfect on my other PC , same specifications but not getting that error only once but maybe it was overloading ,also other PC have the over clock on but dont get that msg , all my work on both PC doesn't get the cpu meter over 20~25% & both have the same ram usage & i noticed when i leave the pc's ram unloaded there was no error but when i leave some stuff opened that make the ram usage about 64~70% i always wake up and see the pc have bluescreen i'll run memtest86+ tonight and wont stop it untill the next day, some of stuff i can help with : takeing a picture of the blue screen that will come up or came up before coz i disabled the auto restart, changeing the ram's sockets in my motherboard.