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.
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
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.
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,
Those dump files are referring to AMPCORE.sysOn Sun 1/3/2010 1:55:21 AM your computer crashed
This was likely caused by the following module: ampcore.sys
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF88008B5B838, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\010210-21309-01.dmp
On Sun 1/3/2010 1:55:21 AM your computer crashed
This was likely caused by the following module: ampcore.sys
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF8800894B838, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\010210-19921-01.dmp
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
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 :)
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
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
Quote