needing help with random BSODs

usasma · 14 Jun 2010

DirectX errors in the stack text - I think it's time to look at a new video card
Either borrow one that you know is good - or purchase one that you can return (if it turns out that the video card isn't the problem).

But first, this older driver is still present: Maestro1.sys Wed Jun 14 06:06:19 2006
Please go to C:\Windows\System32\drivers and renam Maestro1.sys to Maestro1.BAK
Then reboot and see if you get further BSOD's.

If still getting them, then it's time for another video card.

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jun 14 17:10:27.223 2010 (UTC - 4:00)
System Uptime: 0 days 9:37:29.833
BUGCHECK_STR:  0x4E_7
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

ZippoLag · 15 Jun 2010

Sigh, that KeyMaestro thing is an app for my keyboard, I really didn't want to get rid of it but well, off it goes..
So you think it's the video card.. I'll try just without that driver for the moment.
Should I also update DX just in case?
Also, could it be not something else? If problems keep arising, I don't have means to get another card to try (they are quite expensive over here, even the "cheap" ones, and my current card was actually quite a big investment and I was hoping for it to last several years).
Let's hope bsods go away along with the driver still, if they don't.. I'll come back again.

Thanks again, laters.

usasma · 15 Jun 2010

I suspect the video card - but that doesn't mean it's 100% sure (especially since there wasn't any issues with Furmark or Prime95).
Removing the KeyMaestro is only temporary - you can put it back on once we've finished troubleshooting.

In short, we try all the free stuff first - but if it doesn't fix it, then we've gotta try other things.
I can't recall, have you reinstalled the drivers for your video card? If not, that's the next step
After that we'll look at backing up your stuff and then reinstalling Windows.

ZippoLag · 16 Jun 2010

yup, I updated all the drivers after the checks ran ok on my second post.

Maybe is just some sort of obscure windows bug floating around, they have a tendency to pop up only for me (it may soun supersticious or nonsensical, but I have a history of sitting down on perfectly fine comps and they will pop a bsod, since I was little, caused many people to hate me, I call it "the touch").

ZippoLag · 27 Aug 2010

Well, it definately seems it was that keyboard driver, I shall explain:

after removing it, I didn't have any more BSODs, tho the system had become a tad unstable, concluding this was happening only in my session I created another user account, wich performed flawlesly, until I tried to install once again the keyboard driver. Then, the next day I got a blue screen while shuting down the computer.
So, I've uninstalled for good the driver, but just in case, would you mind to take a look at the minidump please?

thanks a lot for everything :)

**Capt.Jack Sparrow** · 27 Aug 2010

Hello,

The Dump are pointing to your Video drivers maybe it's just a false postive. If the crash happen after trying to install the Keyboard driver then if it's working fine just leave it alone. If your have problems see if you can get a Temp keyboard for testing purpose.

Code:

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Try these steps as well. Update the Network driver : NVIDIA DRIVERS 15.25 WHQL
Follow this article and Update the nVidia driver nVidia Driver Cleanup Guide !! « Captain Debugger

Bugcheck:

Code:

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 905114a3, The address that the exception occurred at
Arg3: a9545724, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
nvlddmkm+ff4a3
905114a3 8b480c          mov     ecx,dword ptr [eax+0Ch]

TRAP_FRAME:  a9545724 -- (.trap 0xffffffffa9545724)
ErrCode = 00000000
eax=21767000 ebx=00000000 ecx=a9545874 edx=872c69b8 esi=a9545910 edi=00000000
eip=905114a3 esp=a9545798 ebp=a9545868 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nvlddmkm+0xff4a3:
905114a3 8b480c          mov     ecx,dword ptr [eax+0Ch] ds:0023:2176700c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  msnmsgr.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 90514b72 to 905114a3

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
a9545868 90514b72 86f6c438 21767000 872c6b08 nvlddmkm+0xff4a3
a95458dc 904aa0bd a9545910 a9545910 904aa08d nvlddmkm+0x102b72
a95458f0 904ab8ae a9545910 853ec878 a95459a8 nvlddmkm+0x980bd
a9545900 9044b80e a9545910 853ec878 c1d000d1 nvlddmkm+0x998ae
a95459a8 9044dc17 cafe0053 853ec878 872c6b08 nvlddmkm+0x3980e
a95459c8 90430148 872c6b08 867f5000 853ec878 nvlddmkm+0x3bc17
a95459f0 9090488a a9545a9c 8321b6ee a9545a9c nvlddmkm+0x1e148
a9545a08 90907c7f 9090485f a9545a9c a9545a44 nvlddmkm+0x4f288a
a9545a18 90d57779 853ec878 a9545a9c 8a71e008 nvlddmkm+0x4f5c7f
a9545a44 90d56514 853ec878 a9545a9c 8a71ea40 dxgkrnl+0x25779
a9545abc 90d54481 00000000 00000000 8a3fd388 dxgkrnl+0x24514
a9545ae4 90d5695e 00000001 00000000 00000000 dxgkrnl+0x22481
a9545b08 90d56b4e b23cfe40 00000001 b239f848 dxgkrnl+0x2495e
a9545b64 90d57594 a9545b98 00000001 39809ffc dxgkrnl+0x24b4e
a9545d28 82e4944a 000de144 000de168 778b64f4 dxgkrnl+0x25594
a9545d28 778b64f4 000de144 000de168 778b64f4 nt!KiFastCallEntry+0x12a
000de168 00000000 00000000 00000000 00000000 0x778b64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+ff4a3
905114a3 8b480c          mov     ecx,dword ptr [eax+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+ff4a3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5ce288

FAILURE_BUCKET_ID:  0x8E_nvlddmkm+ff4a3

BUCKET_ID:  0x8E_nvlddmkm+ff4a3

Hope this helps,
Captain

ZippoLag · 28 Aug 2010

I think I know what's causing it.
You see, this keyboard driver, when you use any of the special functions on the keyboard, it displays a small rectangle on the bottom of the screen showing what's been pressed. I've noticed that on certain games, when ran in fullscreen mode, the whole screen goes black when that little rectangle is supposed to appear.
If we put that toghether with the fact that I've had no blue screens in the 2 months without the driver, I think that just gotta be it.

**Capt.Jack Sparrow** · 28 Aug 2010

ZippoLag said:

I think I know what's causing it.
You see, this keyboard driver, when you use any of the special functions on the keyboard, it displays a small rectangle on the bottom of the screen showing what's been pressed. I've noticed that on certain games, when ran in fullscreen mode, the whole screen goes black when that little rectangle is supposed to appear.
If we put that toghether with the fact that I've had no blue screens in the 2 months without the driver, I think that just gotta be it.

Well that's good. Test with a different keyboard and see if that fixes it. If not get a new one that has compatible Windows 7 drivers.

Good Luck,
Captain

ZippoLag · 29 Aug 2010

meh, I think I'll just keep on using it, I miss having a scroller wheel at the disposal of my left hand, but other than that there's no drawback of not using the drivers.

So until another blue one indicates me it's not the driver, I shall keep this thread sleeping.

Thanks for all.

ZippoLag · 26 Sep 2010

Well, hello again.
Today I found my old webcam with it's drivers and I decided to give it a try.
Things were running smoothly until I turned on a "Face Tracking" feature on the capture options and got a BSOD.
After reboot I tried everything else and things were fine again, then attempted to use said feature again and got another BSOD.

So, it's pretty obvious it's the drivers fault (posibly just the program that I was using for the video capture), but just-in-case I come here with both minidumps.