BSOD help needed please

[SylverFyre]

I may have been a little hasty

2 more crashes on cold boots, yesterday and today.

Verifier is now disabled but I'm attaching both dumps in case they're useful.

Could this be a hardware issue?
If so, is there an area of the machine I should be looking at first?

 

[zigzag3143]

I may have been a little hasty

2 more crashes on cold boots, yesterday and today.

Verifier is now disabled but I'm attaching both dumps in case they're useful.

Could this be a hardware issue?
If so, is there an area of the machine I should be looking at first?

these both were Related to WLIDSVC.EXE UxStyle Core from The Within Network, LLC. I would remove them to test.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\052711-14430-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03009000 PsLoadedModuleList = 0xfffff800`0324e650
Debug session time: Fri May 27 15:02:14.084 2011 (GMT-4)
System Uptime: 0 days 0:00:38.927
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8000337ed51, fffff88004178ab0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+186 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8000337ed51, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88004178ab0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ObpWaitForMultipleObjects+186
fffff800`0337ed51 488b4a20        mov     rcx,qword ptr [rdx+20h]

CONTEXT:  fffff88004178ab0 -- (.cxr 0xfffff88004178ab0)
rax=0000000000000001 rbx=fffff8a003253440 rcx=fffff80003009000
rdx=00000000bad0b0b0 rsi=000000000000000f rdi=fffffa800705e480
rip=fffff8000337ed51 rsp=fffff88004179490 rbp=fffff88004179ca0
 r8=0000000000000008  r9=fffff8a00327d000 r10=fffffa8006a87060
r11=fffffffffffffd80 r12=fffff88004179a10 r13=fffff8a0028b8d30
r14=000000000000000e r15=0000000000000026
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ObpWaitForMultipleObjects+0x186:
fffff800`0337ed51 488b4a20        mov     rcx,qword ptr [rdx+20h] ds:002b:00000000`bad0b0d0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  WLIDSVC.EXE

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8000337ed51

STACK_TEXT:  
fffff880`04179490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x186


FOLLOWUP_IP: 
nt!ObpWaitForMultipleObjects+186
fffff800`0337ed51 488b4a20        mov     rcx,qword ptr [rdx+20h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObpWaitForMultipleObjects+186

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

STACK_COMMAND:  .cxr 0xfffff88004178ab0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpWaitForMultipleObjects+186

BUCKET_ID:  X64_0x3B_nt!ObpWaitForMultipleObjects+186

Followup: MachineOwner
---------

 

[SylverFyre]

Thanks for looking again Ken,

According to my services list that is the Windows live sign in assistant - Ive stopped the service and disabled it from starting up

*crosses fingers*

 

[zigzag3143]

Thanks for looking again Ken,

According to my services list that is the Windows live sign in assistant - Ive stopped the service and disabled it from starting up

*crosses fingers*

Was unfamiliar to me so I looked at a reference source that may well be wrong. Sorry for the confusion.

 

[SylverFyre]

Sorry Ken,

I'm attaching a zip with another 3 BSOD dumps

Are you sure that this is drivers and not hardware?
I can't find anything consistent apart from the fact that whenever it bluescreens it's always on the PC is switched on after being switched off for several hours.

I'm tempted to install Ubuntu and see what happens with that.

I tried a USB stick boot recently on cold boot and while Ubuntu didn't lock up the PC, generally it wasn't working - ie. programs wouldnt launch and quit with error messages.

I don't want to use Ubuntu anyway, I'd much prefer to get Windows7 on this machine working

 

[zigzag3143]

Sorry Ken,

I'm attaching a zip with another 3 BSOD dumps

Are you sure that this is drivers and not hardware?
I can't find anything consistent apart from the fact that whenever it bluescreens it's always on the PC is switched on after being switched off for several hours.

I'm tempted to install Ubuntu and see what happens with that.

I tried a USB stick boot recently on cold boot and while Ubuntu didn't lock up the PC, generally it wasn't working - ie. programs wouldnt launch and quit with error messages.

I don't want to use Ubuntu anyway, I'd much prefer to get Windows7 on this machine working

The most recent blames DirectX. That may be a driver or hardware. With these varying causes I am starting to think hardware. You can run these just to try and narrow it down and I would of course re-install DirectX.


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.

 

[SylverFyre]

I haven't got as far as switching memory sticks again, but for the last two days instead of going for a windows start attempt I've run memtest86 from cold.

Both times have come up with over 100 memory errors so I think it's safe to say that I have some dodgy hardware that's probably been getting worse for the time I've had the machine, until the last few months where some consistency has come into the crashing.

Ken, I really appreciate your help in getting my system software to a point where it is stable enough that I've got back to looking at hardware.

All your time and efforts are greatly appreciated - thanks!

Now just to start testing the sticks and slots one at a time

 

[SylverFyre]

Well, I eventually decided that it was most likely RAM that was at fault so I contacted the manufacturer and went through the RMA process. I've now had replacement sticks running in my machine for a fortnight with no errors whatsoever.

Thanks for taking the time to go through my many bluescreen dumps Ken, really appreciated