[iFargle]

Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.0.6002.2.2.0.256.1
  Locale ID:	1033

Additional information about the problem:
  BCCode:	a
  BCP1:	0000000000000004
  BCP2:	000000000000000C
  BCP3:	0000000000000001
  BCP4:	FFFFF80001AB67DE
  OS Version:	6_0_6002
  Service Pack:	2_0
  Product:	256_1

Files that help describe the problem:
  C:\Windows\Minidump\Mini101409-03.dmp
  C:\Users\Jesse\AppData\Local\Temp\WER-57470-0.sysdata.xml
  C:\Users\Jesse\AppData\Local\Temp\WER62B8.tmp.version.txt

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

Any ideas? Google didn't return much for me. The only thing I saw is that it could be my motherboard ( I do need to update the BIOS on it, but I don't have a flash drive..)

[kimsland]

Please click on Start > Run (search) > C:\Windows\Minidump
Then Zip up the Minidump: Mini101409-03.dmp to Attach here (note: the "Manage Attachments" button is located at the bottom area of the new reply window)

Please create a new reply and add the zipped up Minidump attachment to analyze

[Mak213]

STOP 0x0000000A or IRQL_NOT_LESS_OR_EQUAL

A kernel-mode process or driver attempted to access a memory location without authorization. This STOP error is typically caused by faulty or incompatible hardware or software. The name of the offending device driver often appears in the STOP error and can provide an important clue to solving the problem. If the error message points to a specific device or category of devices, try removing or replacing devices in that category. If this STOP error appears during Setup, suspect an incompatible driver, system service, virus scanner, or backup program.

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

Without the Minidump there is no way to say which driver it is.

[iFargle]

There ya go. I think I've figured it out (Here, in the other thread), but I'd like to see what you all think about it. Thanks for the help.

[kimsland]

OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap
BUGCHECK_STR: 0xA
PROCESS_NAME: digsby-app.exe
IMAGE_NAME: win32k.sys

Hmm, took me a while to get my head around on this one
looks like the fault is to do with your nVidia drivers
I would suggest uninstalling them completely then run the Driver Cleaner Tool: http://tinyurl.com/ygx3ber

Restart, then update to the newest nVidia drivers: nVidia 191.07 drivers released

Basically just driver corruption

[iFargle]

Ahh, I see. What I don't get is why Digsby is in there I've updated my drivers, I just didn't do a clean install. We'll see if this helps. Thanks.

[kimsland]

Actually the fault eventuated from having free Digsby IM open at the time
If you don't require this free App any longer, uninstall it

This is the faulting driver though: c:\windows\system32\drivers\nvlddmkm.sys
But if you delete it manually, Windows may not start

[iFargle]

I ran the cleaner. Now a cmd window opens that says

C:\NVIDIA\*, Are you sure (Y/N)? _

What do I pick here? I don't get the question

[Trotter]

Digsby is nasty. I tried it when I was with AT&T and it would kill my internet connection every time. I mean, I would literally have to kill Digsby and reboot the modem every time I opened Digsby up.

[iFargle]

This is the first problem I've had with Digsby. It's changed a little, they don't have that crappy installer anymore. And they actually let the user know that they're going to use your computer to add to their "computational engine" thingamajig.