BSOD on Dell E6510 even after HDD replacement

[tashina]

Hi all,

I know just enough to be dangerous, but not enough to figure this out yet.

I started getting blue screens on this previously stable laptop about two weeks ago. To my knowledge, I had not installed any new drivers recently. When I got the first 2 BSODs in the same day, I did a system restore back 1 or 2 days. Kept getting blue screens - sometimes 2 a day, sometimes 1 per 2-3 days. No pattern. Happened overnight when the computer was sitting alone. Happened in the middle of VOIP meetings at work. Eventvwr would open and then crash (wouldn't close - just sat there and took up CPU and gave no results). Read the memory.dmp, but it seemed pretty generic and I didn't get very far. I ran Dell Diagnostics and right away it came up as bad hard drive and told me they'd send me a new one. Fine. Stopped working on the issue. Got the hard drive (which did not boot - sigh). Re-partitioned, re-formatted and then it worked. Re-loaded everything on it last night. Ran all windows updates. Just got another blue screen. Cry. The BSOD seems pretty generic. Restarts too fast for me to read it all, but I think I caught "clock interrupt" and a pretty generic code "0x...." code.

I would greatly appreciate any assistance. I am going to go run the more extensive memory tests, since at least I know how to do that. I used to build my own PCs in the last 90's, but since using laptops, have gotten much more hardware incompetent sadly.

 

[tashina]

Maybe I didn't manage to get the dump file in there so here are details:
[FONT=Segoe UI, Arial]On Sun 2/10/2013 8:51:56 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]Unknown[/FONT] (0xFFFFF88003178180)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003178180, 0x2)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error.
Google query: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]

Installed newer version of Bios. Ran Dell Diagnostics (no issues). Ran an hour of memory testing with no issues (will do more overnight). Running driver verifier. Sitting back and waiting for the next BSOD or suggestion from forum members. [/FONT]

 

[koolkat77]

Look forward to the verifier reports.

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html