Multiple BSOD errors on brand new build.

[nash0033]

A few weeks ago i build an entire new gaming desktop. At first all was fine but recently i started getting different blue screens.

The errors i have gotten are
0x000007e
0x000001e
0x0000050

I have run 8 passes of memtest86+ with no errors. Attached are a zip of my dmp files.

Thanks.

 

[Arc]

Welcome aboard.

upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

From your recent crashes, we can say that those are drive related. Update your display driver (I got an nvidia update today) update the audio driver, too!


And, http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html



Let us know the results.

 

[nash0033]

Thanks for the reply.

Indeed i seem to need some driver updates. I still have attached the MSINFO32.nfo if drivers are not the only issue. I assume its the problem though.

Thanks again

 

[nash0033]

Progress

So after a thorough driver update, I continue to keep BSODs, possibly more often even, but none of them the same errors as before. The errors are all over the place. Attached is my recent dmp files.

Thanks

 

[Arc]

First of all, you need to uninstall Daemon tools.

Then, get back to the earlier version of the nvidia display driver.

Let us know the results.

 

[nash0033]

After uninstalling daemon and reverting nvidia drivers I am still getting bsod. Once back to back with different errors. Attached are more dmps.

 

[Arc]

It is a STOP 0x000000C2: BAD_POOL_CALLERhttp://www.carrona.org/bsodindx.html#top
Usual causes: Device driver, ?Memory

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[nash0033]

After enabling the verifier and going to class, i came home to an endless loop of BSOD. Here are my 5 most recent DMP files. I am not sure how many you need.

Thanks for the help

 

[Arc]

All the last five ....

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {40, 0, fffff9800b2ccc70, 0}

*** WARNING: Unable to verify timestamp for ndisrd.sys
*** ERROR: Module load completed but symbols could not be loaded for ndisrd.sys
[COLOR=Red]Probably caused by : ndisrd.sys[/COLOR] ( ndisrd+2716 )

Followup: MachineOwner
---------

Get the update from either MioNet| Your personal private network for PC remote access, webcam access software, backup, and file sharing or NT Kernel Resources: Windows Packet Filter Kit, based on your system.

Is there any particular reason that you haven't installed sp1?

[COLOR=Red]Windows 7 Kernel Version 7600 MP [/COLOR](4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.21315.amd64fre.win7_ldr.120830-0333

Before reporting it back, install SP1 and all the updates.

 

[nash0033]

So after installing sp1 and whatnot, i have been getting less frequent bsods, until today. Mostly 07e errors but not only. Ive added the most recent DMPs.

Thanks

 

[x BlueRobot]

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

Probably caused by : [COLOR="red"]hardware [/COLOR]( nvlddmkm+1b0941 )

Image name: nvlddmkm.sys
    Timestamp:        [COLOR="Red"]Thu Aug 30 16:50:16 2012[/COLOR] (503F8BB8)

Driver Reference Table - nvlddmkm.sys

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

Have you tried installing an older graphics card driver?

I would also run:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[Layback Bear]

Just a thought. Check and see what drivers the manufacture of your card suggest.
Example: My Nvidia card is made by MSI and I use MSI website recommendation. Recommendations off the Nvidia website don't work.