BSOD after login when cold (minidump included)

[louisverhagen]

I have a Packard Bell ixterme M5740 i7 cpu [email protected] GHz 6 GB ram using windows 7 64-bit

If I start the computer usually I get the windows login screen, I select a user and then during the login process I get the BSOD. It doesn't matter with which user I log in. I then let the computer "run" a while. After 1/2 hour or so I reboot and login, no problems what so ever. The rest of the time no-problems. I can even reboot , login, etc....

However the next day after the computer has been swithed off and "cooled" down. Again when I log in BSOD. Sometimes it even produces a BSOD before the login screen although that is very rare.

Sounds to me as a hardware problem?
It's a real pain in the butt if you just want to start up the computer to look something up. I hope somebody can analyse the dmp files and help me. The system is still under guarantee, but I would like o have some solid idea what is going on before a sales person sends me on a ghost chase.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.7.683
Locale ID: 2057
Additional information about the problem:
BCCode: 1000008e
BCP1: 000000D1
BCP2: 07DBFD6E
BCP3: 00000002
BCP4: FFFFF880018DE161
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

 

[usasma]

The memory dump file blames pacer.sys - but that's a component of Windows and is, therefore, unlikely to be the actual cause.

The stack text of the dump file mentions lpx6x.sys - the only 3rd party driver mentioned in the stack (so it's the most likely cause of the problem). If you don't know what this driver is for, please search your computer for lpx6x and submit the files to Jotti's malware scan for scanning.

Please let us know the results of the scan (if infected, you'll have to remove the infection before fixing anything else).

Also, please right click on the lpx6x.sys file, select Properties, then select the Details tab. Let us know the names of the file and product.

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:
- 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. Please pay particular attention to any dated 2007 or earlier:

Iviaspi.sys  Tue Jan 09 01:49:11 [COLOR=Red]2007[/COLOR] - InterVideo ASPI Shell - http://www.carrona.org/dvrref.html#Iviaspi.sys
MarvinBus64.sys Fri Sep 23 17:17:03 [COLOR=Red]2005[/COLOR] -    likely a part of Pinnacle Studio's Marvin Bus - http://www.carrona.org/dvrref.html#MarvinBus64.sys
PxHlpa64.sys Wed Mar 12 21:58:17 2008 - Sonic CD/DVD driver (used by many different CD/DVD programs) - http://www.carrona.org/dvrref.html#PxHlpa64.sys
regi.sys     Mon Apr 16 11:19:10 [COLOR=Red]2007[/COLOR] - InterVideo regi.sys driver - http://www.carrona.org/dvrref.html#regi.sys

Summary of the BSOD's:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 28 11:12:05.216 2010 (GMT-4)
System Uptime: 0 days 0:01:01.356
BugCheck D1, {7dbfd6e, 2, 0, fffff880018de161}
*** WARNING: Unable to verify timestamp for lpx6x.sys
*** ERROR: Module load completed but symbols could not be loaded for lpx6x.sys
Probably caused by : pacer.sys ( pacer!PcFilterSendNetBufferLists+29 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 28 11:05:01.773 2010 (GMT-4)
System Uptime: 0 days 0:00:59.913
BugCheck D1, {7cffd6e, 2, 0, fffff880016d0161}
*** WARNING: Unable to verify timestamp for lpx6x.sys
*** ERROR: Module load completed but symbols could not be loaded for lpx6x.sys
Probably caused by : pacer.sys ( pacer!PcFilterSendNetBufferLists+29 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System

 

[louisverhagen]

Thanks for the analyses.

lpx6.sys is the driver for the ndas drive (network drive).

The thing is. I only have troubles getting on to the computer when I have just started it. None of the other computers (including another windows 7 computer) have troubles when they startup with the ndas drive (network drive). I have included the details of the lpx6 driver.

I will switch it of and see what happens.

louis

 

[usasma]

It could be that the copy of the driver on the problem machine is corrupted.
It could be that the problem machine is having connection issues
It could be that there's a compatibility issue between something on the problem system and the NDAS.

What I would suspect is that the system is looking for the NDAS device when you boot it up and it crashes when it can't find it. I would guess that leaving the computer on for a while let's some sort of "error correcting mechanism" of the NDAS provide more stability.

So, have you had any issues with the NDAS device on this system?
Have you disconnected the NDAS device to see if that stops the BSOD's on the problem system?

I would start with uninstalling the drivers/software on the problem machine and then installing freshly downloaded 64 bit Windows 7 drivers for the device. You will have to locate the drivers at the website of the manufacturer of your device (XiMeta doesn't provide drivers to the general public at their website).

 

[louisverhagen]

I deinstalled the NDAS/Ximeta software. And everything seems likes it is working fine. However, I did a roll back two weeks ago thinking it might have to do with a update of windows and evrything worked fine too for a while. So I will wait and see.

I also started checking the harddisk. It is not above suspicion. I saw it had some errors. I am running the WD tools as we speak. But then again the errors might have been caused by the blue screens.... Chicken and egg problem?

I also saw that there is a newer version of the ndas software. (1.71 => 1.72) Might also help. Again, my daughter is running the same software on a windows 7 machine (quad core, packard bell) with no troubles (as was I).

You also mentioned some other (older) drivers. They came with the system. Should I look for updates or let it rest?

Louis

 

[usasma]

"If it ain't broke, don't fix it!"

Different systems have different software combinations. So, if the DNAS drive is having issues with another component on your system - it's entirely possible that that particular combination isn't replicated on your daughter's system.

Also, the fact that a driver is blamed doesn't mean that it's a driver problem (but it is most likely). If the cabling or the device itself is bad, it can make the driver crash - which results in a BSOD blaming the driver.

So, we start with the drivers, and if that doesn't work we move on to checking other stuff.
Checking the hard drive is a good thing - it won't hurt and it may reveal a problem.

Keep the older drivers in mind. We mention the older drivers because they are more likely to cause compatibility issues - or to have glitches that have been fixed by later releases. This doesn't mean that there's anything wrong with them - but we keep our eye on them "just in case".

 

[louisverhagen]

I have ran the machine for over a week now with the NDAS/Ximeta software and had no troubles. Next weekend I will try to reinstall the software and see what happens.

Thanks for all the help

Louis

 

[usasma]

Glad to hear it. Thanks for letting us know!

Good luck!