Personal computing discussed
Moderators: renee, mac_h8r1, Nemesis
emorgoch wrote:Just out of curiosity, did these BSODs start up after you installed nVidia latest driver release (196.21)? I installed those drivers, and shortly there after, I was getting BSODs. First started when I was watching video, then expanded into when I was playing games. Drove me nuts, trying to figure it out. Then I un-installed those drivers (using Programs & features), let Ms install their default driver package, then updated those to the 195 driver release. No problems since.
Neutronbeam wrote:The free version of this MIGHT help-- http://www.resplendence.com/whocrashed
I just had to install/uninstall software to see what was generating my BSOD and ended up with three suspects--after I fixed the problem I never did confirm which one [or ones] caused it.
njenabnit wrote:I would also give memtest a try as well.
thr- wrote:njenabnit wrote:I would also give memtest a try as well.
See OP, no errors.
thr- wrote:So far I've only tried the 196.xx drivers, will give it a shot with the windows driver. But don't really expect it to do anything, maybe with the 186.xx drivers.
Neutronbeam wrote:The free version of this MIGHT help-- http://www.resplendence.com/whocrashed
I just had to install/uninstall software to see what was generating my BSOD and ended up with three suspects--after I fixed the problem I never did confirm which one [or ones] caused it.
On Mon 1-3-2010 14:01:13 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002FD5180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
Dump file: C:\Windows\Minidump\030110-13993-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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
1 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
emorgoch wrote:thr- wrote:So far I've only tried the 196.xx drivers, will give it a shot with the windows driver. But don't really expect it to do anything, maybe with the 186.xx drivers.
The only reason the I mentioned the windows drivers was that MS included the 18x release with the default Windows 7 package, so they get installed automatically after I un-install all the 196 drivers and reboot. I'd just let the 18x drivers do their full thing since I didn't want to interrupt it in the middle, reboot when it's done, and then do the 195 drivers immediately after.
thr- wrote:Neutronbeam wrote:The free version of this MIGHT help-- http://www.resplendence.com/whocrashed
I just had to install/uninstall software to see what was generating my BSOD and ended up with three suspects--after I fixed the problem I never did confirm which one [or ones] caused it.Code: Select allOn Mon 1-3-2010 14:01:13 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002FD5180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
Dump file: C:\Windows\Minidump\030110-13993-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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
1 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Don't really see what I could relate this with, nothing that ads up to the bsod debuglog.emorgoch wrote:thr- wrote:So far I've only tried the 196.xx drivers, will give it a shot with the windows driver. But don't really expect it to do anything, maybe with the 186.xx drivers.
The only reason the I mentioned the windows drivers was that MS included the 18x release with the default Windows 7 package, so they get installed automatically after I un-install all the 196 drivers and reboot. I'd just let the 18x drivers do their full thing since I didn't want to interrupt it in the middle, reboot when it's done, and then do the 195 drivers immediately after.
Tried the 18x driver and 19x right after that, getting the BSOD with both.
Must add to this that sometimes it doesn't BSOD but it just freezes. This is how it BSOD, first you get a bit of FPS drops, systems hangs, continues, hangs completely and than maybe a rare BSOD. After I reboot my system it doesn't want to boot, not getting into my BIOS, fans do spin and it powers up like it should power up but a black screen. After waiting for a few minutes(3-5 minutes) I can start it up without any problems, you would think it's a temperature problem but I'm sure that everything is fine with my temperature. (stress tested it many times) Even when I notice my system is going to BSOD/Freeze, immediately start looking at my temps and they are fine.
Ryu Connor wrote:My Asus X58 has exhibited similar problems.
Tell me if I have the progression of the symptoms right.
You launch the 3D game and things seem to be running fine. Then some random amount of time into the game - five or ten minutes - you notice something isn't right. There is crackling from the audio now and again. Also you notice the game has lost its smoothness and it begins to stutter and drop frames. If you push forward it eventually hard locks completely with the audio looping. If you wait sometimes the system managed to BSOD.
You may have even attempted to quick exit the game when you see the stuttering and the crackling audio occur. You can see the continued stuttering behavior with the mouse cursor on the Aero desktop. Sometimes it locks up on the desktop regardless. Other times you're fast enough to manage to hit restart and watch the PC reboot successfully.
thr- wrote:Seems like the new BIOS update doesn't do anything for me to improve stability, I've been testing it with the warm reboot solution and it seems to work. Asus Inquiry couldn't do much about it except suggest a few things to test which I already did, after that they told me to RMA it at the point of purchase.
Ryu Connor wrote:Glad it seems to have settled for you. Clearing the CMOS and voltage adjustements haven't had much luck for me. Though BIOS 1307 is out now and among the fixes is the statement, "System Stability." I haven't had time to test yet.