usasma
Ran the verifier as asked. After a couple of freezes and a hang in the startup page, I got an F4 BSOD on wake up. Same culprit, but different stop code. Dump file attached.
AS suspected, HP was not much help with any info on a BIOS update. They MAY be able to check things for $50! They blamed the software, where MS blames hardware. Like two kids trying to stay out of trouble. Of the two, MS is easier to deal with.
I feel like I'm in good hands right here!
kcburgie
You ran Driver Verifier with settings designed to stress 3rd party (non-Microsoft) drivers.
Yet Driver Verifier blames csrss.exe (a critical part of the Windows Operating System)
So, we can draw some suppositions from this:
- if the 3rd party drivers were verified, and didn't cause the crash, then we presume that they're OK (we hope this is true)
- if Windows is corrupted/infected, it's possible that that could be causing the crashes. You've run malware scans so we can presume that the system is clean. That leaves OS corruption as a possibility.
- or, it's possible that a hardware fault is causing the crashes.
So, the procedure is to reinstall Windows in a clean, vanilla installation to make sure that Windows isn't at fault. We do this because it's easier and cheaper than testing the hardware (by replacing parts).
I like to rerun Driver Verifier with different settings to see if it'll point to Windows or hardware (it'll help with the decision between installing Windows and hardware testing (and may help in narrowing down the options).
To do this, please reset Driver Verifier to test ALL drivers. This will slow your system down to a crawl, but it shouldn't take that long to get a BSOD. Please post it back for us to have a look at.
BSOD summary:
Code:Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Jan 7 20:16:12.223 2010 (GMT-5) System Uptime: 0 days 0:45:13.299 BugCheck F4, {3, fffffa8004596410, fffffa80045966f0, fffff80002d91240} Probably caused by : csrss.exe PROCESS_NAME: csrss.exe DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
usasma
Reran verifier with the settings you recommended, never really got to the wake up from sleep. It blue screened as soon as I restarted, an 0x0A, IRQL Not_Less_Or_Equal. Restarted Windows normally, even though the option was there to do a repair. Avira virus scan started, so I let it run, 2 and 1/2 hours instead of the normal 15 minutes, no detections. After, I tried to put it to sleep and got a 0xC9 error, IO manager driver violation twice and once on a restart after the monitor failed to come out of stand-by, all point to CAX_CNXT.sys. Conexant modem?
I am currently running a "plain vanilla" install on the new HDD, no other drivers than the Windows Update. Only AV and DSL programs. Can't get more basic than that.
Maybe the modem driver didn't install correctly? 4 minidumps attached.
Let me know what you find and thanks for all your patience.
kcburgie
Good work! 3 of the 4 BSOD's are Driver Verifier Minidumps - and they point to the CAX_CNXT.sys file - which is a component of your Conexant modem. Because this is a clean install, I'd suspect that a malfunction of the modem hardware is more likely than a driver issue.
So, I'd uninstall any software for the modem using Control Panel... Programs...Uninstall a program.
Then uninstall the device in Device Manager (right click and select "Uninstall")
Then open the case and remove the card from the computer.
This will solve any software/driver/hardware problems with the modem.
If you need a modem, please purchase another one rather than attempting to use this one.
Summary of the dump files:
Code:Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Jan 9 14:33:48.495 2010 (GMT-5) System Uptime: 0 days 0:00:43.602 BugCheck A, {0, 2, 0, fffff80002aa8a83} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Jan 9 18:31:00.449 2010 (GMT-5) System Uptime: 0 days 3:42:04.556 BugCheck C9, {228, fffff88004266b04, fffff9803b63cc10, 0} *** WARNING: Unable to verify timestamp for CAXHWBS2.sys *** ERROR: Module load completed but symbols could not be loaded for CAXHWBS2.sys *** WARNING: Unable to verify timestamp for CAX_CNXT.sys *** ERROR: Module load completed but symbols could not be loaded for CAX_CNXT.sys Probably caused by : CAX_CNXT.sys ( CAX_CNXT+63b04 ) DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Jan 9 19:15:46.600 2010 (GMT-5) System Uptime: 0 days 0:37:02.582 BugCheck C9, {228, fffff8800412bb04, fffff98028b34c10, 0} *** WARNING: Unable to verify timestamp for CAXHWBS2.sys *** ERROR: Module load completed but symbols could not be loaded for CAXHWBS2.sys *** WARNING: Unable to verify timestamp for CAX_CNXT.sys *** ERROR: Module load completed but symbols could not be loaded for CAX_CNXT.sys Probably caused by : CAX_CNXT.sys ( CAX_CNXT+63b04 ) DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Jan 9 19:57:29.764 2010 (GMT-5) System Uptime: 0 days 0:26:21.870 BugCheck C9, {228, fffff88003d0bb04, fffff9802ab90c10, 0} *** WARNING: Unable to verify timestamp for CAXHWBS2.sys *** ERROR: Module load completed but symbols could not be loaded for CAXHWBS2.sys *** WARNING: Unable to verify timestamp for CAX_CNXT.sys *** ERROR: Module load completed but symbols could not be loaded for CAX_CNXT.sys Probably caused by : CAX_CNXT.sys ( CAX_CNXT+63b04 ) DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System
usasma
Uninstalled the modem, made sure it was gone in Device Manager, and scanned for any remaining remnants. Pulled the modem from the case. Rarely use it anyway.
Put the computer to sleep and on the second wake, 0x7A, ntfs.sys. The modem might have been "a" problem, but not "the" problem. Doesn't seem to matter which drivers or power settings I use, I just can't let it sleep. Its got to have something to do with start up sequence. It worked in Vista, but not in 7, at least on this computer. To bad you can't tune a computer with a hammer.
Thought we had it though!
One dump attached
kcburgie
Check your BIOS power management. Check the ACPI Suspend Type. Is it set to S3 or S1? Try changing it. I did and it fixed my problem. Or at least it appears to have.
thunderclap
Unfortunately, my BIOS doesn't have these options, it is very basic. Proprietary C from HP, and no updates are available.
kcburgie
This is one of them that blames something different from the WinDbg tool.
WinDbg blames win32k.sys, while BlueScreenView blames NTFS.sys
Please turn Driver Verifier back on for all non-Microsoft drivers.
usasma
Ran verifier with non MS drivers selected, one black screen, a couple of hangs at wake. I tried the startup repair option,but "Windows cannot repair this comp automatically" unknown bug check; 0x0,0x2,0x0,0xFFFFF80002A9FA83, result failed 0x490 was all I got. Two auto windows updates along the way.
Interesting that WinDbg and BlueScreen View came up with different results, one would think this would be universal. Bsv blamed ntoskrnl.exe this time. 3 Dumps attached.
kcburgie
These are Verifier enabled memory dumps - but they don't blame any non-Microsoft drivers (and that's what you're testing for). This suggests Windows corruption or hardware problems.
The next step is to get a couple of memory dumps when Driver Verifier is verifying ALL drivers.
That'll help us to see if it's a Windows problem or a hardware problem.
Quote