|17 Apr 2012||#1|
| || |
BSOD of on newly deployed laptops, ntoskrnl.exe, 0x0000000a
We have deployed around 45 new HP Probook 6360's. I have been getting many calls about BSOD issues. I'm having trouble pinpointing the issue. I'm thinking it is our VPN client, Junos Pulse, or our Proxy client, Bluecoat, but it may be driver related or memory related as well. I built the computers with Microsoft Config Manager, sysprepped the system, then made my image. We deployed out HP Elitebook 6460's with the same method and have no issues.
The probooks are running Windows 7 Pro - 64bit with 8gb of ram.
Can someone please look through these logs/files and give me an idea of what to try.
|My System Specs|
|17 Apr 2012||#2|
| || |
This was related to your Blue Coat Web Filter driver ( proxyclientwebfilter64.sys) Yours is dated Jan 2012 so I suspect no newer driver is available but I would check with the developer.
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
|My System Specs|
|17 Apr 2012||#4|
| || |
It is "read" using a specialized tool called WinDeBugger.
My pleasure on the response. I have been in your shoes and know how it feels.
If you want to investigate further there is a built in tool called verifier which you can run to watch for mis-behaving drivers. When it finds one it registers it and then crashes the system to ensure it is written into the DMP file.
I would also run a memory test (memtest) to make sure it isnt the ram causing it.
These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.
* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!
* If you have a Raid update its Driver.
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool
*Boot from the CD, and leave it running for at least 5-7 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.
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.
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/Windows 7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.
If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking
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.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
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.
Thanks to JGriff2 & Usasma.
Using Driver Verifier (Windows Drivers)
|My System Specs|
|Similar help and support threads for2: BSOD of on newly deployed laptops, ntoskrnl.exe, 0x0000000a|
|0x0000000a ntoskrnl.exe+75c00||BSOD Help and Support|
|BSOD ntoskrnl.exe with 0x0000000a||BSOD Help and Support|
|Windows 7 BSOD -0x0000000a ntoskrnl.exe||BSOD Help and Support|
|Freshly built PC with 2 random NTOSKRNL.exe 0x0000000a & 0x00000109||BSOD Help and Support|
|0x0000000a + IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe random BSOD, help :S||BSOD Help and Support|
|My computer is starting to have BSOD, error 0x0000000a ntoskrnl.exe||BSOD Help and Support|
|BSOD and Freezing 0x0000000a IRQL_less_or_equal ntoskrnl.exe+7cc40||BSOD Help and Support|
|Our Sites ||Site Links ||About Us ||Find Us |
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 11:08 AM.