BSOD in Sleep Mode

[sman5922]

Hi again,

I posted a while ago on this thread and I've been following it because my problem is just so similar. Can you please describe to me the state of your problem now? Like did anything change. I also get the random BSOD, but usually at wake-up. I also have a 320 GB HDD. I'm really wondering if its the hotfix that will help. By the way, could you please tell me where the stop errors would be shown?

sman5922
My desktop only bsod's at wake up from sleep, at least so far.Since you have a laptop, I'm not sure if the fix will work for you. Follow the advice of usasma, torrentg and the rest, they are trying to figure this out for you, and it may help someone else along the way.
I've reset the "auto restart after failure" in BIOS so I can read the stop error codes before restarting.
You really do need to fill out your system specs.
kcburgie

I think the fix will help you out. I'm starting to doubt it will help me because I don' think I get those same stop errors. Even if the fix does work for me, I'm just going to wait for the update now that MS knows about it. Could you tell me what error message you get? I used to get a variety now its narrowed down to "Bad_Pool_Header" and "Memory Management".
I finally did fill out my system specs as best as possible.

 

[kcburgie]

sman5922
I've been getting 7A, Kernel_Data_Inpage_Error, and F4,Process or thread has exited or terminated, errors.
Thanks for filling out your specs.

kcburgie

 

[kcburgie]

usasma
After several attempts at down loading the hotfix, I had to call MS support. The tech I talked to said the hotfix is" temporarily unavailable for download" He couldn't access it either. It may be getting an face lift or readied for ? This could not be confirmed as the research dept was closed. I should hear back from him on Tuesday.

In the mean time he suggested some things to try, but when I told him I had already done them, the list pared down to just a few. He did say to try the new HDD I had ordered, so what the heck.
You and the staff have done an awsome job at staying ahead of the game.

kcburgie
PS. just to clear a point; the "Auto Restart on failure" settings are in system, advanced settings and not in BIOS as I stated in an earlier post. Sorry if this caused confusion sman. If it weren't for bad memory, I may not have any memory at all.

 

[sman5922]

usasma
After several attempts at down loading the hotfix, I had to call MS support. The tech I talked to said the hotfix is" temporarily unavailable for download" He couldn't access it either. It may be getting an face lift or readied for ? This could not be confirmed as the research dept was closed. I should hear back from him on Tuesday.

In the mean time he suggested some things to try, but when I told him I had already done them, the list pared down to just a few. He did say to try the new HDD I had ordered, so what the heck.
You and the staff have done an awsome job at staying ahead of the game.

kcburgie
PS. just to clear a point; the "Auto Restart on failure" settings are in system, advanced settings and not in BIOS as I stated in an earlier post. Sorry if this caused confusion sman. If it weren't for bad memory, I may not have any memory at all.

The hotfix is probably being put into the update for Tuesday. No confusing caused. I already knew the settings and where they were located. Thanks.

 

[socks]

So I seem to be having the same issue as a lot of others, windows crashing when returning from sleep. I have included the .dmp files below, if someone could take a look at them and point me in the right direction I would be very grateful. Additionally, what application can I use to actually see the .dmp files for myself, as they seem to be stored in some format I'm not familiar with, and the only thing willing to open them is visual studios.

--------------------------------------------------------------------------------
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000096
BCP2: FFFFF8800894B838
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\010210-19921-01.dmp
C:\Users\Cort\AppData\Local\Temp\WER-272580-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Highlights - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

---------------------------------------------------------------------------------

 

[Capt.Jack Sparrow]

So I seem to be having the same issue as a lot of others, windows crashing when returning from sleep. I have included the .dmp files below, if someone could take a look at them and point me in the right direction I would be very grateful. Additionally, what application can I use to actually see the .dmp files for myself, as they seem to be stored in some format I'm not familiar with, and the only thing willing to open them is visual studios.

--------------------------------------------------------------------------------
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000096
BCP2: FFFFF8800894B838
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\010210-19921-01.dmp
C:\Users\Cort\AppData\Local\Temp\WER-272580-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Highlights - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

---------------------------------------------------------------------------------

Hi Welcome to SF,

[FONT=Segoe UI, Arial]On Sun 1/3/2010 1:55:21 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ampcore.sys[/FONT]
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF88008B5B838, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
Dump file: C:\Windows\Minidump\010210-21309-01.dmp
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Sun 1/3/2010 1:55:21 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ampcore.sys[/FONT]
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF8800894B838, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
Dump file: C:\Windows\Minidump\010210-19921-01.dmp
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

Those dump files are referring to AMPCORE.sys
Have you installed CodeAnalyst ?? If so try to reinstall that and see if that fixes the problem.
Also try to disable CALoadService from services see whether your getting Blue Screens.
Start > Services.msc > search for CALoadService Right Click and Properties
Change the startup type to disabled

Hope this helps

 

[socks]

Thanks Captain, I hope that fixes the issue. Also, for the future, what program did you use to view the dump logs?

 

[Capt.Jack Sparrow]

Thanks Captain, I hope that fixes the issue. Also, for the future, what program did you use to view the dump logs?

Your Most Welcome Mate.
You could use Blue Screen Viewer
In case if this didn't work post us back we should be able to help you out

 

[kcburgie]

usasma et al

One week since I tried to download the hotfix, hours on the phone to MS, a new HDD, some testing, aaand, no help ! MS wouldn't let go of the fix ( "not available for public download" ) and said that I need a BIOS update that is not available. I'll try and jack up HP , but I've run into a wall a couple times before. A new motherboard with a real BIOS may be in order. Until then I guess I let it run. This install doesn't seem to freeze like the last one.

While testing the MS ideas the comp blue screened three times, just when they thought it was fixed. 7A s, Kernel_Data_Inpage_Error. According to BlueSceen View, caused by ntoskrnl.exe, but thats all I can make of it. I'll attach the dumps if you care to look at them.

Anything else you can think of let me know.
Thanks again for all you help!
kcburgie

 

[usasma]

We look for consistency in BSOD's in order to get clues as to what's going on.
In this case the last 3 BSOD's were STOP 0x7A's ( BSOD Index )

With this sort of consistency (and the presence of System Services in the stack text) - I'd suggest running Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[kcburgie]

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

 

[usasma]

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:

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

 

[kcburgie]

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

 

[usasma]

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:

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

 

[kcburgie]

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

 

[thunderclap]

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.

 

[kcburgie]

thunderclap

Unfortunately, my BIOS doesn't have these options, it is very basic. Proprietary C from HP, and no updates are available.

kcburgie

 

[usasma]

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.

 

[kcburgie]

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

 

[usasma]

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.