BSOD at start up! :( (updated)

[Niclas1199]

Hey guys.

My laptop used to have Vista64bit installed, but i recently upgraded it with windows 7 - 32bit home. Specs: Intel Core 2 duo 2,1GHz, 4gb ram, Nvidia GeForce 8600GTM.
Its been running stable for about 2 months.

This afternoon i DL the latest patch 3.3.5 for World of Warcraft, but when i started up the game it crashed and the whole computer with it.

When i turned on the computer again, right before the logon screen it showed blue screen saying that an error had been found and windows had been shut down to prevent damage. It has done this a couple of times before random (not associated with wow).

But now it keeps on doing it, right before the logon screen appears :O I tried starting it in safemode and uninstalled wow but it didnt solve the problem. Every third time or so, the logon screen appears and it starts up fine with no problems though, so it seems pretty random
I also tried running the startup repair tool, but it didnt work either.
Also sometimes the resolution gets messed up (set too 400*600 or something) when the logon screen finally appears after a couple of blue screens.

It has overheated several times before, so maybe that could have done some damage to the hardware :/ but im not sure.

Any help on finding out whats wrong is greatly appreciated!

Regards Niclas.

 

[usasma]

Your Device Manager shows problems with these devices:

Ikke tilgængelig ACPI\CPL0002\2&DABA3FF&1 The drivers for this device are not installed.

Basissystemenhed PCI\VEN_1180&DEV_0592&SUBSYS_002514C0&REV_12\4&39F8F158&0&33F0 The drivers for this device are not installed.

Ikke tilgængelig ACPI\ENE0100\3&33FD14CA&0 The drivers for this device are not installed.

Basissystemenhed PCI\VEN_1180&DEV_0843&SUBSYS_002514C0&REV_12\4&39F8F158&0&32F0 The drivers for this device are not installed.

Please install the drivers for these devices, they should be available from the PC Manufacturer's support website. Although I don't speak your language, here's my best guess as to what these devices are:
- 1st Ikke tilgængelig = Battery meter driver
- Both Basissystemenhed = Ricoh Memory Card reader driver
- 2nd Ikke tilgængelig = ENE CIR Receiver infrared device

You have 2 antivirus' running - this is not good as they will fight each other. Also, 3 of the 6 memory dumps include references to this - one even mentions both in the stack text.

Run the appropriate removal tool after you've uninstalled the antivirus programs ( Antivirus Uninstallers ). IMO you'll be better off removing both and installing the free Microsoft Security Essentials ( http://www.microsoft.com/security_essentials/ )

Please update your Fingerprint sensor's driver as this component of it is from 2008:

tcusb.sys Mon Dec 08 18:53:52 2008 (493DB390)

Description here: Driver Reference

Should all of this not fix the BSOD's, then please post back. There may be a hardware component to all of this, but we can't tell until you've fixed the stuff that I've mentioned.

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Tue Sep 21 16:06:32.359 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:11.154
*** WARNING: Unable to verify timestamp for [COLOR=Red]SYMEVENT.SYS[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
*** WARNING: Unable to verify timestamp for [COLOR=Red]avgldx86.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for avgldx86.sys
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001A
Arguments 00041284 05d51001 00000a83 c0402000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Tue Sep 21 13:46:07.087 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:22.881
*** WARNING: Unable to verify timestamp for [COLOR=Red]SYMEVENT.SYS[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
PROCESS_NAME:  smss.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 000000F4
Arguments 00000003 85bb4400 85bb456c 82e42830
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Tue Sep 21 11:00:06.736 2010 (UTC - 4:00)
System Uptime: 0 days 0:31:36.531
BUGCHECK_STR:  0x1a_61940
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  [COLOR=Red]avgwdsvc.exe[/COLOR]
Bugcheck code 0000001A
Arguments 00061940 001f2000 4623c886 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Wed Sep 15 03:12:13.663 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:16.458
*** WARNING: Unable to verify timestamp for avgldx86.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx86.sys
Probably caused by : [COLOR=Red]avgldx86.sys[/COLOR] ( avgldx86+1735 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments c0000005 8bfbf735 80d8656c 80d86150
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Tue Aug 31 12:09:43.053 2010 (UTC - 4:00)
System Uptime: 0 days 1:39:03.848
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+18f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  [COLOR=Red]avgupd.exe[/COLOR]
Bugcheck code 1000008E
Arguments c0000005 82e3b081 a4f9c704 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Aug 30 06:16:32.499 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:11.294
Probably caused by : RDPCDD.sys ( RDPCDD!DriverEntry+2c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  System
Bugcheck code 1000008E
Arguments c0000005 82e06081 80d85fdc 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[Niclas1199]

Hey, thanks for the quick answer! Unfortunately it didnt work.

I DL and installed drivers: Infrared, CardReader, chipset and smartbattery.
I uninstalled both AVG and the other antivirus program, cleaned, and installed the one you suggested.
And i uninstalled the fingerprint drivers that werent working.

I also uninstalled my Nvidia screen driver, and tried to install it again, but it failed :S?

It was able to start up 3 times without problems. But this evening it has showed BSOD again 4 times

I've uploaded another dump.

Do you have any other suggestions? :/

 

[cybercore]

092110-24523-01.dmp
MEMORY_MANAGEMENT (1a)
Unable to verify timestamp for avgldx86.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx86.sys
FAILURE_BUCKET_ID: 0x1a_41284_SYMEVENT+14449


092210-25100-01.dmp
CRITICAL_OBJECT_TERMINATION (f4)
BUGCHECK_STR: 0xF4_WerFault.exe (Windows Problem Reporting - Microsoft® Windows® Operating System)
FAILURE_BUCKET_ID: 0xF4_WerFault.exe_IMAGE_wininit.exe


092110-24398-01.dmp
MEMORY_MANAGEMENT (1a)
PROCESS_NAME: avgwdsvc.exe
FAILURE_BUCKET_ID: 0x1a_61940_nt!MiSwapWslEntries+48


092110-22526-01.dmp
CRITICAL_OBJECT_TERMINATION (f4)
FAILURE_BUCKET_ID: 0xF4_C0000005_IMAGE_smss.exe
A stack line - 80ecf4d0 82c8679a ffffffff c0000005 80ecf964 SYMEVENT+0x14449


091510-33134-01.dmp
BugCheck 1000007E, {c0000005, 8bfbf735, 80d8656c, 80d86150}
Probably caused by : avgldx86.sys ( avgldx86+1735 )
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
FAILURE_BUCKET_ID: 0x7E_avgldx86+1735


083110-35583-01.dmp
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
PROCESS_NAME: avgupd.ex
FAILURE_BUCKET_ID: 0x8E_nt!CmpKcbCacheLookup+18f


083010-25100-01.dmp
BugCheck 1000008E, {c0000005, 82e06081, 80d85fdc, 0}
Probably caused by : RDPCDD.sys ( RDPCDD!DriverEntry+2c )
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
FAILURE_BUCKET_ID: 0x8E_RDPCDD!DriverEntry+2c



You have these drivers:

SYMEVENT.SYS Wed Jun 24 23:14:58 2009
avgldx86.sys

I suspect symantec cannot work well with avg. I would replace both with MSE.

 

[Niclas1199]

What? I only have one driver? :O? Or am I misunderstanding something?

I have already uninstalled both AVG and Symantec and replaced with the one suggested :/

 

[usasma]

I'd suggest that you use these free tools to remove the remnants of AVG and Norton/Symantec (if you haven't done so already):
AVG: AVG - Tools download
Norton: KB Article Not Found

All but one of the dumps that cybercore has posted are from before you removed the antivirus. It's this one that's the new one:

092210-25100-01.dmp
CRITICAL_OBJECT_TERMINATION (f4)
BUGCHECK_STR: 0xF4_WerFault.exe (Windows Problem Reporting - Microsoft® Windows® Operating System)
FAILURE_BUCKET_ID: 0xF4_WerFault.exe_IMAGE_wininit.exe

AVG and Symantec are NOT present in this memory dump.

More to follow

 

[usasma]

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:

[FONT=lucida console]
enecir.sys   Wed Mar 07 03:26:49 2007 - ENE Consumer IR Driver for eHome - http://www.carrona.org/dvrref.html#enecir.sys
rimmptsk.sys Wed Sep 10 01:22:33 2008 - Ricoh Memory Card Reader driver - http://www.carrona.org/dvrref.html#rimmptsk.sys
rimsptsk.sys Mon Apr 21 02:26:10 2008 - Ricoh Memory Card Reader driver - http://www.carrona.org/dvrref.html#rimsptsk.sys
tcusb.sys    Mon Dec 08 18:53:52 2008 - TouchChip USB Kernel Driver (FingerPrint Sensor) - http://www.carrona.org/dvrref.html#tcusb.sys
[/FONT]

Please note that the tcusb.sys driver is the same date. Don't worry about it for now. If you happen to find a more updated driver, go ahead and update it again.

With the exception of tcusb.sys, these probably aren't involved directly in the crashes (as they weren't present in the previous dump files). Still, it's a good idea to update them.

Don't forget to visit Windows Update to ensure that you have all the available updates (there are some older Windows drivers that are updated this way).

As this is a STOP 0xF4 error (more info here: BSOD Index ), I'd suggest running Driver Verifier according to these directions:

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:

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

[FONT=lucida console]
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Wed Sep 22 14:43:10.355 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:23.150
PROCESS_NAME:  WerFault.exe
BUGCHECK_STR:  0xF4_WerFault.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 000000F4
Arguments 00000003 870dc030 870dc19c 82df6830
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
  
  [/FONT]

 

[Niclas1199]

I couldent find updates for these drivers: "enecir.sys" and 2*"rimmptsk.sys" :/

But I dont understand how a fingerprint driver can cause the BSOD, when i've uninstalled the fingerprint program? (Protector suite)

Anyway
For the "tcusb.sys" driver which seem to be the main problem? my windows solution center has come up with a "solution" to DL a driver for a fingerprint program, and i asume that it is an update for this exact driver.
But i suppose thats the windows update, that i shouldent use?

Is it this one then: Welcome To UPEK - Support - Downloads ?

Hmm it sounds pretty risky using the Driver Verifier? So I think I will try to update the "tcusb.sys" driver before using it :/

And again, I cannot thank you enough for taking the time and helping me out!

 

[usasma]

Updating the drivers may not be needed (we do this because often the cause of a BSOD is outdated drivers). So hold off on this until we see if they continue to be involved.

You uninstalled the fingerprint program using their uninstaller. The BSOD shows that the driver is still loaded in that last BSOD. It's also possible that the driver was re-installed by Windows Update - but that's a whole 'nother can of worms!

I would try the UPEK link first, then the Windows Update - but please understand that this is not necessarily the cause of your BSOD's. If updating it doesn't fix the BSOD's, then Driver Verifier becomes necessary.

 

[Niclas1199]

I downloaded and installed the UPEC driver, but that only made it worse :/
Now BSOD appears even when windows has started up, and windows Aero has stopped working.

I'll try the driver verifier later in the evening.

Is there any way I can check if its a hardware faillure? because if it isnt, i think completely reinstalling windows is the only thing left to do.

 

[usasma]

If the fingerprint device is broken, you'll have to disconnect it to check.
Since it's a notebook, this won't be very easy to do.
If it's still under warranty, return the system to the service center for repair.

 

[Niclas1199]

I tried running the (im not sure what its called in english) "search for errors" on my C disk in "my computer". It then sceduled to do it the next time it started up.

The problem is it gets stuck at 71%, and I've tried restarting it, but it just gets stuck at the same percent again

so ehm, how do I stop it from searching :/?

This is the last thing I will do, then it will get a complete reboot.
But thanks alot for all the help man!

 

[usasma]

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)

 

[Niclas1199]

Will that make it stop searching :O? How do I run them when I cant get to my desktop?

 

[usasma]

I have taken the time to write instructions about the diagnostics at the link that I provided.
Please read the information there.

This won't stop the searching, it'll test your hardware.