BSOD Issues

Crypt135 · 23 Jul 2010

Hi, I've been having BSOD issues once again after updating my gfx card drivers earlier today. Rolling them back to an older version, even through a fresh install, did not appear to help at all and I'm at a loss as to what could be causing these issues. All of the blue screens have shown up as IRQL_NOT_LESS_OR_EQUAL with the bug check code 0x0000000a, except for one which was SYSTEM_SERVICE_EXCEPTION with bug check code 0x0000003b.

The last BSOD before this post was also a bit strange, about ~10 seconds before it occurred windows desktop manager apparently stopped responding/bugged out.

Also, I'm not sure if hardware might have anything to do with this, but while trying to diagnose some previous BSOD's I've at least already confirmed my RAM is not faulty through Memtest.

Information from the sf diagnositc tool:

Attachment 86944

Attachment 86945

Attachment 86946

Attachment 86947

Attachment 86948

Thanks in advance.

JMH · 23 Jul 2010

Crypt135 said:

Hi, I've been having BSOD issues once again after updating my gfx card drivers earlier today. Rolling them back to an older version, even through a fresh install, did not appear to help at all and I'm at a loss as to what could be causing these issues. All of the blue screens have shown up as IRQL_NOT_LESS_OR_EQUAL with the bug check code 0x0000000a, except for one which was SYSTEM_SERVICE_EXCEPTION with bug check code 0x0000003b.

The last BSOD before this post was also a bit strange, about ~10 seconds before it occurred windows desktop manager apparently stopped responding/bugged out.

Also, I'm not sure if hardware might have anything to do with this, but while trying to diagnose some previous BSOD's I've at least already confirmed my RAM is not faulty through Memtest.

Information from the sf diagnositc tool:

Attachment 86944

Attachment 86945

Attachment 86946

Attachment 86947

Attachment 86948

Thanks in advance.

Hi Crypt135 and welcome

In examining the DMP files they all seem to point to a windows 7 OS file (ntkernlmp) which is almost impossible. Since it points to an OS file I can give you a few things to try.

1- since these seemed to occur after a GFX driver upgrade I would remove all traces of the current driver (they make a removal tool I think) and download and install a new copy just to be sure.

2- I would run system file check to verify and repair your system files. This will tell you if the OS file is truly at fault. You do this by typing cmd in search, then right clicking and running as admin. Then Type SFC /SCANNOW.

Let us know the results

The usual causes of this type of BSOD (BC 0xA) are:
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

What anti-virus are you running?

If you continue to get BSOD's we can get more aggressive by running driver verifier, but you should have a win 7 dvd (that works), a backup, and a restore point just in case. Let us know if/when you are ready.

Good Luck Mate

Jan

Code:

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


Loading Dump File [C:\Users\K\Desktop\072310-19375-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03291e50
Debug session time: Fri Jul 23 00:07:09.515 2010 (GMT-4)
System Uptime: 0 days 0:46:01.796
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {78000324a608, 2, 1, fffff800030d04f3}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+133 )

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

2: 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: 000078000324a608, 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: fffff800030d04f3, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fc0e0
 000078000324a608 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerExpiration+133
fffff800`030d04f3 f0480fb314c8    lock btr qword ptr [rax+rcx*8],rdx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f8caa0 -- (.trap 0xfffff88002f8caa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80003248988 rbx=0000000000000000 rcx=0000000000000390
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030d04f3 rsp=fffff88002f8cc30 rbp=000000000002b272
 r8=fffffa800704f700  r9=00000000000000c0 r10=0000000000000072
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KiTimerExpiration+0x133:
fffff800`030d04f3 f0480fb314c8    lock btr qword ptr [rax+rcx*8],rdx ds:fffff800`0324a608=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030c3b69 to fffff800030c4600

STACK_TEXT:  
fffff880`02f8c958 fffff800`030c3b69 : 00000000`0000000a 00007800`0324a608 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f8c960 fffff800`030c27e0 : 00000006`6e185e43 00000006`6e28c26e fffff880`02f64180 fffff880`02f67300 : nt!KiBugCheckDispatch+0x69
fffff880`02f8caa0 fffff800`030d04f3 : 00000000`00020000 00000000`00000000 00000000`00000000 00000000`00d564d5 : nt!KiPageFault+0x260
fffff880`02f8cc30 fffff800`030cfd97 : 00000002`4d7ffdc0 00000002`0002b273 00000002`4d7ffd68 00000000`00000072 : nt!KiTimerExpiration+0x133
fffff880`02f8ccd0 fffff800`030ccdfa : fffff880`02f64180 fffff880`02f6f040 00000000`00000001 fffff800`00000000 : nt!KiRetireDpcList+0x277
fffff880`02f8cd80 00000000`00000000 : fffff880`02f8d000 fffff880`02f87000 fffff880`02f8cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerExpiration+133
fffff800`030d04f3 f0480fb314c8    lock btr qword ptr [rax+rcx*8],rdx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerExpiration+133

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+133

BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+133

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

Crypt135 · 23 Jul 2010

Thanks for the response.

The system file check did not bring up any errors and I ran it a few times just to be sure. Also, I've already tried clearing out the old gfx driver completely and installing a new copy (via instructions from the Nvidia website) but that did not help either.

I'm currently using Microsoft Security Essentials and Malewarebytes for anti-virus, although until recently I was using AVG (if that matters).

At this point I've backed up files/etc. to an external HDD, created a restore point, and am ready to give driver verifier a shot.

JMH · 23 Jul 2010

Crypt135 said:

Thanks for the response.

The system file check did not bring up any errors and I ran it a few times just to be sure. Also, I've already tried clearing out the old gfx driver completely and installing a new copy (via instructions from the Nvidia website) but that did not help either.

I'm currently using Microsoft Security Essentials and Malewarebytes for anti-virus, although until recently I was using AVG (if that matters).

At this point I've backed up files/etc. to an external HDD, created a restore point, and am ready to give driver verifier a shot.

Hi Crypt again

MSE plus Malwarebytes are acceptable .
AVG is generally ok [I use the Pro version of AVG.]

Follow the directions below.

If you need more help let us know.

Good luck.

Jan.

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Crypt135 · 23 Jul 2010

Finished running the verifier and got five blue screens in total, but apparently it only recorded four. Two of them were on start-up, two in a game, and one around the log-in screen (can't recall exactly when or where). I believe it was after the fourth that the desktop manager stopped working once again after logging in.

Attachment 87097

**cluberti** · 23 Jul 2010

Well, driver verifier isn't going to help us here, because whatever is causing it is causing the kernel to look like the victim when watchdog times out. It's a driver issue for sure (given the bugcheck codes and the pattern), but figuring it out is going to have to be some good old fashioned gumshoe'ing. You've got the following non-Microsoft drivers loaded and running on the system at the time of the failure:

Code:

// I've never seen CPU-Z or Speedfan cause bugchecks before, but anything's possible:
2: kd> lmvm cpuz133_x64
start             end                 module name
fffff880`0469e000 fffff880`046a7000   cpuz133_x64 T (no symbols)           
    Loaded symbol image file: cpuz133_x64.sys
    Image path: \??\C:\Windows\system32\drivers\cpuz133_x64.sys
    Image name: cpuz133_x64.sys
    Timestamp:        Wed Mar 10 11:18:00 2010 (4B97C638)
    CheckSum:         0000B75D
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

2: kd> lmvm speedfan
start             end                 module name
fffff880`017c1000 fffff880`017c8000   speedfan T (no symbols)           
    Loaded symbol image file: speedfan.sys
    Image path: \SystemRoot\SysWOW64\speedfan.sys
    Image name: speedfan.sys
    Timestamp:        Sun Sep 24 09:26:48 2006 (45168798)
    CheckSum:         00005062
    ImageSize:        00007000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

// Your nvidia driver set is the more likely culprit, although which one is almost impossible to say:
2: kd> lmvm nv*
start             end                 module name
fffff880`00e00000 fffff880`00e29000   nvraid   T (no symbols)           
    Loaded symbol image file: nvraid.sys
    Image path: \SystemRoot\system32\DRIVERS\nvraid.sys
    Image name: nvraid.sys
    Timestamp:        Wed May 20 02:39:40 2009 (4A13A5AC)
    CheckSum:         000343E8
    ImageSize:        00029000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

fffff880`01061000 fffff880`010d9000   nvrd64   T (no symbols)           
    Loaded symbol image file: nvrd64.sys
    Image path: \SystemRoot\system32\DRIVERS\nvrd64.sys
    Image name: nvrd64.sys
    Timestamp:        Tue Aug 04 20:32:24 2009 (4A78D318)
    CheckSum:         0002F208
    ImageSize:        00078000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

fffff880`01126000 fffff880`01151000   nvstor   T (no symbols)           
    Loaded symbol image file: nvstor.sys
    Image path: \SystemRoot\system32\DRIVERS\nvstor.sys
    Image name: nvstor.sys
    Timestamp:        Wed May 20 02:45:37 2009 (4A13A711)
    CheckSum:         000381B4
    ImageSize:        0002B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

fffff880`011b3000 fffff880`011f2000   nvstor64 T (no symbols)           
    Loaded symbol image file: nvstor64.sys
    Image path: \SystemRoot\system32\DRIVERS\nvstor64.sys
    Image name: nvstor64.sys
    Timestamp:        Tue Aug 04 20:31:07 2009 (4A78D2CB)
    CheckSum:         0003D346
    ImageSize:        0003F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

fffff880`013eb000 fffff880`013f6000   nvsmu    T (no symbols)           
    Loaded symbol image file: nvsmu.sys
    Image path: \SystemRoot\system32\DRIVERS\nvsmu.sys
    Image name: nvsmu.sys
    Timestamp:        Mon Jun 29 03:36:37 2009 (4A486F05)
    CheckSum:         00012068
    ImageSize:        0000B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

fffff880`042f0000 fffff880`04341500   nvmf6264 T (no symbols)           
    Loaded symbol image file: nvmf6264.sys
    Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys
    Image name: nvmf6264.sys
    Timestamp:        Thu Jul 30 19:48:18 2009 (4A723142)
    CheckSum:         0005B9A8
    ImageSize:        00051500
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

fffff880`048c1000 fffff880`048da000   nvhda64v T (no symbols)           
    Loaded symbol image file: nvhda64v.sys
    Image path: \SystemRoot\system32\drivers\nvhda64v.sys
    Image name: nvhda64v.sys
    Timestamp:        Thu Jan 28 09:24:54 2010 (4B619E36)
    CheckSum:         0001B32F
    ImageSize:        00019000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

fffff880`0fef5000 fffff880`10b62c80   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon Jun 07 18:16:55 2010 (4C0D6FD7)
    CheckSum:         00C7A8E1
    ImageSize:        00C6DC80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

fffff880`10b63000 fffff880`10b64180   nvBridge T (no symbols)           
    Loaded symbol image file: nvBridge.kmd
    Image path: \SystemRoot\system32\DRIVERS\nvBridge.kmd
    Image name: nvBridge.kmd
    Timestamp:        Mon Jun 07 18:07:11 2010 (4C0D6D8F)
    CheckSum:         0000EB20
    ImageSize:        00001180
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Assuming you've got an nVidia chipset (looks like RAID and video at the least), all of these should be checked to see if there are newer versions out there that you can update to.

Crypt135 · 23 Jul 2010

I've removed both CPUZ and Speedfan just to try and rule those out, and I also installed an nForce driver update I somehow missed before, but I still blue screened shortly after. As far as I know, all of my Nvidia related drivers are now up to date and I have the latest driver updates for my mobo.

Here's the latest dmp file if it helps:

Attachment 87118

edit: I do not have the latest July driver update for my gfx card because that particular update is what started this whole mess.

Jonathan_King · 24 Jul 2010

You say it all started when you installed the July nVidia driver? I would therefore suggest a system restore to get to a point before the troubles.

Otherwise, I have to suspect hardware.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Test hard drive: HD Diagnostic

...Summary of the Dumps:

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 23 21:00:08.223 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:04.614
BugCheck A, {7800031f5348, 2, 1, fffff8000307c4f3}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+133 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 23 20:48:11.953 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:05.250
BugCheck A, {780003243d48, 2, 1, fffff800030ca4f3}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+133 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 23 20:40:39.265 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:58.562
BugCheck 1E, {ffffffffc000001d, fffff88000000000, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
BUGCHECK_STR:  0x1E_c000001d
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 23 20:58:25.481 2010 (UTC - 4:00)
System Uptime: 0 days 0:09:33.778
BugCheck A, {78000324a5c8, 2, 1, fffff800030d04f3}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+133 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

**cluberti** · 24 Jul 2010

As usual, JK is spot on - if driver updating didn't help, and a system restore to before your previous driver update does not, start suspecting (and testing/stressing) your hardware.

Crypt135 · 24 Jul 2010

Restored back to the day before the gfx driver update, but I still got another BSOD; however, this one looks a bit different than the previous (or at least the bug check code is different).

Attachment 87234

Two or three weeks back I already ran my RAM through memtest for about three days straight with each individual stick, all of them in together, for 6 passes each, etc. and did not receive any errors or red flags.

I'm now working on testing the hard drive, but if running the diagnostic from Western Digital does not work off of a CD, I may need some assistance (my hard drives are RAIDed, and the physical drives were not even detected in the program from the regular windows download).