PDA

View Full Version : Crash analysis



linw
15-08-2012, 10:09 AM
Anyone good at 'Bluescreen' crash analysis?
The offending machine is not in my hands, unfortunately, or I would have run memory checks, dust cleaning, re-seating etc etc. Hate trying to fix these fundamental problems via remote with unsophisticated users!!

Alternatively, anyone know a good fixer in or near Levin?


It is an E8400 cpu running win 7 with 4GB RAM. About 3 yrs old. TIA.


071512-40591-01.dmp 15/08/2012 9:18:30 a.m. 0x00000124 00000000`00000000 fffffa80`0539c028 00000000`b2000000 00000000`00010005 ntoskrnl.exe ntoskrnl.exe+7f1c0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17835 (win7sp1_gdr.120503-2030) x64 ntoskrnl.exe+7f1c0 C:\Windows\Minidump\071512-40591-01.dmp 4 15 7601 318,650
071412-27705-01.dmp 14/07/2012 2:34:26 p.m. KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7f190 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17835 (win7sp1_gdr.120503-2030) x64 ntoskrnl.exe+7f190 C:\Windows\Minidump\071412-27705-01.dmp 4 15 7601 319,162
040212-22230-01.dmp 2/04/2012 4:57:24 p.m. PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff960`003bebf8 00000000`00000000 fffff800`02e79043 00000000`00000000 win32k.sys win32k.sys+b10c5 x64 ntoskrnl.exe+7cd40 C:\Windows\Minidump\040212-22230-01.dmp 4 15 7601 320,634
120211-36114-01.dmp 2/12/2011 9:11:42 p.m. 0x00000124 00000000`00000000 fffffa80`04b07028 00000000`be000000 00000000`00800400 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17835 (win7sp1_gdr.120503-2030) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\120211-36114-01.dmp 4 15 7601 320,634
103011-26847-01.dmp 30/10/2011 1:06:23 p.m. BUGCODE_USB_DRIVER 0x000000fe 00000000`00000006 fffffa80`055801a0 00000000`4f444648 00000000`00000000 usbehci.sys usbehci.sys+2977 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\103011-26847-01.dmp 4 15 7601 319,162
071411-19578-01.dmp 14/07/2011 4:50:46 p.m. DRIVER_POWER_STATE_FAILURE 0x0000009f 00000000`00000003 fffffa80`03f9a050 fffff800`00b9c518 fffffa80`0638a390 ntoskrnl.exe ntoskrnl.exe+7fd00 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17835 (win7sp1_gdr.120503-2030) x64 ntoskrnl.exe+7fd00 C:\Windows\Minidump\071411-19578-01.dmp 4 15 7601 319,226

Speedy Gonzales
15-08-2012, 12:57 PM
Get bluescreenview run it, dont delete the dmp files. What does it say, is the cause.

It looks like the USB drivers, are crashing

linw
15-08-2012, 01:29 PM
Thanks, Speedy, but that was the output from Nirsoft bluescreen view. Tried to upload the zipped dump files but the manager said it was an invalid file! What's with that??

I have asked the owner to initiate a windows mem test but haven't heard back about that yet.

Will get Secunia to check file versions as well.

Wish I had the machine here!

Speedy Gonzales
15-08-2012, 01:36 PM
Are they overclocking?? If they are, set it back to its defaults

Speedy Gonzales
15-08-2012, 02:10 PM
Dont know about the zip prob, you'll have to ask Jen or Chilling, to see why its saying its invalid. When it says its a valid attachment

linw
15-08-2012, 08:45 PM
Are they overclocking?? If they are, set it back to its defaults
Nah, bog standard. It is an I3 CPU not an E8400. Got my wires crossed.

wainuitech
15-08-2012, 09:34 PM
That list has several different error codes, all meaning different things.

Try looking the W7's own log files may be something there.

Look in both the eventvwr and Reliability monitor. Click start, type in reli open the history from the result, will take a moment to load, it will show any errors, sometimes they do help track it down.

linw
16-08-2012, 09:59 AM
Thanks, WT. Yes, it is a puzzle being that there seem to be different causes.

I'm getting onto the machine this morning with TV so will look at the reliability monitor.

ruup
16-08-2012, 12:56 PM
Hi, I haven't tried this myself but it may be useful...

http://www.filecluster.com/System-Utilities/Benchmark-Diagnostics/Download-WhoCrashed.html

Cheers

linw
16-08-2012, 03:34 PM
Thanks, ruup. I tried that but it (Whocrashed) also had trouble coming to any conclusion. A couple were hardware errors and the others were probably dvrs unknown.

Got on with TV and looked at the Reliability Monitor. Zero use.

Got windows to check for drivers in Dev Mgr. It updated LAN dvr and Display. Said others were latest.

Looked again at Event logs and saw a couple of Ntfs errors so chkdsked twice. Quite a few indexes were fixed.

Also saw a couple of bunches of controller errors Harddisk3\DR9 DR7 and DR4. There is an ext HDD attached so are these errors for that drive??

I certainly don't feel confident anything has been done to fix it so I await the next crash!

Bit of a quandary as it is a Computer Lounge system inside the 2 yr warranty. Is this a warranty issue??? I can't say whether it is hardware related or a setup/software issue. Probably the latter, so I wear the aggro and most of my time!

wainuitech
16-08-2012, 05:50 PM
Sometimes the only way to tell if its hardware or software is to wipe the drive and reinstall, if its still doing it from a fresh install then look at hardware.

What happens if the PC is run in safe mode, does it still crash ?

linw
18-08-2012, 09:54 AM
Not sure whether safe mode is practical because of the often long time between crashes. Delays are 3 mth, 2 mth, 4 mth, 3 mth, 1 day (jul), 1 day (Aug). The Jul and Aug crash pairs were 4 wks apart.

Think I'll try HDtune to check the HDD (no events about disk probs so it is most likely OK) and OCCT to see if putting some stress on will produce a crash.

Would also be a good idea to run with only one RAM stick (has 2 x 2GB) and see if it will hold up. If not, swap the sticks and try again. But don't know if I can trust them to do this hardware job! But with the sometimes big gaps between crashes................