Varied BSODs, Drivers/Memory

Code:

fffff880`0949a2d8  fffff880`0f212fdcUnable 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
 nvlddmkm+0x1cafdc

2nd from last dmp points to a video display driver problem....keep trying the list that Arc recommended.

Last dmp points to memory corruption. Since you say MemTest86+ shows no error, then it would appear the fault must lie with the motherboard.

It wouldn't hurt to try different memory if you can get it. A member I'm helping changed his RAM sticks that tested good with memtest and his system finally calmed down. Knock on wood Attachment 303837

Seems his RAM wasn't compatible with his MB. Do you have this? Computer memory upgrades for ASRock Z87 Extreme3 Motherboard from Crucial.com Guaranteed-compatible upgrades for your ASRock Z87 Extreme3.
Click on "Show all compatible computer memory" for an expanded list then run the blue slider back from 32GB to 8GB. You can also get it to show single or 2-piece kits.

For this MB? ASRock > Z87 Extreme 3 | Memory List I can't find any listing for Crucial Ram even though Crucial says it's guaranteed to work....

And if its one 8GB stick, I haven't explored the possibilities if the ram would run better in one slot or another or if you have matched pairs, and the MB would prefer matching slots.

One item that help the other member I'm helping is he cleared his CMOS. This will give you an idea: Bios-cmos-reset - How to reset the CMOS? - biosflash.com but you should find, and use the proper procedure in your MB manual.

Your welcome.

Okay on the two sticks, the strangeness could be that crucial is in the business of selling ram and asrock sells mb's therefore crucial has more desire to test ram for various boards than asrock has to test its mb against various ram designs.

If you can't find different ram to test it may be pointless to continue, maybe a local shop could loan/rent you some.
Now how are you going to get a single stick to span both dimms? couldn't resist. I don't see the harm in running memtest on one stick at a time it depends if your machine will boot up or not on one stick. You might have to move the one stick to different slots, though I'd start with slot one first. Movem' around test all configurations.

You will have to create a matrix to cover all the combinations of ram to slots and if your board holds true to form it may require one stick to remain in slot 1 in order to boot, if that's the case leave stick a in slot one while you test stick b in the other three then just reverse the sticks and re-run the testing. At least try to run without a stick in slot 1 and see if it will boot if it does then you can go all over the place.

Your error is: Event ID 10 is logged in the Application log after you install Service Pack 1 for Windows 7 or Windows Server 2008 R2 with a possible fix-it.
This Vista version explains it better: Fix: "This device cannot start" Code 10 error in Device Manager in Windows read it, but don't run it use the one above for Win7.

More: Error codes in Device Manager in Windows | Error #10

Agreed; Follow through on Arc's suggestion and Golden's reinforcement of trying those nvidia drivers.

Crash on boot, couldn't reference memory? Could be the memory make an effort to find different ones.
The WerFault error could be related to the nvidia drivers, keep trying different ones to see if the error replicates. I refer you to: WerFault.exe error?

I don't see any .dmp attachment it may help to see what caused the WerFault error.

A question only you can answer; How knowledgeable is your friend, do you trust him or her? You may end up with new problems and have to start a new thread or you may not, at best it's a 50/50 chance.

If you think its drivers you could try this route: Installing and updating drivers in 7

AutSamurai said:

..... I might as well note my friend is highly pressuring me to reinstall Windows. He's sure I have driver issues.

Hi, I'm just stopping in to amplify your quote above. It is sort of hidden below the screen shot.

Don't let my post distract you from following advice provided by other members, mine is a notation only.

Sometimes when battling an issue on a machine, you have to consider the time invested and the time to resolve. I've spent too much time on my own machines trying to find the one thing that will fix the issue. Eventually I start over with a Clean install - very basic, install my network drivers, and let Windows Update everything including most drivers in the optional update offers.

I don't change anything for about a week to make sure the base system works well. Then slowly I might start making changes one at a time to see how I can improve my system. If something breaks in the process, I have a good idea what broke it and can roll back the last thing changed.

I think your friend gives you some sound advice.

Good luck what ever you decide.

Bill
-

Good counterpoint Bill.

Aww...Don't be so hard on yourself, just the other day I had to recheck my tool box three times before I actually saw the tool I was looking for.


Your .dmps point to Memory Management (0x1a) and, IRQL_NOT_LESS_OR_EQUAL (0xA)
With 0x1a, Argument 1:

Code:

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8004aeca10
Arg3: 000000000000ffff
Arg4: 0000000000000000

Refers to:

0x41790
A page table page has been corrupted. On a 64 bit version of Windows, parameter 2 contains the address of the PFN for the corrupted page table page. On a 32 bit version of Windows, parameter 2 contains a pointer to the number of used PTEs, and parameter 3 contains the number of used PTEs.

For 0xA:

Code:

*******************************************************************************
*                                                                             *
*                        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: 0000000000000021, 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: fffff80002cfb670, address which referenced memory

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Now that we have the technical explanation out of the way, and from your discovery it's easy to speculate that with the loose connection, when you started your machine the operating system (OS) was looking for a graphics card that it knew was there because it could see the card's drivers - think memory -, but now its not?!?

Your earlier blue screens were a symptom and grew worse until it affected the startup sequence causing the BSOD.

It sure would of been nice if you found that clasp issue and tested before you applied the code10 fix and reset the CMOS, but there's nothing in those two that will cause any harm.

Keep an eye on it and report back like you said, if your happy after a while please come back to mark your thread solved to help other members that may have a similar problem.