Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD again.......

09 Jun 2010   #11
Jonathan_King

Windows 7 Professional x64
 
 

It pointed to a core Windows file, 100% guaranteed not to be the issue. I can't open the dmp for whatever reason, but I'm making an educated guess that it was ntkrnlmp.exe.

It didn't point to a specific driver, that's why we need driver verifier. We are guessing it's a driver from the bugcheck codes.


My System SpecsSystem Spec
.
10 Jun 2010   #12
penfold007

Windows 7 Ultimate x86
 
 

before I use the driver verifier, could you please tell me what the file was that you said cant cause the bsod but was showing in the minidump?? you also said it was a driver isue, but have you any idea what the probable culprit was??

many thanx
My System SpecsSystem Spec
10 Jun 2010   #13
penfold007

Windows 7 Ultimate x86
 
 

do you think that it 64bit specific?? if so would 32bit win 7 solve it??
My System SpecsSystem Spec
.

10 Jun 2010   #14
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by penfold007 View Post
before I use the driver verifier, could you please tell me what the file was that you said cant cause the bsod but was showing in the minidump?? you also said it was a driver isue, but have you any idea what the probable culprit was??

many thanx
You asked 15 hours aga. JK replied, you asked again here, I am replying. It isnt the win 7 OS file, just that the debugger has to point at something

Quote   Quote: Originally Posted by penfold007 View Post
do you think that it 64bit specific?? if so would 32bit win 7 solve it??
It can happen in either format. Might have less chance of it happening in win 7 32bit. Yet to be determined


Good luck with verifier. Just make sure you have a backup, restore point, and working win 7 dvd




Ken
My System SpecsSystem Spec
10 Jun 2010   #15
penfold007

Windows 7 Ultimate x86
 
 

OK many thanks, will let you know of the outcome
My System SpecsSystem Spec
22 Jun 2010   #16
penfold007

Windows 7 Ultimate x86
 
 

well...... did the drive verifier....... on startup was getting the BSOD. BUT.... it still wasnt saying what the driver was that was causing the problem????
My System SpecsSystem Spec
22 Jun 2010   #17
Jonathan_King

Windows 7 Professional x64
 
 

My System SpecsSystem Spec
23 Jun 2010   #18
penfold007

Windows 7 Ultimate x86
 
 

latest dmp file at 11 ish this morning
My System SpecsSystem Spec
23 Jun 2010   #19
Jonathan_King

Windows 7 Professional x64
 
 

Verifier did not appear to be running at the time of the crash. Please make sure it is: Using Driver Verifier to identify issues with Drivers

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_062310-24304-01.zip\062310-24304-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have thread information
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82a4b000 PsLoadedModuleList = 0x82b93810
Debug session time: Tue Jun 22 23:26:58.408 2010 (UTC - 4:00)
System Uptime: 0 days 1:37:00.625
Loading Kernel Symbols
...................................................Unable to load image Unknown_Module_00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
Unable to add module at 00000000

Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {82938634, 2, 1, 82ab4daf}

Unable to read KTHREAD address 8a8d6708
Probably caused by : ntkrpamp.exe ( nt!KiTimerExpiration+15d )

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

0: 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: 82938634, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 82ab4daf, address which referenced memory

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

Unable to read KTHREAD address 8a8d6708

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82bb3718
Unable to read MiSystemVaType memory at 82b93160
 82938634 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!KiTimerExpiration+15d
82ab4daf 8911            mov     dword ptr [ecx],edx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from 00640069 to 82b0becc

STACK_TEXT:  
aa9f0834 00640069 00790061 005c0073 00640045 nt!MiRestoreTransitionPte+0x233
WARNING: Frame IP not in any known module. Following frames may be wrong.
aa9f0838 00790061 005c0073 00640045 006e0069 <Unloaded_Unknown_Module_00530048>+0x110021
aa9f083c 005c0073 00640045 006e0069 00750062 <Unloaded_Unknown_Module_00530048>+0x260019
aa9f0840 00640045 006e0069 00750062 00670072 <Unloaded_Unknown_Module_00530048>+0x9002b
aa9f0844 006e0069 00750062 00670072 00200068 <Unloaded_Unknown_Module_00530048>+0x10fffd
aa9f0848 00750062 00670072 00200068 006f0048 <Unloaded_Unknown_Module_00530048>+0x1b0021
aa9f084c 00670072 00200068 006f0048 0069006c <Unloaded_Unknown_Module_00530048>+0x22001a
aa9f0850 00200068 006f0048 0069006c 00610064 <Unloaded_Unknown_Module_00530048>+0x14002a
aa9f0854 006f0048 0069006c 00610064 005c0079 <Unloaded_Unknown_Module_00000000>+0x200068
aa9f0858 0069006c 00610064 005c0079 006f0052 <Unloaded_Unknown_Module_00530048>+0x1c0000
aa9f085c 00610064 005c0079 006f0052 00610079 <Unloaded_Unknown_Module_00530048>+0x160024
aa9f0860 005c0079 006f0052 00610079 0020006c <Unloaded_Unknown_Module_00530048>+0xe001c
aa9f0864 006f0052 00610079 0020006c 00610059 <Unloaded_Unknown_Module_00530048>+0x90031
aa9f0868 00610079 0020006c 00610059 00630075 <Unloaded_Unknown_Module_00530048>+0x1c000a
aa9f086c 0020006c 00610059 00630075 00740068 <Unloaded_Unknown_Module_00530048>+0xe0031
aa9f0870 00610059 00630075 00740068 00610020 <Unloaded_Unknown_Module_00000000>+0x20006c
aa9f0874 00630075 00740068 00610020 0064006e <Unloaded_Unknown_Module_00530048>+0xe0011
aa9f0878 00740068 00610020 0064006e 00480020 <Unloaded_Unknown_Module_00530048>+0x10002d
aa9f087c 00610020 0064006e 00480020 006c006f <Unloaded_Unknown_Module_00530048>+0x210020
aa9f0880 0064006e 00480020 006c006f 0079006c <Unloaded_Unknown_Module_00530048>+0xdffd8
aa9f0884 00480020 006c006f 0079006c 006f0072 <Unloaded_Unknown_Module_00530048>+0x110026
aa9f0888 006c006f 0079006c 006f0072 0064006f <Unloaded_Unknown_Module_00000000>+0x480020
aa9f088c 0079006c 006f0072 0064006f 00480020 <Unloaded_Unknown_Module_00530048>+0x190027
aa9f0890 006f0072 0064006f 00480020 0075006f <Unloaded_Unknown_Module_00530048>+0x260024
aa9f0894 0064006f 00480020 0075006f 00650073 <Unloaded_Unknown_Module_00530048>+0x1c002a
aa9f0898 00480020 0075006f 00650073 0043005c <Unloaded_Unknown_Module_00530048>+0x110027
aa9f089c 0075006f 00650073 0043005c 00720068 <Unloaded_Unknown_Module_00000000>+0x480020
aa9f08a0 00650073 0043005c 00720068 00730069 <Unloaded_Unknown_Module_00530048>+0x220027
aa9f08a4 0043005c 00720068 00730069 00690074 <Unloaded_Unknown_Module_00530048>+0x12002b
aa9f08a8 00720068 00730069 00690074 0065006e <Unloaded_Unknown_Module_00000000>+0x43005c
aa9f08ac 00730069 00690074 0065006e 0031005c <Unloaded_Unknown_Module_00530048>+0x1f0020
aa9f08b0 00690074 0065006e 0031005c 00300030 <Unloaded_Unknown_Module_00530048>+0x200021
aa9f08b4 0065006e 0031005c 00300030 0030005f <Unloaded_Unknown_Module_00530048>+0x16002c
aa9f08b8 0031005c 00300030 0030005f 00380039 <Unloaded_Unknown_Module_00530048>+0x120026
aa9f08bc 00300030 0030005f 00380039 002e0037 <Unloaded_Unknown_Module_00000000>+0x31005c
aa9f08c0 0030005f 00380039 002e0037 0050004a <Unloaded_Unknown_Module_00000000>+0x300030
aa9f08c4 00380039 002e0037 0050004a 00000047 <Unloaded_Unknown_Module_00000000>+0x30005f
aa9f08c8 002e0037 0050004a 00000047 00640000 <Unloaded_Unknown_Module_00000000>+0x380039
aa9f08cc 0050004a 00000047 00640000 00690064 <Unloaded_Unknown_Module_00000000>+0x2e0037
aa9f08d0 00000000 00640000 00690064 006b0073 <Unloaded_Unknown_Module_00000000>+0x50004a


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!KiTimerExpiration+15d
82ab4daf 8911            mov     dword ptr [ecx],edx

SYMBOL_NAME:  nt!KiTimerExpiration+15d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cacf

FAILURE_BUCKET_ID:  0xA_nt!KiTimerExpiration+15d

BUCKET_ID:  0xA_nt!KiTimerExpiration+15d

Followup: MachineOwner
---------
My System SpecsSystem Spec
23 Jun 2010   #20
penfold007

Windows 7 Ultimate x86
 
 

it wont be, had to format and re-install as after verifier it wouldnt let me back in, even in safe mode. So these results are from a bsod this morning.
the only 2 non microsoft verified drivers on at the moment are the marvell sata 6Gb driver for motherboard and the Sata 3 driver for motherboard. All others are from the system or windows update
My System SpecsSystem Spec
Reply

 BSOD again.......




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 18:11.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App