BSOD,error 0x0000001e Dump Info Included, Help!

[twistertime]

Acer all in One running Windows 7 64 bit. Am getting the BSOD 0x0000001e when trying to attach pictures to email and also when I try to connect to my playbook through USB port or even through wireless network.
Included is a copy of the Dmp info.
Hopefully someone can help.
Thanks
Tony in Snowy Canada
System Information (local)
</B>
computer name:
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) CPU G6950 @ 2.80GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4151427072 total
VM: 2147352576, free: 1943621632



[FONT=Segoe UI, Arial]Crash Dump Analysis
</B>[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT][/FONT]

[FONT=Segoe UI, Arial]On Fri 30/12/2011 2:36:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123011-16458-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88006189CD0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 30/12/2011 2:36:16 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ksecdd.sys[/FONT] (ksecdd+0x21A3)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88006189CD0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\ksecdd.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Kernel Security Support Provider Interface
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 30/12/2011 2:00:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123011-15366-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880065CECD0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 30/12/2011 1:24:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123011-18844-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880047F3CD0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 30/12/2011 1:15:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123011-20654-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88006579CD0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 30/12/2011 1:11:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123011-22167-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88002662CD0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]
Conclusion
</B>[/FONT]
[FONT=Segoe UI, Arial]6 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



[/FONT]

 

[JMH]

No DMP included above...

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[twistertime]

Minidump file for BSOD, oxoooooo1e

Thank you so much for the help and now I believe I have the mini dump file you requested.

 

[twistertime]

More BSOD Dump Info

I did not have all my settings setup for the Dump file as you requested, here was the most recent file after I plugged in my Blackberry Playbook to the USB port.

Thanks again so much for all that have helped.
Happy New Year
Tony

 

[JMH]

twistertime / Tony.
Your problems were probably caused by Kernel Security Support Provider Interface.

To hopefully alleviate the situation...

> Please run the update readiness tool and then update to SP-1

Ensure you install the correct 64 or 32 bit option for your system)
Download the System Update Readiness Tool (64bit)
Download the System Update Readiness Tool (32bit)

http://windows.microsoft.com/installwindows7sp1


> Download Malwarebytes free version.
Update immediately.
Run a Full System Scan.

Let us know the results.
Good luck & Happy New Year to you too.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!

 

[twistertime]

BSOD Update

Took the SP1 update and it was succesful. Did the Malware check and it found nothing. Plugged my Blackberry Playbook into the USB port and Windows recognized it and installed a driver for the Playbook and then....BSOD, included the dump file- 010112-24336-01.
So I rebooted the computer and went to post a reply to this thread and when I clicked on the browse button to attach the dump file......BSOD!I have attached a second dump file for the second BSOD, it is file 010112-18142-01. So I rebooted in Safe Mode with Networking and now I am posting these 2 dump files for help ( they may show the same thing but I thought I would post all details of what happened along with the files).
I can tell you this much, since taking the iupdates it does not seem to be any different then it has been all along.

Thanks for your help and Happy New Year!

 

[JMH]

These crashes were caused by memory corruption (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!!!


1-Memtest.

*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 or 6 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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data 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).

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"
- 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. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

Old drivers you have there may be problematic as indeed AVG.
Yet to be determined.

 

[twistertime]

BSOD Update

Thanks for the reply/help.Here is an update even though longer testing is being run as we speak.

Did the memtest 6 times over and there were no faults found.

Did the Driver Verifier as stated in an earlier post by JMH and I rebooted and ran the computer with no issues for several hours. Decided to try and create the fault as it was created before by plugging in the Blackberry Playbook to my USB port. The computer faulted out after plugging in the Playbook but did not give me a BSOD it actually just rebooted ( this being different then when not running driver verifier as I would get a BSOD).
I did not see anything from Driver Verifier? Should a fault show in a popup window if it detects something from the non microsoft drivers?

Thanks again for your patience.
Tony

 

[JMH]

Thanks for the reply/help.

I did not see anything from Driver Verifier? Should a fault show in a popup window if it detects something from the non microsoft drivers?

Thanks again for your patience.
Tony

Re Driver Verifier.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

If it crashes a Dmp file should be produced for us to further analyze.

 

[twistertime]

BSOD Update

I do see what you are trying to do with the "OverTaxing" the drivers to get it to happen.Before the changes to the Verifier setup there were 2 ways to get the BSOD, plugging in the Playbook and also attaching a file to an email/post would create the error and thus a dump file. Now when I do this same condition I do not get the BSOD, it just reboots and with the non BSOD then there is no dump file and this is new since the changes. So I am wondering if it faults out on it's own will it just reboot and tell us nothing?
Does this information help in any way?
It has been 12 hours and no faults when running normal without tying to cause the issue as stated above.

Thanks again,
Tony

 

[JMH]

Ok.
Verifier is pointing to nothing at this point it appears.
Continue doing what you normally do.
If / when you get another crash submit the new DMPS for analysis.

 

[twistertime]

BSOD Update

No BSOD's since setting up the verifier 40 hours ago. Only time I had any issue was when the system rebooted when I plugged in the Playbook, but it just rebooted windows, no BSOD, and I still can't ever connect to the Playbook to transfer files.

Should I undo the verfier setup?
Any next steps?

Thanks
Tony

 

[JMH]

Disable Verifier.
All looks positive ATM.
See how you go.
I would love another good report after about a week.
Good luck!

 

[twistertime]

BSOD Update, all good now.

Although there was no BSOD issues when the sytem was running, I still could not connect with my Blackberry Playbook or upload files to an email without causing the system to reboot. Decided to reload the OS as this computer is only 1 year old. Backed up files and reloaded the system to the way it was when I got it. Now this computer is operating as it should without any reboots and I can upload files and connect to the Playbook. Not sure which driver was hanging the system or if there was a virus in the system up but it is no longer.Will continue to watch the system to see whn and if things change and what may be causing it ( new updates, new software,...)
Purchased a copy of Kaspersky 2011 Internet Security and loaded this on when I did the restore.
This has been a great learning experience and with everyones help it has greatly helped.
Thanks again
Tony

 

[zigzag3143]

Congrats on the clean install, often it is the fastest, most sensible way to resolve a driver problem.

Now the bad new. Kaspersky is known to cause BSOD's on some systems, so if you start getting them keep this in mind.


Good Luck and good job.




I do notice Kaspersky which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST.

http://support.kaspersky.com/downloads/utils/kavremover10.zip

http://www.microsoft.com/security_essentials/

 

[JMH]

Tony,
It has been a delight working with you... Well done too!
Hope all goes well.
Kaspersky....may have been better had you consulted us first...
Good luck! {Yet again}