Solved BSODs after Mainboard and CPU Upgrade plus change to 64 bit Windows 7

[toranaboy]

I cannot get enough information online to teach myself debugging blue screens with Windbg. I get to !analyze -v and my eyes glaze over.

My tale of woe would wring tears from a needle's eye but I will spare you.

What is with my Windows 7 box? Before I rebuilt it and upped the little fellow to 64 bit, it ran like a top.

I have swapped or replaced the motherboard, hdd and psu. The RAM survived 9 iterations of memtest86+. I have experienced crashes with both the onboard and GTS 450 graphics. I have wept salt tears. I have chewed the carpet in rage

I uninstalled Daemon Tools Lite on the strength of the contents of one minidump. That was yesterday. I suppose it is at least possible that that will solve the problem since I have not had a crash since.

I attach the material from the SF diagnostic tool. I have other stuff available which I collected a la the forum sticky before having my attention drawn to the tool just before posting. For any assistance I will be pathetically grateful.

 

[Arc]

Welcome aboard.

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 1A[/COLOR], {5003, fffff70001080000, b9e, ba00000153c}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45f3d )

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

According to Carrona.org, STOP 0x0000001A: MEMORY_MANAGEMENThttp://www.carrona.org/bsodindx.html#top
Usual causes: Device driver, memory, kernel

But neither a driver nor memory is indicated in the dump. So let us start with search for a faulty driver.
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.

Also, remove the following programs...

Start Menu\Programs\GIGABYTE 
Start Menu\Programs\GIGABYTE\AutoGreen
Start Menu\Programs\GIGABYTE\ET6
Start Menu\Programs\GIGABYTE\Smart 6

And free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

 

[toranaboy]

Thanks I will report in a day or so.

 

[toranaboy]

Fresh Minidump

I attach .dmp file: 102312-36675-01.zip for your information.

 

[Arc]

According to the latest dump you uploaded, you need to upgrade the network driver:

Download the network card driver from manufactuer's website.
Then reinstall the driver:

• Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
• Double click to expand "Network adaptors".
• Right click your network card and click Uninstall.
• Check "Delete driver software for this device" check box, click OK.
• Restart the computer

If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

Let us know the situation after updating this driver.

 

[toranaboy]

Had problems with update so swapped in a newer adapter. We shall see what we shall see. Do you want any further minidumps? I have uploaded one herewith (I hope) from earlier on.

 

[Arc]

Let us know the results after swapping the adapter, coz, this dump also indicates some network problem.

You may plan to remove BitComet and see if the situation is different here or not.

 

[toranaboy]

Noted. Thanks. I'll forward my next minidump in due course

 

[toranaboy]

Further Crash

Herewith .dmp file. I have uninstalled BitComet.

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800159ca88, fffff8800abdbfc0, 0}

[COLOR=Red]Probably caused by : NETIO.SYS[/COLOR] ( NETIO!WeightCompare+8 )

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

It is network related, and you need to follow the instructions given in post #5

EDIT ..... It is D-Link Wifi LAN Card.

fffff880`0abdbdc8  fffff800`032750cb nt!ExFreeToNPagedLookasideList+0x27
fffff880`0abdbdd0  fffff880`0a8ea600Unable to load image \SystemRoot\system32\DRIVERS\Dnetr28ux.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Dnetr28ux.sys
*** ERROR: Module load completed but symbols could not be loaded for Dnetr28ux.sys
 Dnetr28ux+0x25600

Search for the updates in either http://www.ralinktech.com/en/04_support/support.php?sn=500 or http://www.dlink.com/ca/en/home-solutions/support.

 

[toranaboy]

At post #6 I uninstalled previous USB wireless LAN adapter and replaced with another much newer adapter (D-Link DWA N 150) Have now downloaded the latest driver for the 'new' adapter, uninstalled and re-installed the adapter with the latest driver. I now await the next bsod. (I hope I am doing this properly). I am, of course, following Lord Krishna's advice as per your sig

 

[Arc]

At post #6 I uninstalled previous USB wireless LAN adapter and replaced with another much newer adapter (D-Link DWA N 150) Have now downloaded the latest driver for the 'new' adapter, uninstalled and re-installed the adapter with the latest driver. I now await the next bsod. (I hope I am doing this properly).

Let us know the results there, ok?

I am, of course, following Lord Krishna's advice as per your sig

I try to follow all the times, failed once ... for one time I expected.

 

[toranaboy]

It's been a couple of days since the last crash. It seems likely that you have identified the culprit. How long do you think I should wait before pronouncing the problem solved and disabling verifier (and offering my gratitude to you of course)? Verifier is not causing any noticeable performance problems.

 

[Arc]

Disable verifier now. It is no more required there.

 

[toranaboy]

Thanks to Arc

Well, I am confident that the culprit driver has been identified. It was for the NetComm NP 545 USB wireless ethernet adapter. It must have been the change from 32 bit to 64 bit windows that exposed the problem.

Thank you Arc for your assistance. I was operating beyond my modest level of competence when I came upon the forum and I would be struggling still but for your help. I also picked up a little hindu lore which was nice. I am uncertain how to make my appreciation for your efforts known to the administrators. Please advise. Also, I would be pleased to make a modest donation to a charity of your choosing by way of thanks.

 

[Arc]

Nice to know that your system is free from the issue now.

Happy to help, nothing else is required, thanks

 

[toranaboy]

netio.sys strikes again?

There is still a problem. Some days ago I installed qBittorrent (to replace BitComet) but have done nothing else to the system.

 

[Arc]

lmvm Dnetr28ux
start             end                 module name
fffff880`06012000 fffff880`061a5000   Dnetr28ux   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Dnetr28ux.sys
   [COLOR=Red] Image name: Dnetr28ux.sys
    Timestamp:        Thu Apr 28 11:48:18 2011[/COLOR] (4DB906AA)
    CheckSum:         00193FD2
    ImageSize:        00193000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Is it the latest?

 

[toranaboy]

I have had only the one crash. I have uploaded the compressed .dmp file. It is the latest and only dump since I prematurely declared the problem solved

 

[toranaboy]

Forgot to enable Driver verifier so have done so now.