BSOD on cold boot - stop code 0x0000001E

alcatraz · 13 Jan 2012

Ran dsk chk again, both are clean with no errors, so moving onto step 2 now... will post results! :)

alcatraz · 13 Jan 2012

Hi writhziden, ran sfc scannow 3 times, each with no errors.. will await your response before proceeding...

writhziden · 14 Jan 2012

alcatraz said:

Hi writhziden, ran sfc scannow 3 times, each with no errors.. will await your response before proceeding...

Continue to step 3. :)

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\alcatraz\Windows_NT6_BSOD_jcgriff2\011312-20514-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03065000 PsLoadedModuleList = 0xfffff800`032aa670
Debug session time: Fri Jan 13 15:21:25.502 2012 (UTC - 7:00)
System Uptime: 0 days 0:25:10.000
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : cdrom.sys ( cdrom!DeviceMainTimerTickHandler+ba )

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

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3130336631346535
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9c1a8 -- (.exr 0xfffff80000b9c1a8)
ExceptionAddress: fffff88000ec6c7c (Wdf01000!FxPkgIo::DispathToInCallerContextCallback+0x00000000000000a0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9c250 -- (.trap 0xfffff80000b9c250)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000082 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000ec6c7c rsp=fffff80000b9c3e0 rbp=fffffa80082169d0
 r8=fffffa8007f03b10  r9=0000000000000000 r10=fffffa8007f03b10
r11=fffff88000f01260 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
Wdf01000!FxPkgIo::DispathToInCallerContextCallback+0xa0:
fffff880`00ec6c7c 4c8b1b          mov     r11,qword ptr [rbx] ds:29a0:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d95fe to fffff800030e1c10

STACK_TEXT:  
fffff800`00b9b288 fffff800`030d95fe : 00000000`00000000 00000000`00000000 fffff800`00b9ba00 fffff800`0310d830 : nt!KeBugCheck
fffff800`00b9b290 fffff800`0310d4fd : fffff800`032eb71c fffff800`03228c30 fffff800`03065000 fffff800`00b9c1a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b2c0 fffff800`0310c2d5 : fffff800`0322c0fc fffff800`00b9b338 fffff800`00b9c1a8 fffff800`03065000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b2f0 fffff800`0311d361 : fffff800`00b9c1a8 fffff800`00b9ba00 fffff800`00000000 fffffa80`08214020 : nt!RtlDispatchException+0x415
fffff800`00b9b9d0 fffff800`030e12c2 : fffff800`00b9c1a8 00000000`00000002 fffff800`00b9c250 00000000`00000000 : nt!KiDispatchException+0x135
fffff800`00b9c070 fffff800`030dfbca : 00000000`00000000 fffffa80`0d3da1c0 00000000`00000000 00001f80`00000500 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c250 fffff880`00ec6c7c : fffffa80`088c29a0 00000000`00000000 fffff880`00000000 00000000`00000158 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c3e0 fffff880`00ec5490 : fffffa80`07f03c70 fffffa80`088c29a0 fffffa80`07f03b10 fffffa80`08214020 : Wdf01000!FxPkgIo::DispathToInCallerContextCallback+0xa0
fffff800`00b9c410 fffff880`00eaf245 : fffffa80`088c29a0 0000057f`f773d3d8 fffffa80`088c2d18 fffffa80`088c2d38 : Wdf01000!FxPkgIo::Dispatch+0x2b4
fffff800`00b9c490 fffff880`0483ecde : fffffa80`088c2c20 fffff800`030ee1f4 fffffa80`00000000 fffffa80`07704a80 : Wdf01000!FxDevice::Dispatch+0xa9
fffff800`00b9c4c0 fffff880`00eb8f19 : fffff880`04151d68 fffff880`04144688 fffff880`04151d68 00000000`00000000 : cdrom!DeviceMainTimerTickHandler+0xba
fffff800`00b9c500 fffff880`00eb8f50 : fffff800`00b9c630 fffff800`00b9c648 00000000`00000000 fffffa80`03c4ce00 : Wdf01000!FxTimer::TimerHandler+0xb5
fffff800`00b9c540 fffff800`030ed5fc : fffff800`0000000f fffff800`00b9c618 00000000`00000008 00000000`00000000 : Wdf01000!FxTimer::_FxTimerDpcThunk+0x18
fffff800`00b9c570 fffff800`030ed496 : fffffa80`03c063d8 fffffa80`03c063d8 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`030ed37e : 00000003`8407dc60 fffff800`00b9cc58 00000000`00017a1a fffff800`0325a5c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`030ed167 : 00000001`189a49cf 00000001`00017a1a 00000001`189a49ce 00000000`0000001a : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`030d996a : fffff800`03257e80 fffff800`03265cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cdrom!DeviceMainTimerTickHandler+ba
fffff880`0483ecde 4883c438        add     rsp,38h

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  cdrom!DeviceMainTimerTickHandler+ba

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdrom

IMAGE_NAME:  cdrom.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79298

FAILURE_BUCKET_ID:  X64_0x1E_0_cdrom!DeviceMainTimerTickHandler+ba

BUCKET_ID:  X64_0x1E_0_cdrom!DeviceMainTimerTickHandler+ba

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

Your last .dmp file listed cdrom.sys as the culprit, but it was another KMODE_EXCEPTION_NOT_HANDLED (1e) crash, so the steps I outlined in my first post are still relevant.

Also, you should update the following drivers ASAP.

Code:

PxHlpa64	fffff880`015f0000	fffff880`015fbd00	Wed Mar 12 19:58:17 2008 (47d88a39)	0001d5ea		PxHlpa64.sys
AVerIR	fffff880`04c00000	fffff880`04c1e000	Mon Sep 08 03:31:35 2008 (48c4f0f7)	00026326		AVerIR.sys
GEARAspiWDM	fffff880`04000000	fffff880`0400d000	Mon May 18 06:17:04 2009 (4a1151c0)	000159b4		GEARAspiWDM.sys

alcatraz · 15 Jan 2012

Hi I went through all steps in step 3 with no errors found. With regard to the driver updates, I'm having trouble updating the 3 drivers you listed. I cant find my model of pc on my manufacturers website and therefore cant find the correct driver update for Avermedia. I downloaded what I thought was the best match, but its just a folder with lots of files in it, with no instructions on how to update! I'm not savvy enough to know how to update these types of system drivers so I'm at a loss now really

alcatraz · 15 Jan 2012

Oh I havent had a crash (BSOD) for the last 2 days now, forgot to mention that!! It's booted from cold just fine!

writhziden · 15 Jan 2012

alcatraz said:

Hi I went through all steps in step 3 with no errors found. With regard to the driver updates, I'm having trouble updating the 3 drivers you listed. I cant find my model of pc on my manufacturers website and therefore cant find the correct driver update for Avermedia. I downloaded what I thought was the best match, but its just a folder with lots of files in it, with no instructions on how to update! I'm not savvy enough to know how to update these types of system drivers so I'm at a loss now really

To update your drivers, see Driver Install - Add Hardware Wizard and Driver Install - Device Manager for two different methods to install drivers. :)

The two methods should allow you to use the folders you have downloaded that are full of files.

alcatraz said:

Oh I havent had a crash (BSOD) for the last 2 days now, forgot to mention that!! It's booted from cold just fine!

That's great news. Do your normal routine for a week, and if your system is stable, you can mark the thread as solved by clicking the green button at the bottom of the thread next to Post Reply. :)

If you have any problems, we can proceed with the next steps.

writhziden · 05 Feb 2012

Is the system still running stable? Were you able to update your drivers?