BSOD: INTERRUPT_EXCEPTION_NOT_HANDLED 0x3d

[hajduzoltan1983]

Hi everyone!

I'm having a serious problem with my Win7 x64, as it crashes all the time since I installed (Win Vista does the same). I have updated all the drivers, run the Memtest, bought new memory modules but I cant rid of the problem. Can you check the attached files please?

Thank you!

 

[zigzag3143]

You have only one DMP file from March, the rest are from January. Where are the rest if it crashes all the time?

 

[hajduzoltan1983]

I was using my laptop instead, as Win7 on my desktop PC is unusable. Find my new attachment please created after the "verifier" today.
Thanks!

 

[zigzag3143]

I was using my laptop instead, as Win7 on my desktop PC is unusable. Find my new attachment please created after the "verifier" today.
Thanks!

Related to Microsot Filesystem Filter Manager

Please run a system file check and post the results

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

 

[hajduzoltan1983]

"Windows Resource Protection did not find any integrity violations."

 

[hajduzoltan1983]

somebody can help me please?

 

[writhziden]

Check your hard disk for errors:

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.

 

[hajduzoltan1983]

Check Disk fixed some errors on secondary HDD, i hope it will help.. we will see soon

 

[writhziden]

Alright, post back whether the system is stable or not. Also, you may want to run disk check again if you have not already done so to make sure all errors have already been fixed.

 

[hajduzoltan1983]

Check disk did not found any new errors, the system has been stable for 10 hours now

 

[hajduzoltan1983]

No errors on HDD but the BSOD still remains..

 

[writhziden]

Please upload the latest crash reports. Now that errors have been removed from the hard disks, they may point to the true culprit.

 

[hajduzoltan1983]

new minidump

 

[writhziden]

[list=1][*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0301f000 PsLoadedModuleList = 0xfffff800`03263650
Debug session time: Sun Mar 25 08:53:46.592 2012 (UTC - 6:00)
System Uptime: 0 days 7:16:05.672
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff88002e22110, 0, 0, fffff800030a5857}

Probably caused by : ntkrnlmp.exe ( nt!KiInterruptDispatchNoLock+163 )

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

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

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff88002e22110
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff800030a5857

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


CONTEXT:  fffff88002e22110 -- (.cxr 0xfffff88002e22110)
rax=0000000000000002 rbx=0000000000000001 rcx=0000000000000001
rdx=0000000000000008 rsi=fffff80003210e80 rdi=fffff8000320ef18
rip=fffff800030a5857 rsp=fffff88002e22af0 rbp=fffff78000000320
 r8=0000000000000001  r9=fffff8000320ef18 r10=0000000000000000
r11=fffff88002e22b40 r12=0000000000000000 r13=fffff88002e22c20
r14=0000000000000004 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!KeUpdateSystemTime+0x2c7:
fffff800`030a5857 4a09040a        or      qword ptr [rdx+r9],rax ds:002b:fffff800`0320ef20=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3D

PROCESS_NAME:  Anno5.exe

CURRENT_IRQL:  d

LAST_CONTROL_TRANSFER:  from fffff80003611895 to fffff800030a5857

STACK_TEXT:  
fffff880`02e22af0 fffff800`03611895 : fffff800`03637460 fffff880`02e22ca0 fffff800`03637460 00000000`00000000 : nt!KeUpdateSystemTime+0x2c7
fffff880`02e22bf0 fffff800`03098273 : 00000000`00000000 fffff880`02e22c01 fffffa80`039c6240 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`02e22c20 00000000`650ee998 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
00000000`10a9d3dc 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x650ee998


FOLLOWUP_IP: 
nt!KiInterruptDispatchNoLock+163
fffff800`03098273 f685f3000000ff  test    byte ptr [rbp+0F3h],0FFh

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiInterruptDispatchNoLock+163

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

STACK_COMMAND:  .cxr 0xfffff88002e22110 ; kb

FAILURE_BUCKET_ID:  X64_0x3D_nt!KiInterruptDispatchNoLock+163

BUCKET_ID:  X64_0x3D_nt!KiInterruptDispatchNoLock+163

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\hajduzoltan1983\Windows_NT6_BSOD_jcgriff2\032412-22074-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03061000 PsLoadedModuleList = 0xfffff800`032a5650
Debug session time: Sat Mar 24 06:28:19.736 2012 (UTC - 6:00)
System Uptime: 0 days 5:01:24.016
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff8800acd9110, 0, 0, fffff800030e7857}

Probably caused by : ntkrnlmp.exe ( nt!KiInterruptDispatchNoLock+163 )

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

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

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff8800acd9110
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff800030e7857

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


CONTEXT:  fffff8800acd9110 -- (.cxr 0xfffff8800acd9110)
rax=0000000000000002 rbx=0000000000000001 rcx=0000000000000001
rdx=0000000000000008 rsi=fffff80003252e80 rdi=fffff80003250f18
rip=fffff800030e7857 rsp=fffff8800acd9af0 rbp=fffff78000000320
 r8=0000000000000001  r9=fffff80003250f18 r10=0000000000000000
r11=fffff8800acd9b40 r12=0000000000000000 r13=fffff8800acd9c20
r14=0000000000000004 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!KeUpdateSystemTime+0x2c7:
fffff800`030e7857 4a09040a        or      qword ptr [rdx+r9],rax ds:002b:fffff800`03250f20=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3D

PROCESS_NAME:  setup.exe

CURRENT_IRQL:  d

LAST_CONTROL_TRANSFER:  from fffff80003022895 to fffff800030e7857

STACK_TEXT:  
fffff880`0acd9af0 fffff800`03022895 : fffff800`03048460 fffff880`0acd9ca0 fffff800`03048460 00000000`00000000 : nt!KeUpdateSystemTime+0x2c7
fffff880`0acd9bf0 fffff800`030da273 : 00000000`00000000 00000000`078a1000 00000000`0031eb01 00000000`0031eb28 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0acd9c20 00000000`00bb3249 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
00000000`0031e8ac 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xbb3249


FOLLOWUP_IP: 
nt!KiInterruptDispatchNoLock+163
fffff800`030da273 f685f3000000ff  test    byte ptr [rbp+0F3h],0FFh

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiInterruptDispatchNoLock+163

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

STACK_COMMAND:  .cxr 0xfffff8800acd9110 ; kb

FAILURE_BUCKET_ID:  X64_0x3D_nt!KiInterruptDispatchNoLock+163

BUCKET_ID:  X64_0x3D_nt!KiInterruptDispatchNoLock+163

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


[/list]

Both crashes are crashes that occur very rarely in Windows 7, and so they do not have much information regarding the cause...


The crash may be related to drivers:

• 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. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 204418
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  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 http://www.sevenforums.com/tutorials/700-system-restore.html 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.