needing help with random BSODs

[ZippoLag]

Hello there, I'm runnig a rather new (1 year old) pc, assembled it myself (I believe should be visible on my profile here).
Things were going smoothly up until december, when I started having BSODs every now and then, checked EVERYTHING, and it seemed my main hard drive was starting to fail (even tho it's new, the reallocated sector count started to grow). An then everything was fine again, no problems up until a month ago, when I started having BSODs rather regularly, most times while playing or moments after closing Battle Forge.
But now, just moments ago I was doing nothing except: livemsn chatting, writing a file on notepad, listening to music with AIMP2, and downloading some files with JDownloader. Then, just when I was about to hit "save" on notepad, sound went *brbrbrbr*, BSOD came up, dump got made, and comp rebooted.

tldr: new comp throwing up BSODs for no evident reason, please take a look at the following and point me in the right direction. Thanks.

Firma con problemas:
Nombre del evento de problema: BlueScreen
Versión del sistema operativo: 6.1.7600.2.0.0.256.48
Id. de configuración regional: 11274

Información adicional del problema:
BCCode: 19
BCP1: 00000020
BCP2: 851EC1D0
BCP3: 851EC1F0
BCP4: 08040012
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Archivos que ayudan a describir el problema:
C:\Windows\Minidump\060210-19671-01.dmp
C:\Users\Seba\AppData\Local\Temp\WER-41015-0.sysdata.xml

 

[usasma]

6 memory dumps from 13 May 2010 to the present (just over 2 weeks)
5 different STOP error codes, with 4 different causes

I would suspect a memory problem - most likely with your video card, but it could be with the mobo.
There is some mention of the hard drive also - so I'd test that:

Start with these free, bootable diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Try the next test on your video card. If there are no problems yet, then run the second test (Prime95).

Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Then, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2008 or earlier:

hcmon.sys    Mon Oct 08 11:00:31 [COLOR=Red]2007[/COLOR] - VMware USB monitor
Maestro1.sys Wed Jun 14 06:06:19 [COLOR=Red]2006[/COLOR] - Multimedia Keyboard by BTC
VMkbd.sys    Mon Oct 08 11:30:39 [COLOR=Red]2007[/COLOR] - VMware keyboard filter driver
VMNET.SYS    Fri Mar 16 06:05:31 [COLOR=Red]2007[/COLOR] - VMware Virtual Network Driver
vmnetadapter.sys Fri Mar 16 06:06:08 [COLOR=Red]2007[/COLOR] - VMware virtual network adapter driver 
vmnetbridge.sys Fri Mar 16 06:06:36 [COLOR=Red]2007[/COLOR] - VMware bridge driver
vmnetuserif.sys Mon Oct 08 11:02:25 [COLOR=Red]2007[/COLOR] - VMware network application interface driver
vmx86.sys    Mon Oct 08 10:31:16 [COLOR=Red]2007[/COLOR] - VMware Virtualization Driver
vstor2.sys   Fri Mar 23 13:02:01 [COLOR=Red]2007[/COLOR] - VMware Virtual Storage Volume Driver         
vstor2-ws60.sys Tue Aug 07 15:22:28 [COLOR=Red]2007[/COLOR] - VMware Virtual Storage Volume Driver

Summary of the BSOD:

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 15:09:27.420 2010 (GMT-4)
System Uptime: 0 days 3:32:52.030
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri May 28 22:51:03.168 2010 (GMT-4)
System Uptime: 0 days 2:04:00.778
BugCheck A, {caf00a78, 2, 1, 82effff0}
Probably caused by : ntkrpamp.exe ( nt!KeSignalGateBoostPriority+4b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon May 24 20:41:42.388 2010 (GMT-4)
System Uptime: 0 days 7:34:22.966
*** WARNING: Unable to verify timestamp for volmgrx.sys
*** ERROR: Module load completed but symbols could not be loaded for volmgrx.sys
*** WARNING: Unable to verify timestamp for ISODrive.sys
*** ERROR: Module load completed but symbols could not be loaded for ISODrive.sys
*** WARNING: Unable to verify timestamp for amdxata.sys
*** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
*** WARNING: Unable to verify timestamp for msrpc.sys
*** ERROR: Module load completed but symbols could not be loaded for msrpc.sys
*** WARNING: Unable to verify timestamp for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
*** WARNING: Unable to verify timestamp for Fs_Rec.sys
*** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.sys
*** WARNING: Unable to verify timestamp for ksecpkg.sys
*** ERROR: Module load completed but symbols could not be loaded for ksecpkg.sys
*** WARNING: Unable to verify timestamp for giveio.sys
*** ERROR: Module load completed but symbols could not be loaded for giveio.sys
*** WARNING: Unable to verify timestamp for vmstorfl.sys
*** ERROR: Module load completed but symbols could not be loaded for vmstorfl.sys
*** WARNING: Unable to verify timestamp for spldr.sys
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
*** WARNING: Unable to verify timestamp for speedfan.sys
*** ERROR: Module load completed but symbols could not be loaded for speedfan.sys
*** WARNING: Unable to verify timestamp for Null.SYS
*** ERROR: Module load completed but symbols could not be loaded for Null.SYS
*** WARNING: Unable to verify timestamp for ehdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ehdrv.sys
*** WARNING: Unable to verify timestamp for Maestro1.sys
*** ERROR: Module load completed but symbols could not be loaded for Maestro1.sys
*** WARNING: Unable to verify timestamp for VMkbd.sys
*** ERROR: Module load completed but symbols could not be loaded for VMkbd.sys
*** WARNING: Unable to verify timestamp for nvsmu.sys
*** ERROR: Module load completed but symbols could not be loaded for nvsmu.sys
*** WARNING: Unable to verify timestamp for usbehci.sys
*** ERROR: Module load completed but symbols could not be loaded for usbehci.sys
*** WARNING: Unable to verify timestamp for nvmf6232.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6232.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for nvBridge.kmd
*** ERROR: Module load completed but symbols could not be loaded for nvBridge.kmd
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for hcmon.sys
*** ERROR: Module load completed but symbols could not be loaded for hcmon.sys
*** WARNING: Unable to verify timestamp for vmnetadapter.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetadapter.sys
*** WARNING: Unable to verify timestamp for VMNET.SYS
*** ERROR: Module load completed but symbols could not be loaded for VMNET.SYS
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
*** WARNING: Unable to verify timestamp for eamon.sys
*** ERROR: Module load completed but symbols could not be loaded for eamon.sys
*** WARNING: Unable to verify timestamp for RTKVHDA.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHDA.sys
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for vmnetbridge.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetbridge.sys
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
*** WARNING: Unable to verify timestamp for vmnetuserif.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetuserif.sys
*** WARNING: Unable to verify timestamp for vstor2.sys
*** ERROR: Module load completed but symbols could not be loaded for vstor2.sys
*** WARNING: Unable to verify timestamp for vstor2-ws60.sys
*** ERROR: Module load completed but symbols could not be loaded for vstor2-ws60.sys
*** WARNING: Unable to verify timestamp for vmx86.sys
*** ERROR: Module load completed but symbols could not be loaded for vmx86.sys
*** WARNING: Unable to verify timestamp for epfwwfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for epfwwfpr.sys
*** WARNING: Unable to verify timestamp for peauth.sys
*** ERROR: Module load completed but symbols could not be loaded for peauth.sys
*** WARNING: Unable to verify timestamp for secdrv.SYS
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
BUGCHECK_STR:  0xc2_7
PROCESS_NAME:  audiodg.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri May 21 20:54:08.430 2010 (GMT-4)
System Uptime: 0 days 8:58:17.040
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BugCheck 1000007E, {c0000005, 9057de20, 8b2eff10, 8b2efaf0}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+175e20 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri May 14 01:14:24.892 2010 (GMT-4)
System Uptime: 0 days 3:01:15.486
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BugCheck 1000008E, {c0000005, 8f7bca7c, aefd4750, 0}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+181a7c )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  BattleForge.ex
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Thu May 13 19:19:25.618 2010 (GMT-4)
System Uptime: 0 days 0:25:56.227
BugCheck A, {28, 2, 1, 82e380e9}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+1ed )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe

 

[ZippoLag]

Thanks a lot, I'll run the whole batch on the weekend.

 

[ZippoLag]

OK, here's what I've got, I haven't found any problems (tho I haven't been really able to analyse the HDDs), I hope this helps narrowing down the possible causes.

malware:
panda: clean
bitfedender: clean
(I use nod32, so no wonder there weren't any problems here)

RAM:
memtest86+: no errors (17 passes, ran overnight 12 hours)

HDD:
seatools for DOS doesn't detect any drives :s
wddiag doesn't boot :/
SpeedFan SMART data on both disks:
main: S.M.A.R.T. hard disk status and hard disk failure prevention
sec: S.M.A.R.T. hard disk status and hard disk failure prevention
extra note: randomly (sometimes once a month, sometimes once week, sometimes none for a couple of months) I get an error while trying to save a file to disk (including when copying/moving a file), I states something by the lines of "cannot write the file due to lack of permissions to open the source file" (yes, I recall it sounded a bit nonsensical), I'll screenshot it if it pops again.
I'm on the process of getting the lattest Hiren's Boot CD and using whatever HDD testing software it has.

GPU:
furmark: ran for 15 minutes with no problems, temp started at 48ºC and maxed at 64ºC after 6 minutes
prime95: ran smallFFTs for 7 hours without problems, all cores at 100% all the time, 201 tests in total, core temp didn't go above 34ºC (note: didn't let me specify more than 3 torture test threads, wich I guess makes sense since I'm running a 3-core amd proccessor) while using the comp for general purposes (mostly firefox browsing, downloading updated drivers an other batch downloads)

DRIVERS:
Uninstalled old VMWare (since I wasn't using it anymore anyway)
impossible to replace or update Keymaestro software (keyboard utility)
Updated mobo and video drivers (tho they were dec/2009)

I will continue using the pc as usual and reply again with a new minidump if the error keeps popping up.

 

[usasma]

Are you using RAID? That can cause the hard drives to not be seen.

Try running the free version of HDTune from within Windows. Direct download link here: http://www.hdtune.com/files/hdtune_255.exe

If you still can't test either, disconnect the secondary drive (both cables) and see if that stops the BSOD's (and see if you can test the primary drive). I suggest this based on the screenshot of the SMART data for this drive.

 

[ZippoLag]

I tried out SeaTools for windows, it detected the drives just fine so I ran a short test on both and both passed. BTW no, I'm not using RAID.
I used the HD Tune you just gave me and scanned the drives for errors, both passed. Even still, yeah, those SMART stats kinda worry me, so I'm in the process of backing all my data up, but burning ~100 dvds is such a pain..
Thanks again.

 

[usasma]

Short/quick tests aren't very accurate - I'd suggest running the long test when you get time.

 

[ZippoLag]

I got the latest WD diagnostics to run just fine from the latest Hiren's boot cd, the main disk passed the full test without errors.
I also tried Seatools for DOS from it, but as expected, it didn't pick up any of the drives again.

I'll try the Seatools for windows's long test if you think it's neccesary, but it fills like overkill at this point.

Thanks for the help and patience.

PS: when I said I ran HDTune, I ran the long test, I didn't check the "Quick" checkbox. I ran only the quicktest on SeaTools for Windos just to see if it was working.

edit: well, overkill or not, I've just completed SeaTools for Windows long test on both drives, and both have passed.

 

[usasma]

Well, you've done everything that I can think of.
It's time to sit back and wait to see if the dump files recur.

 

[ZippoLag]

Well, I had the comp on for about 12 hours, it was working kinda "laggy" at moments, but I shrugged it off since I was multitasking heavily I was expecting one of the apps to be slow..
Anyways, trying to open PES 2010 was the last drop it seems, since as soon as I doubleclicked the shortcut bsod came up, here's the minidump.

Thanks once again.

 

[usasma]

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

[FONT=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/FONT]

 

[ZippoLag]

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]

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]

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]

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]

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.

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:

*******************************************************************************
*                                                                             *
*                        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]

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]

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]

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]

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.