Solved Non-specific BSOD

[essenbe]

Good News, I hope it works out well for you. Just tell Microsoft, your Motherboard died. Just wait awhile to make sure that's what the problem was. Let us know.

 

[toranaboy]

A New Motherboard and different BSODs

A person could get discouraged I had hoped for a cure, or at least the same problem and the motherboard excluded. What in heaven's name is going on now? If I had spent my time flipping burgers for McDonalds instead of working on this blasted machine I could have got me a fine shop-bought 'puter, and pride go hang. You blokes heard of fellow named Job?

And, for your delectation and delight: minidumps etc.

Yours despondently

Jim

 

[essenbe]

Jim, are you running on board graphics?

Before you do this create a system restore point. http://www.sevenforums.com/tutorials/697-system-restore-point-create.htmlThen I want you to leave it on for 24 hours of use. Don't just let it idle, use it. Do whatever you want. Play a game, watch you Tube Videos, watch a movie, whatever you want, just put it through it's paces. It will seem a little slow and lag a little. That's normal. Verifier puts stress on the drivers and tries to make them crash in order to identify which one is the trouble maker.

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

   Information

What is Driver Verifier:
It puts stress on the drivers, and therefore it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How we know that DV is enabled:
It will make the system bit slow and sluggish.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there are no Restore points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

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

 

[essenbe]

BTW, Yes, I know of Job quite well. Just be thankful you are only dealing with a computer and not what Job had to deal with. But, I understand the frustration very well too. Been there, Done that.

 

[toranaboy]

I am using on-board graphics. I have run the intel update utility. Verifier good to go, and I will run a program called HeavyLoad to impose and artificial load on the pc when I'm not around. I will restart after posting this. I will check in again tomorrow; wish me luck

 

[essenbe]

Good luck, my friend. I hope it tells us what we need to know.

 

[carwiz]

Windows Update keeps failing due to a corrupt WcpStore.
Radar Preleaks are being reported "out the kazoo".
Appcrash is being reported on just about everything that runs.
Even Prefetch is failing.

There's so many questionable add-ons to this "new install", I don't know where to start debugging except with a Clean Install and audit every addition made to the system. It's still looking like a drive problem but there could be a faulty shell extension or Daemon tool causing file corruption.

Besides the motherboard drivers, Windows Update MUST complete before adding ANYTHING! Once the system is up to date and stable, create a restore point then add ONE item at a time and audit stability.

Forgot to mention:
Before shutting down to re-install, run TDSSKiller to make sure there's no root kits installed. A clean install will not remove those.
Get TDSSKiller from here: http://support.kaspersky.com/viruses/disinfection/5350

 

[essenbe]

Ken, he ran a 'clean all' before the install. That would get rid of a root kit wouldn't it?

 

[carwiz]

That should have cleaned the disk if the "all" parameter was used; Otherwise it would not.

Added: It should be done again!

The more I think about, perhaps it won't. If you read the specs on clear all, it clears partitions. BUT... some root kits will store themselves outside of a Windows partition. The TDSSKiller does direct disk I/O and looks at the disk, not at partitions per say.

 

[essenbe]

He did the clean all command, see post # 35 (http://www.sevenforums.com/bsod-help-support/328341-non-specific-bsod-4.html#post2847545) But it wouldn't hurt to run the TDSSKiller and do another Clean all.

 

[carwiz]

I think it would be wise to run it. As you say, can't hurt.

 

[Layback Bear]

Just for information.

**A install using a Clean All should of wrote the disc/partition to zeros. That is the good news.

**Their is also bios infection out and about on the web.

**If Jim copied over anything for the old install without running scans on them first the infection could of came with the copy process.

 

[toranaboy]

No problems reported by TDSKiller. I have a linux box with a new-ish 2TB drive. I will switch that disk in and do a clean install as before.

 

[toranaboy]

Verifier Pays Off

I skipped the clean install and just installed Win 7 over good ol' linux Mint. I fired up verifier after deleting an On/Off iPhone thing which came with the motherboard and caused a crash. That was at nine hours ago. I just had a BSOD starring dxgmms1.sys (it seems). I have uploaded the sf diagnostic tool file. I leave it in the hands of you mavens. I thought it must be something to do with Directx, but then what would I know?

 

[carwiz]

How did all that crap get loaded again? Uninstall the last software you installed or roll back to the restore point you created after Windows Update completed.

BugCheck 50, {ffffffffffffffd0, 1, fffff80002c96dac, 0}
Unable to load image \SystemRoot\system32\DRIVERS\AppleCharger.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AppleCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
Could not read faulting driver name
Probably caused by : AppleCharger.sys ( AppleCharger+1a93 )

 

[toranaboy]

Be the crap king I suppose Doing as you suggest now, to windows update restore point.

 

[essenbe]

Jim, both dump files were on 8-24 and both blamed AppleCharger. You shouldn't use the Disk that came with the motherboard. It is not needed at all. Go to the Motherboard's web site and download the drivers you need. Only use the most recent drivers. Be sure you get the newest Chipset driver and the Lan driver. You will also need the USB 3.0 drivers and any other drivers you want. Put them on a USB flash drive and install the drivers after the install.

I would like Ken (carwiz) to look at this and know what he sees.

Seems I'm slowing down in my old age. Ken's already been here and beat me to it.

 

[toranaboy]

Wilco. I thought I uninstalled that pesky applecharger thingie. grr. Why if I get my hands on that Steve Jobs I'll...

 

[toranaboy]

It's taking a while to d/l those fresh motherboard drivers. I have to hit the hay. I imagine you gentlemen have a bit of time left in your weekend and I wish you a comfortable time of it if I may. I'll be in touch.

Regards,

Jim

 

[carwiz]

I was just checking email while waiting for breakfast when this thread popped up.

Breakfast is ready... BBL.