New
#1
I can't seem to stop crashing
This is driving me nuts! I am having one hell of a time with my system. I believe the source of my crashing is my video card but I'm not positive. I really need some help solving this one.
This is driving me nuts! I am having one hell of a time with my system. I believe the source of my crashing is my video card but I'm not positive. I really need some help solving this one.
3. Run a System Health Report - START | type perfmon /report - a viewer will appear | Save as an HTML file (default file extension) - This opens the monitor window only it does not generate a report. I need to know what to monitor and where it it saved to and how to stop the monitoring.
I wonder if your overclocked hardware is the cause. Please remove Riva Tuner completely, and restore all hardware to default settings.
See if you can find an update for your Intel storage controllers on the manufacturer's web page:Instead of running the SF Tool or uploading the new dumps, please follow these directions as usasma asked, if you get more BSODs: https://www.sevenforums.com/crashes-d...tructions.htmlCode:iaStorV.sys Wed Apr 08 12:57:17 2009
...Summary of the Dumps:If that doesn't work, please enable driver verifier: Using Driver Verifier to identify issues with DriversCode:Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Tue Jul 20 15:30:06.504 2010 (UTC - 4:00) System Uptime: 0 days 0:02:06.283 BugCheck 50, {fffff08002d0ee48, 0, fffff80002dfa0bf, 7} Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 ) BUGCHECK_STR: 0x50 PROCESS_NAME: firefox.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Wed Jul 21 21:38:08.555 2010 (UTC - 4:00) System Uptime: 0 days 0:40:04.445 BugCheck 50, {fffff0a00a6b1180, 0, fffff80002f97a8f, 7} Probably caused by : ntkrnlmp.exe ( nt!CmpConstructName+20 ) BUGCHECK_STR: 0x50 PROCESS_NAME: LULnchr.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Wed Jul 21 21:57:25.750 2010 (UTC - 4:00) System Uptime: 0 days 0:06:41.640 BugCheck 1A, {41790, fffffa8005856f30, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 ) BUGCHECK_STR: 0x1a_41790 PROCESS_NAME: LWS.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Wed Jul 21 21:49:11.263 2010 (UTC - 4:00) System Uptime: 0 days 0:07:22.153 BugCheck 7A, {1, ffffffffc0000005, fffffa800aec4060, fffff68000072000} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : win32k.sys ( win32k+b3bbd ) BUGCHECK_STR: 0x7a_c0000005 PROCESS_NAME: firefox.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Wed Jul 21 21:40:43.189 2010 (UTC - 4:00) System Uptime: 0 days 0:00:56.079 BugCheck 50, {fffff684003bac20, 0, fffff80002dd8e37, 5} Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+97 ) BUGCHECK_STR: 0x50 PROCESS_NAME: SDWinSec.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Wed Jul 21 20:55:12.736 2010 (UTC - 4:00) System Uptime: 0 days 4:48:24.626 BugCheck 50, {fffff0a0016e9b48, 0, fffff80002fb757e, 7} Probably caused by : ntkrnlmp.exe ( nt!CmpDelayDerefKCBWorker+d6 ) BUGCHECK_STR: 0x50 PROCESS_NAME: System ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
I had already tried the first couple of points, so I followed your tip to go to msi and reinstall the driver. I wandered over to msi and reinstalled all of the drivers listed. It's been a day and a half so far and so far so good.
Great, thanks for the report!
Glad it's working better now...hopefully it will stay that way!