Three BSODs within the past few days

[icefall5]

Hello! I have had three crashes within the past few days, and each has cited a different file as the cause. I'm not really sure what to do. I did not do anything new or different when this started--no drivers were updated, no new programs, nothing. I am fully up-to-date on my Windows and driver updates.

Steps I have tried:

• Ran memtest86+, no errors were found.
• Was running the latest stable release of my graphics driver (314.07), upgraded to the latest beta release (314.21) to try to fix--did not help.
• Ran sfc /scannow, it found no errors.

I'm not sure what else to do. Any help would be greatly appreciated!

 

[Pauly]

Your errors seem to be gfx related, first step IMO would be to uninstall all gfx drivers run http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html then reinstall new drivers

Get temp monitoring software if you dont already and run http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html whilst checking temps should give you an idea if your card is OK

Any more dumps after this and post back with new files

 

[icefall5]

I completely reinstalled my graphics driver (used DriverSweeper and selected Clean Installation when reinstalling), and I ran FurMark. My GPU temperature leveled out at 61°, and I saw no artifacts. The log is attached in case anything useful can be gleaned from it.

 

[icefall5]

Had another BSOD. New dump is attached. Error was IRQL NOT LESS OR EQUAL.

 

[Pauly]

Can draw anything conclusive from that last dump but it is still complaing about nvidia drivers

 

[icefall5]

Just had another BSOD, this one's attached.

 

[Pauly]

Exactly same as before blames nVidia drivers

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff88047ec5000, 1, fffff88005215243, 5}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+18b243 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88047ec5000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88005215243, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
 
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001ec3100
GetUlongFromAddress: unable to read from fffff80001ec31c0
 fffff88047ec5000 Nonpaged pool
FAULTING_IP: 
nvlddmkm+18b243
fffff880`05215243 890491          mov     dword ptr [rcx+rdx*4],eax
MM_INTERNAL_CODE:  5
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  dwm.exe
CURRENT_IRQL:  0
TRAP_FRAME:  fffff88002dabe60 -- (.trap 0xfffff88002dabe60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000003f3a01 rbx=0000000000000000 rcx=fffff88007800000
rdx=00000000101b1400 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005215243 rsp=fffff88002dabff0 rbp=fffff88002dabff0
 r8=fffffa8007860368  r9=00000000406c5000 r10=0000000000000012
r11=fffff88002dac060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po nc
nvlddmkm+0x18b243:
fffff880`05215243 890491          mov     dword ptr [rcx+rdx*4],eax ds:fffff880`47ec5000=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80001d07673 to fffff80001c8ac40
STACK_TEXT:  
fffff880`02dabcf8 fffff800`01d07673 : 00000000`00000050 fffff880`47ec5000 00000000`00000001 fffff880`02dabe60 : nt!KeBugCheckEx
fffff880`02dabd00 fffff800`01c88d6e : 00000000`00000001 fffff880`47ec5000 fffffa80`070ca900 fffffa80`07860000 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`02dabe60 fffff880`05215243 : fffff880`02dac050 fffff880`05291661 fffff880`02dac630 fffffa80`07860000 : nt!KiPageFault+0x16e
fffff880`02dabff0 fffff880`02dac050 : fffff880`05291661 fffff880`02dac630 fffffa80`07860000 fffffa80`07860368 : nvlddmkm+0x18b243
fffff880`02dabff8 fffff880`05291661 : fffff880`02dac630 fffffa80`07860000 fffffa80`07860368 00000000`406c5000 : 0xfffff880`02dac050
fffff880`02dac000 fffff880`02dac630 : fffffa80`07860000 fffffa80`07860368 00000000`406c5000 fffff880`003f3a01 : nvlddmkm+0x207661
fffff880`02dac008 fffffa80`07860000 : fffffa80`07860368 00000000`406c5000 fffff880`003f3a01 fffff880`02dac060 : 0xfffff880`02dac630
fffff880`02dac010 fffffa80`07860368 : 00000000`406c5000 fffff880`003f3a01 fffff880`02dac060 00000000`00000000 : 0xfffffa80`07860000
fffff880`02dac018 00000000`406c5000 : fffff880`003f3a01 fffff880`02dac060 00000000`00000000 00000000`406c5000 : 0xfffffa80`07860368
fffff880`02dac020 fffff880`003f3a01 : fffff880`02dac060 00000000`00000000 00000000`406c5000 00000000`003f3a01 : 0x406c5000
fffff880`02dac028 fffff880`02dac060 : 00000000`00000000 00000000`406c5000 00000000`003f3a01 00000000`00000040 : 0xfffff880`003f3a01
fffff880`02dac030 00000000`00000000 : 00000000`406c5000 00000000`003f3a01 00000000`00000040 fffff880`02dac0a0 : 0xfffff880`02dac060
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nvlddmkm+18b243
fffff880`05215243 890491          mov     dword ptr [rcx+rdx*4],eax
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nvlddmkm+18b243
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  51427b3c
FAILURE_BUCKET_ID:  X64_0x50_nvlddmkm+18b243
BUCKET_ID:  X64_0x50_nvlddmkm+18b243
Followup: MachineOwner
---------
0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0508a000 fffff880`05b35000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Mar 15 01:37:00 2013 (51427B3C)
    CheckSum:         00A8D47C
    ImageSize:        00AAB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You could try roling back to an older driver that worked for you 306.97 is a good one, avoid the one dated dec12/jan13

Do you have another machine you can try the vid card in or another card to try in this machine or onboard gfx you can use for testing ?

 

[icefall5]

I do have onboard graphics I can try if needed, although I'd really like to avoid that if possible. Just yesterday and today I got two new dumps which are attached. Anything new from these ones?

 

[Pauly]

Did you try rolling back the gfx driver ? i only suggested onboard gfx as a test not a permanent solution

One dump wont load other blames memory/driver problem, did you let memtest run for multiple passes ?
You could also do a check on HDD Hard Drive Diagnostic Procedure using something like SeaTools | Seagate

Another option would be to enable driver verifier to try to flush out any faulting driver
http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[icefall5]

Alright, I went several rounds with Galaxy tech support and they concluded that it's not a GPU issue. I had three more BSODs; the dumps are attached. Below is a recap of what I have tried.

• Memory (2x4GB Corsair Vengeance 1600 MHz)
  • Ran memtest86+, returned no errors
  • Ran RAM test in PassMark, no errors
• GPU (Nvidia GTX 650 Ti)
  • Logged GPU temperature up to BSOD, was normal
  • Ran both PassMark and FurMark, neither returned any errors
• CPU (AMD Athlon II X4 645)
  • Ran PassMark CPU test, no errors
  • Tracked CPU temps up to BSOD, temps were normal
  • Rolled back graphics driver to a version recommended by the Nvidia forums, BSODs continued
• General
  • No malware or viruses on my system (scanned with MSE Prerelease and Malwarebytes)

 

[Pauly]

Im going to ask some others BSOD members to have a look at your dumps

 

[x BlueRobot]

[COLOR="Red"]BugCheck A[/COLOR], {fffff38000000014, 2, 0, fffff80001c9ba3c}

Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+24c )

A driver has attempted to access a invalid memory address at a IRQL level was too high, the CPU can't halt the process since the scheduler is turned off at DISPATCH_LEVEL. Any request from lower levels are blocked by the CPU. Page faults are also illegal operations here.

0: kd> [COLOR="SeaGreen"]lmvm Rt64win7[/COLOR]
start             end                 module name
fffff880`05cde000 fffff880`05dad000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        [COLOR="red"]Mon Mar 04 07:25:55 2013[/COLOR] (51344C83)
    CheckSum:         000D1FB8
    ImageSize:        000CF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Realtek RTL8168D/8111D driver is slightly outdated (latest version26/3/2013), please update it from here:

• Realtek

0: kd> [COLOR="SeaGreen"]lmvm nvlddmkm [/COLOR]
start             end                 module name
fffff880`05019000 fffff880`05ac4000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="Red"]Fri Mar 15 01:37:00 2013[/COLOR] (51427B3C)
    CheckSum:         00A8D47C
    ImageSize:        00AAB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Version: 314.22
Release Date for Desktops and Notebooks : March 25th 2013
In Device Manager: 9.18.13.1422

The latest WHQL driver is the 25th March, this has been tested by Microsoft for stability and compatibility, and should not cause any problems.

• http://www.sevenforums.com/graphic-cards/602-latest-nvidia-forceware-video-drivers-windows-7-a.html

 

[icefall5]

I stopped having issues for a few days, so I hoped they were done. That's not the case. I had another one tonight, so I uninstalled everything NVIDIA-related and went to the Windows Update version of the driver. After I restarted the computer from that installation and started typing this post, I had ANOTHER BSOD. I've completely re-run the SF Diagnostic Tool, and the results are attached. The new dumps are there.

Also, to clarify, I was running NVIDIA version 314.22 when all of the issues occurred. I jumped around between versions for a few days to check; I must've run the initial diagnostic tool for this thread when I had an older version.

It'll show my graphics card as being way out-of-date; that's because the Windows Update version is 311.06. I'm currently upgrading it to the beta version 320.00 in the hopes that it will miraculously be fixed in that version, and that process will be completed by the time anyone reads this.

EDIT: The situation has apparently reached the critical point: just had a third BSOD while updating to 320.00. That dump is attached. I managed to dig out my old GPU (I thought I had brought it home from college); I'll be reinstalling that after typing this post to see if that fixes the issues. No problems found in the Event Viewer (I checked the System log).

 

[x BlueRobot]

[COLOR="Red"]BugCheck A[/COLOR], {fffff38000000014, 2, 0, fffff800020c6a3c}

Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+24c )

The files aren't revealing much, apart from a Page Fault which shouldn't have happened, the BSOD then occurred straight after this.

Report back the results of changing the drivers and the graphics card.

 

[icefall5]

Just got back to my computer and found yet another one. This one blames a new file -- amd_sata.sys. Apparently it's not the new GPU causing the problem. Hopefully this helps pinpoint it further!

 

[x BlueRobot]

amd_sata.sys is linked to your AMD SATA ACHI driver, check for updates from here:

• AMD Support & Drivers

 

[icefall5]

Switched back to the Microsoft AHCI driver, still blue screened. I don't know if I'll be able to fix this. I've checked my RAM, my GPU, the OS itself, everything. Do I have no option other than a clean install at this point?

 

[x BlueRobot]

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[icefall5]

It made my computer run VERY slowly (as it's intended to do), and it finally crashed. This dump is attached. Does the verifier put information anywhere else that I need to upload?

EDIT: Had two more, they're attached.

 

[x BlueRobot]

The BSODs all pointed to Stop 0xA:

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r