Windows 7: random bsod's on prev stable vista machine

hi,
i'm running win7pro64 and am experiencing what looks to be random bsod's.

i've updated my profile to hold all the specs for the machine. this box was previously used with vista64ultimate with no issues for over a year. i am doing no overclocking and running everything at normal specs.

i ran my first Windows 7 install 2 weeks ago and have had multiple bsod's daily since then.

i've had them happen when watching a movie file in wmc, watching live tv in wmc, watching recorded tv in wmc, watching a show on hulu desktop (not in wmc) and while the computer is doing nothing but just idling...

i've reinstalled Windows 7 multiple times. installing from vista64ultimate using the "clean install" method, installing from Windows 7 using "clean install" and installing from a bootable dvd after formatting the drive. same result each time.

i've tried letting Windows 7 pick all my drivers, and i've also tried to manually download/install all drivers, but the results seem to be the same.

i've run the windows memory diagnostic and it came back with no errors.

here's the whocrashed report from the 2 bsod's that happened tonight, and i've attached the dmp files from both of those bsod's.

thanks for any help on this, as i'm starting to pull my hair out
please let me know if there is any more info that is needed about my system or the errors to help figure this out.



in the meantime, i'll attach anymore dmp files if (when) i encounter any more bsod's.

On Tue 11/10/2009 4:06:10 AM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007DAB028, 0xB6782000, 0xA1000135)
Error: WHEA_UNCORRECTABLE_ERROR
Dump file: C:\Windows\Minidump\110909-20748-01.dmp



On Tue 11/10/2009 3:26:13 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002DD5180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
Dump file: C:\Windows\Minidump\110909-21886-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

Attachment 35964

Attachment 35965

after browsing around here and on other forums, i've read a couple posts about people having problems with hauppauge's tuner drivers, even the latest Windows 7 drivers provided by hauppauge.

so on a whim, i removed my HVR 1600 tuner card and ran everything i could try, except for live tv.

no crashes or bsod's as of yet, but that was only an hour or 2 of testing/watching. it has run multiple hours before (with the tuner card installed) only to crash repeatedly in hour 4. for example, watch a 3 hour football game on live tv just fine, only to have it bsod during the last 45 seconds of the game (now that's annoying), and then again after that when trying to watch a movie...

hopefully removing (and then replacing) the tuner card will solve the issues, but i'm honestly not too optimistic, since random troubleshooting usually isn't the best method.

i'll post back with an update either way, and if anyone has any suggestions, please feel free to post.

Thats the same error we have been having and... machine was running perfectly under Vista and started playing up as soon as 7 was installed.

Today put Vista back on and the reboots continued...so PC is in hardware shop now :-)

It's getting 0x124 hardware errors. Please see this excellent thread about the subject, written by H2S04.

And because you have this too, "CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts."

...I'd say follow step 4) first, from the link I gave. That's an AMD thing.

bios updated to latest version.
we'll see if that stops the bsod's.

looking through that thread "to-do" list, i've done: 1, 2, 3, 4 (just now), 5 (autoupdates), 6, and 7

no crashes under normal usage after reinstalling the tv tuner and flashing the bios to the most current version using the @bios tool (F6+, i believe)

hope that is the end of it!

thanks for the help!

See...H2SO4 fixes machines without even replying to a thread. lol

i've been running very stable since my last post after updating my bios, no crashes, no reboots, everything running fine until tonight when i went to wake up my computer and found a BSOD

this is my whocrashed info:

On Tue 12/8/2009 2:08:13 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002DD5180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
Dump file: C:\Windows\Minidump\120709-25116-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

any ideas on this?
i'm running all the latest drivers for everything, most recent bios, and haven't installed anything new in the past week. i put in a new bd-drive last week, but it has been running fine for a week before this.

i think i might just play the "wait and see" game with this one for now...

Post the crash dump same as before, using the paperclip.

so just as i'm posting the crash dump, i get another BSOD. yay!

attaching dmp files from both bsod's

On Tue 12/8/2009 4:00:37 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002D64180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
Dump file: C:\Windows\Minidump\120709-21606-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.