BSODs; iTunes, Youtube, random; 0x1e, 0x3d...

Richey13 · 13 Feb 2012

Throughout the course of the last few months I've been trying to fix this constant BSOD that haunts me. It happens very randomly, and I've yet to be able to correlate it to ONE particular reason, outside of maybe faulty RAM... But my RAM has tested fine time in and time out.

Recurring BSOD's: (as far as I know, I've been asleep for many)
0x000001e
0x000003d

System Specs:
Windows 7 Ultimate, x64
This is original
Full Retail: Was installed by myself.
The system is about 4 years old, I've updated a few times and re-installed Windows 7 a few months ago...

AMD Phenom 9750 (2.40 ghz)
4.00 gb RAM (DDR2)
Zotac GTX 465 (1gb gddr5)
WDC WD1600 ATA Device, WD6400 SCSI Disk Device

If you do need any more information, please do ask!

Thanks yet again,
Richey13

Richey13 · 13 Feb 2012

Bump..

writhziden · 17 Feb 2012

Code:


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\BSODDmpFiles\Richey13\Windows_NT6_BSOD_jcgriff2\021312-43664-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0301d000 PsLoadedModuleList = 0xfffff800`03262670
Debug session time: Mon Feb 13 13:33:18.161 2012 (GMT-7)
System Uptime: 0 days 7:00:52.691
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff88000000000, 8, fffff8800377ac00}

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

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

3: 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: fffff88000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: fffff8800377ac00, 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: 
+6686952f037edebc
fffff880`00000000 ff              ???

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  fffff8800377ac00

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  8

LAST_CONTROL_TRANSFER:  from fffff800030e5588 to fffff80003099c40

FAILED_INSTRUCTION_ADDRESS: 
+6686952f037edebc
fffff880`00000000 ff              ???

STACK_TEXT:  
fffff880`031fae28 fffff800`030e5588 : 00000000`0000001e ffffffff`c000001d fffff880`00000000 00000000`00000008 : nt!KeBugCheckEx
fffff880`031fae30 fffff800`030992c2 : fffff880`031fb608 00000000`00000000 fffff880`031fb6b0 fffffa80`04074130 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`031fb4d0 fffff800`0309741f : fffff880`031fb6b0 fffff880`0f2e5408 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`031fb6b0 fffff880`00000000 : 00000000`00000000 fffffa80`03fc11d0 00000000`00000000 00000000`00000000 : nt!KiInvalidOpcodeFault+0x11f
fffff880`031fb840 00000000`00000000 : fffffa80`03fc11d0 00000000`00000000 00000000`00000000 fffffa80`00000012 : 0xfffff880`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4977d
fffff800`030e5588 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_BAD_IP_nt!_??_::FNODOBFM::_string_+4977d

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

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

Loading Dump File [F:\BSODDmpFiles\Richey13\Windows_NT6_BSOD_jcgriff2\021312-40232-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03013000 PsLoadedModuleList = 0xfffff800`03258670
Debug session time: Mon Feb 13 06:30:53.773 2012 (GMT-7)
System Uptime: 0 days 0:20:26.692
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff88008d8d7f0, 0, 0, fffff88000000000}

Probably caused by : ntkrnlmp.exe ( nt!KiInterruptHandler+29 )

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

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

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff88008d8d7f0
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff88000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3D

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  8

EXCEPTION_RECORD:  fffff88008d8df98 -- (.exr 0xfffff88008d8df98)
Cannot read Exception record @ fffff88008d8df98

TRAP_FRAME:  fffff88008d8e040 -- (.trap 0xfffff88008d8e040)
Unable to read trap frame at fffff880`08d8e040

LAST_CONTROL_TRANSFER:  from fffff8000308f1e9 to fffff8000308fc40

STACK_TEXT:  
fffff880`08d8cf38 fffff800`0308f1e9 : 00000000`0000003d fffff880`08d8d7f0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`08d8cf40 fffff800`0308b529 : 00000000`00000000 fffffa80`04bba9d0 fffff880`08d8d7f0 fffff800`030bb830 : nt!KiBugCheckDispatch+0x69
fffff880`08d8d080 fffff800`030bb4fd : fffff800`03298c90 fffff800`031d9edc fffff800`03013000 fffff880`08d8df98 : nt!KiInterruptHandler+0x29
fffff880`08d8d0b0 fffff800`030ba2d5 : fffff800`031d9ed4 fffff880`08d8d128 fffff880`08d8df98 fffff800`03013000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`08d8d0e0 fffff800`030cb361 : fffff880`08d8df98 fffff880`08d8d7f0 fffff880`00000000 0000ffff`ffffffff : nt!RtlDispatchException+0x415
fffff880`08d8d7c0 fffff800`0308f2c2 : fffff880`08d8df98 00000000`00000000 fffff880`08d8e040 fffffa80`04cf66b0 : nt!KiDispatchException+0x135
fffff880`08d8de60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInterruptHandler+29
fffff800`0308b529 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiInterruptHandler+29

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x3D_nt!KiInterruptHandler+29

BUCKET_ID:  X64_0x3D_nt!KiInterruptHandler+29

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

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.
Possible causes are Memory problems...

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:

Shut down and turn off your computer.
Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
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.

Begin by re-installing iTunes using the steps for Removing and reinstalling iTunes, QuickTime, and other software components for Windows Vista or Windows 7.