Keep getting BSODs, can't find the cause

esha · 03 Jul 2010

Just recently I've switched from Win7 32bit to 64bit. Never had any problems under 32bit, but with 64bit I keep getting BSODs.

I've tried to change some components (new processor, new video card, new RAM), checked to make sure that all drivers are up to date - didn't help. I've unplugged any hardware I don't need urgently. I don't really know what else I could change.

The BSODs happen randomly. Sometimes when starting a program, sometimes when doing 3D renders, somtimes just when browsing the Web. I really can't find a pattern there. I also tried re-installing Windows, that didn't help either.

The BlueScreenView tool tells me that there is a problem with the ntoskrnl.exe but I can't really believe that. Until the BSOD everything runs smoothly.

I've tried the driver verifier but I don't really know how to use it.

I've attached the minidumps, perhaps you could help me with that?

Tews · 03 Jul 2010

Your .dmp file points to memory corruption as the reason for your crash..

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.

Let us know if you need help with this...

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 114a61, 1, 18f6e1}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner

These drivers are old and should be checked for replacements

Code:

wacommousefilter.sys Fri Feb 16 13:12:17 2007 
akshhl.sys Fri Jul 20 05:30:59 2007

esha · 03 Jul 2010

Thanks, I've just burned the CD and I'll run Memtest during lunch.

About the drivers: I've no idea what to do about them.
I do have a Wacom tablet, but I've installed the latest driver for it and I don't use a Wacom mouse, only the pen. So I don't know where this old wacommousefilter.sys comes from.

The akshhl.sys must be related to a certain software I use (its dongle needs a special driver) but also for that I've downloaded the latest driver. It said on the homepage that it was for Win7. And other users confirmed that it was working fine with Win 7.

I don't know how to get updates for single drivers. Any hints?

ttran · 03 Jul 2010

wacommousefilter.sys is your Wacom(tablet) Mouse Filter;
Wacom Hardware Drivers

You should update the driver that use it (akshhl.sys), don't update akshhl.sys it self.

Please run the memtest, if you get error, run single stick of ram to find a good one, then test it on different slots to find which slot on motherboard are bad (possible).

Regard,

Tuan

esha · 03 Jul 2010

Ok, I've kept the memtest running for nearly 11 hours, 5 passes as you said.
No errors were found.
But I noticed that the RAM sticks are from different manufactures. I have 2 sticks with 2048 called Hynix and 2 sticks with 1024 from MDT. Could that be the cause?

And another thing: These old driver files are all I get, even with the new installation packs. There doesn't seem to be a newer version. And I'm not even sure if Windows really uses them. Should I rename the files in question and see what happens?

ttran · 04 Jul 2010

Please upload new dmp file if you have
Also, It never hurt to run Memtestx86 for more than 5 passes, run it at least 7 passes together...If you found error...run it individually on each ram stick....if both ram stick are good...try to test one stick on different slot to find a bad one...If all slots are good...-->probably compatibility issue

I don't recommend to remove them completely, because they might corrupt your system
Here is some information I found when googling, see if you can update it:

Akshhl.sys with description AKSHASP HL Device Driver is a driver file from company Aladdin Knowledge Systems Ltd. belonging to product Aladdin HASP HL Function Device Driver.

Regard,

Tuan

Jonathan_King · 04 Jul 2010

I suspect your outdated ASACPI.sys driver is the cause. Please install the latest ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit for your motherboard here: ASUSTeK Computer Inc.-Support-

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)

If the BSODs persist, please post back and we'll go from there.

esha · 04 Jul 2010

Well, I'm running Win7 32bit on the same computer (just booting from a different harddisk) and don't have any BSODs there. Only on 64bit. So if it really is a RAM error it can only be in those portions which aren't used by the 32bit system. Can I somehow find out which RAM sticks those are and exclude them from the memtest so it runs faster?

And another stupid question here:
How do I find the correct driver for my motherboard? Can I somehow find out what type it is?

I started the automatic search utility on the Asus homepage, and I got many different categories which each contain some files for download (see screenshot). Which one should I get? All of them?

ttran · 04 Jul 2010

And another stupid question here:
How do I find the correct driver for my motherboard? Can I somehow find out what type it is?
I started the automatic search utility on the Asus homepage, and I got many different categories which each contain some files for download (see screenshot). Which one should I get? All of them?

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it

Wait for another BSODs, if it is still memory issue, we will go from there

Regard,

Tuan

esha · 07 Jul 2010

Since I was on a deadline with a project I didn't want to lose another day to the memtest tool. I had the RAM sticks replaced, and that was it. I've been using the system daily, and no blue screens anymore during the last 4 days. So I'd say it's fixed - and I hope it stays fixed *g*

Thanks for analyzing the dump for me, so I knew what to replace. Wish I had found your forum earlier, it would have saved me getting a new graphics card (because at first I thought that was the culprit).

:)