Solved BSOD but only When on Customers Domain

[mtech61]

I have a customer with Server 2008 Std Domain (64Bit), 8 XP SP3 Workstations and 3 Win 7 X64 Workstations.

I rebuilt one Windows 7 x64 PC in April Last year and it has been Randomly BSOD'ing and hanging (About once a month initially), But Only at their premises on their domain. If I bring it back to my Office and log on with cached credentials (I have Server 2008 R2 STd and WORKGROUP Network) It performs flawlessly. I have had this Workstation here being torture tested since 22/12/2011 and it hasn't missed a beat. In Fact it never fails at my Office only at client.

Sometimes it simply hangs on the Ctrl-Alt-Del Screen and doesn't generate a Minidump. Sometimes it's while the User is working, sometimes it's during the night when the Machine is idling. It's about every 2 - 3 days. The Only thing I haven't tried is new Keyboard, mouse and monitor. I am going to take it back over the weekend and try checking the CAT5 Cabling to the Switch in the server Cabinet, is that likely?, it's about all I haven't tried.

Operating System MS Windows 7 64-bit SP1Professional (OEM)
CPU Intel Core 2 Quad Q8300 @ 2.50GHz 42 °C Yorkfield 45nm Technology
RAM 8.00 GB Dual-Channel DDR3 @ 533MHz (7-7-7-20) Transcend 2 x 4Gb
Motherboard Gigabyte Technology Co., Ltd. G41MT-S2P (Socket 775) 30 °C
Graphics Acer AL2017 (1400x1050@60Hz)
Intel(R) G41 Express Chipset
LogMeIn Mirror Driver
Hard Drives 488GB Seagate ST3500418AS ATA Device (SATA) 37 °C
78GB Seagate ST380013AS ATA Device (SATA) 36 °C
Optical Drives HL-DT-ST DVDRAM GH22NS40 ATA Device
Audio High Definition Audio Device
Avast Business Professional 6 (on all Machines with no problems)
2KVA UPS

I have tried the following:

Replaced Mainboard (under warranty Northbridge overheating)
Replaced Power supply (Under warranty Died - Gigabyte 470watt)
Updated Seagate Firmware on Boot drive (CC49 was CC46)
Memtest Overnight 20 Passes on both 4Gb Dimms separately Both passed 100%
Deep Surface Scans on both HDD's (with three different Apps from DOS environment and within Windows)
CPU Test (Prime 95) No Overheating 24 hours all 4 cores
Reloaded Virgin Windows 7 x64 - 4 or 5 times
Numerous different Malware/Anti-virus tests and clean every time.

I am running out of ideas, the user is back at Work Monday and I have promised it will work

PS. Cant attach Perfmon as it just runs and never stops?

 

[usasma]

It only has 55 Windows Updates after SP1 - most systems have 60-70 or more. Please check to see if you have all available Windows Updates

The System log in Event Viewer shows issues with network connectivity. Search the log for errors and it'll show a lot of them. It also shows corrupt data structures on the HDD's boot volume. Please run CHKDSK /R /F I'd also suggest rerunning SeaTools long test on each of the disks.

The WER section of MSINFO32 shows 2 STOP 0x50 errors, one blaming the OS core and the other blaming the NTFS file system.

The version of LogMeIn that you're using dates from 2007 - please update or remove it.

Beyond that, there's nothing that stands out (personally I'm betting on a hard drive problem and/or a network connectivity issue). I'd suggest using Driver Verifier to see if we can force a crash that'll name the offending driver. Here's the settings that I suggest:

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 "Special Pool" and "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 to stop Driver Verifier from loading (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]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\122811-22401-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Dec 28 05:58:44.908 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:56.879
Probably caused by : Ntfs.sys ( Ntfs!NtfsUninitializeNtfsMcb+2b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!NtfsUninitializeNtfsMcb+2b
Bugcheck code 00000050
Arguments fffff8b0`0872f220 00000000`00000000 fffff880`0123aeb3 00000000`00000005
BiosVersion = F2
BiosReleaseDate = 05/16/2011
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q8300  @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2499
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\122111-17238-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Dec 20 22:25:21.246 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:22.947
Probably caused by : fltmgr.sys ( fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+503 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  LogMeIn.exe
FAILURE_BUCKET_ID:  X64_0x50_fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+503
Bugcheck code 00000050
Arguments fffffac0`07afb7d0 00000000`00000000 fffff880`01196e83 00000000`00000005
BiosVersion = F2
BiosReleaseDate = 05/16/2011
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q8300  @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2499
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[mtech61]

Hi John

Thanks for looking

It only has 55 Windows Updates after SP1 - most systems have 60-70 or more. Please check to see if you have all available Windows Updates

It has now done all the updates according to Windows?

The System log in Event Viewer shows issues with network connectivity. Search the log for errors and it'll show a lot of them. It also shows corrupt data structures on the HDD's boot volume. Please run CHKDSK /R /F I'd also suggest rerunning SeaTools long test on each of the disks.

These Network connectivity errors are because I am running this Box at my Office and not on the clients domain while testing, so it cannot connect to the Server hence the DNS and other connectivity errors. I did look there first but there's never anything immediately preceding the Crash that looks out of the ordinary in the event viewer.

The WER section of MSINFO32 shows 2 STOP 0x50 errors, one blaming the OS core and the other blaming the NTFS file system.

These are the ones it recorded, but most times it doesn't create a log especially on the hanging ctrl-alt-del. Also the during the middle of the night ones don't get minidumps for some reason.

The version of LogMeIn that you're using dates from 2007 - please update or remove it.

It was Freshly installed Build 2126 (December 2011) on a new Windows Install ?

Beyond that, there's nothing that stands out (personally I'm betting on a hard drive problem and/or a network connectivity issue).

Hard drives are ruled out, CHKDSK /F done numerous times both drives passed Seatools (and 2 Other independant) deep surface scan diagnostics at least 5 times on each drive. SFC /Scannow also passes without issues. Is it possible to have a drive that passes all Seagate tests but crashes randomly on boot up? MY Suppliers won't replace it if it passes all Seagate tests.

I'd suggest using Driver Verifier to see if we can force a crash that'll name the offending driver. Here's the settings that I suggest:

OK. Going to try this on site this afternoon when I connect it back on to their domain after running some CAT5 cable tests.

Thanks for the Help

 

[usasma]

If it doesn't fail the HDD test, no one is going to pay for a new hard drive.

I have a "quirk" about CHKDSK. I insist upon running it with both the /r and /f parameters (chkdsk /r /f) - and it's worked quite well for me for a long time.

Keep an eye on the LogMeIn drivers. I haven't seen issues with them recently, but I haven't seen them dated as old as 2007 for a while either. Check the C:\Windows\System32\drivers directory for the dates (you can also look in MSINFO32 Software Environment...System Drivers ).

Maybe try some stress tests (I'm wondering if Prime95 will force something out)? Here's the link to my hardware diag's page: http://www.carrona.org/hwdiag.html

 

[mtech61]

I have got the Machine from Hell back on my Test Bench here in my office. When I took it back to the client on Sat morning (after 10 days of torture with no BSOD), I checked the CAT5 Cable to the Server Room and two Pins were crossed (7 & 8 But AFAIK they aren't used anyway only pins 3,4,5,6 ??) so I repaired that and plugged the Box back in and once it booted up I went into the Event viewer to see what was happening and it BSOD'ed as I was reading the events (No Minidump) Just dxgmms1.sys and PAGE_FAULT_IN_NONPAGED_AREA (Got Cam shot on my Phone). I rebooted in Safe Mode and it BSOD'd there too. I Plugged in my Spare Box and found that all of a sudden it's NIC was dead (Strange as the last time it was used was by this User and it worked fine the last time) I'm beginning to suspect the 24 Port Switch, I changed Ports but by then the damage was done. I left the loan unit there but had to fit another NIC and it's slow but working.

I am busy doing Seatools again, CHKDSK etc, but I think I am going to wipe this drive and start from scratch again.

For the Record I also Changed her Monitor (Long shot I know) and swopped Printers with another user (Also Long shot) only the Mouse and the Keyboard are original (Unlikely)

Two things that are different from my office are the 24 Port Switch and Cabling which I've now rectified. Can a Dodgy Switch affect just this one PC??

Any suggestions (However weird or obscure) welcome. Will post as I find out more...

 

[profdlp]

It appears that dxgmms1.sys is related to DirectX and/or your video card drivers. I'd try reinstalling both, beginning with DirectX.

 

[usasma]

The switch can't do it (IME).
Run a clean install when you wipe it, that way you can rule out any 3rd party stuff. Here's how I do a clean install:

For testing purposes, it's best to install Windows "clean".
This is, basically, installing it the way that Microsoft intended (using drivers from Windows Update).
This procedure is for Windows 7, Vista is similar (but has 2 service packs)

You will need your installation/recovery DVD(s) before you start. Once you wipe the hard drive there's no going back!!!

1. Backup all your data.
This will wipe everything off of your hard drive, so anything that you want to keep will need to be saved elsewhere.

NOTE: If this is due to an infection, remember to scan the data with another system's current antivirus in order to locate and remove any malware.

2. Connect the system to the internet (if the system says disconnect from the Internet, then do so).

3. Use one of these free utilities to wipe the hard drive clean:
DBAN ( DBAN Download | Darik's Boot And Nuke )
KillDisk ( Freeware Download Active@ KillDisk ).
This will also delete any recovery partitions on the system - so the intallation/recovery DVD's are essential!!!

4. Install Windows by booting from the installation/recovery DVD - DO NOT tweak any settings!!!

5. Visit Windows Update and get all updates

6. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center

7. Visit Windows Update and get any other available updates

8. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)

9. Download, install, and update a free antivirus so you don't get infected while testing ( Free AntiVirus ).

If the problems persist, then the problem is most likely with your hardware.

CAVEAT: If you have an Asus motherboard, check the date on the C:\Windows\System32\driver\ASACPI.sys file. 2004/2005 is a problem, 2009,2010 is OK. Updates are available at the Asus support website.

CAVEAT: If you have a Sony system, make sure that you DO NOT have the 2007 (or earlier) version of the Sony Firmware Extension Parser (SFEP.sys). Update this driver immediately!!!

I'm favoring mobo issues at this point - simply because the system won't settle down and point at anything consistently.

 

[mtech61]

I rebuilt this PC again (now i5) and moved it to another position in the Office, moved another user with a perfect PC that never gives problems to that Network point and it Crashed while booting up.

Got out the old Cable testers and it showed a dead Pin 3 (previously showed Pins 7 and 8 Inverted) replace the Plugs again all shows dandy. Reboot, no problem. Next Morning Crash wont boot until we pull the Network cable out. Try again and it boots fine. Cable test shows fine. I figure problem must be in the ceiling so client get's someone up there and checks for cable damage or some type of interference, couldn't find anything but it's settled down now. (Can these cables develop capacitance overnight ??)

I am going to replace the cable with better quality cable and route it better and hopefully this problem doesn't re-occur. It wasn't the switch because I tried different sockets and they all did these random BSOD's over a period of weeks.

Personally I think the place is haunted.. but that's another story at least this 6 month saga looks to be over.

 

[profdlp]

...Personally I think the place is haunted...

I had a boss once who claimed that our building was located on an old Indian burial ground. Looking back twenty years later, that still seems to be the most logical explanation for some of the stuff that happened there.

 

[usasma]

Reminds me of the cable problem I had at home a while back.
The cable tech claimed it was my router - so they gave me a new one.
Still had connection problems.

A week later my wife spotted another cable tech in a neighbor's yard.
Turns out the neighbor had nicked the cable and moisture got into it.
They fixed that - and my problems miraculously went away!

It's very expensive and a lot of work to replace everything - but who's to say that that's not the problem?

As for the switch - those things get treated badly day-in and day-out.
I'd suggest trying a new switch to see if it helps. You can purchase one from a major retailer and return it for a full refund in most states.