Recent varied BSOD crashes

ColinN · Sep 27, 2010

Hi all,

Could you take a look at the two recent crashes in this please? (23rd and 27th September)

My PC has worked perfectly for a year with the configuration listed on my profile, barely any problems whatsoever but in the last week or two I have had some strange behaviour (as well as the two BSODs mentioned above).

-A few random application crashes which haven't happened before.
-Windows thought it was a fake copy for some reason and needed re-activating.

I've got Windows 7 Pro x64, which was the MSDNAA version, installed myself to a completely clean disk.

Hardware itself is 3 years old, except for the memory which is 1 year old.

I did a Windows Memory Test and it passed the "Extended" test (though I only let it run for one pass...). Also a scandisk passed ok.

Thanks!

usasma · Sep 27, 2010

These devices are disabled. Did you do this deliberately? If so, why?
Please uninstall them.

Code:

VirtualBox Host-Only Ethernet Adapter    ROOT\NET\0000    This device is disabled.

April and July memory dumps seem to involve the storage sub-system
The September memory dumps don't blame anything in particular.

To deal with the storage sub-system, please run these free diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: http://<a href="http://www.carrona.org/dvrref.html" target="_blank">Driver Reference</a>Driver Reference ).
Please pay particular attention to any dated 2008 or earlier:

Code:

[FONT=lucida console]
[COLOR=Red]ASACPI.sys[/COLOR]   Sun Mar 27 22:30:36 2005 (42476C4C) - Asus ATK0110 ACPI Utility ([COLOR=red]a known BSOD maker[/COLOR]) - http://www.carrona.org/dvrref.html#[COLOR=Black]ASACPI.sys[/COLOR]
ctac32k.sys  Wed Jul 02 04:38:22 2008 (486B3E7E) - Creative Audio Driver - http://www.carrona.org/dvrref.html#ctac32k.sys
rdpdispm.sys Fri Mar 21 01:06:22 2008 (47E3424E) - RDP Encoder Mirror Driver - Live Mesh - http://www.carrona.org/dvrref.html#rdpdispm.sys
[/FONT]

If this doesn't stop the BSOD's, then please run Driver Verifier according to these directions:

Code:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:

[FONT=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 27 15:49:04.956 2010 (UTC - 4:00)
System Uptime: 0 days 21:48:52.109
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wlmail.exe
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`0000ff6e 0000df6e`0001bed8
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep 23 04:32:27.405 2010 (UTC - 4:00)
System Uptime: 4 days 14:58:17.158
BugCheck F4, {3, fffffa8005d6cb30, fffffa8005d6ce10, fffff80002f7f5d0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`05d6cb30 fffffa80`05d6ce10 fffff800`02f7f5d0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 18:22:14.263 2010 (UTC - 4:00)
System Uptime: 0 days 5:02:12.027
Probably caused by : fileinfo.sys ( fileinfo!memmove+41 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
Bugcheck code 00000050
Arguments ffffe8a0`0dfb3c2e 00000000`00000000 fffff880`01107961 00000000`00000007
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Apr 18 15:43:25.031 2010 (UTC - 4:00)
System Uptime: 5 days 1:07:25.852
Probably caused by : Ntfs.sys ( Ntfs!NtfsExtendedCompleteRequestInternal+110 )
PROCESS_NAME:  wlmail.exe
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`06e203f8 fffff880`06e1fc60 fffff880`01033280
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

ColinN · Sep 28, 2010

Hi, thanks for the quick response.

The April and May memory dumps were fixed then I believe, I updated my chipset drivers, I'm only talking about the two September ones here.

I've updated the ASACPI.sys driver to the most recent one I could find on the internet, dated 2009 sometime.

The Creative driver is for my soundcard, I've got the latest driver package released a month or two back for that so that is the most recent one....

The other one comes with Live Mesh (now Live Sync) and I find that a really useful piece of software. It's been installed on my system for ages with no issues so I'm reluctant to remove it.

The disabled VirtualBox network adaptors are disabled on purpose because I had an issue with them confusing my real network adaptors when I quit VirtualBox and resumed from Sleep. I'll uninstall VirtualBox completely, I have an old version anyway and hardly use it.

I've tested both my HDDs with Seagate SeaTools, both came out fine.

Currently testing memory with MemTest, I got errors with both sticks in so currently testing with one stick to see if it's my motherboard or RAM which is having problems!

I'll report back if I find any issues here.

EDIT: I think I have found the problem! One DIMM runs fine and passes Memtest ok, the other one doesn't and seems to cause errors all over the place pretty quickly. Guess I'll be sending that back to Crucial then. I'm just thankful it isn't my motherboard! Thanks for the help usasma.

Recent varied BSOD crashes

ColinN

New member

My Computer

At a glance

usasma

Mr. Cranky Pants

My Computer

At a glance

ColinN

New member

My Computer

At a glance

Similar threads

Recent varied BSOD crashes

ColinN

New member

My Computer My Computer

At a glance

usasma

Mr. Cranky Pants

My Computer My Computer

At a glance

ColinN

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer