Windows Dump File, unsure of cause

Hi All

Can somebody please help me in working out what my dump file is caused by?

I have saved it as a text file after placing it through the windows debug.

Thankyou

centrehelpdesk said:

Hi All

Can somebody please help me in working out what my dump file is caused by?

I have saved it as a text file after placing it through the windows debug.

Thankyou

Love to help but even after renaming, it still is of an incorrect format. where is the file that was originally created?


can you upload that to us??




Ken

Hi Ken

Thanks for the quick response, absolutley, I have now attached the .DMP file, I should mention that this is a Terminal Server Virtual Machine.

Does anyone have any clue? This is a production terminal server, and it fairly critical that we fix this

thanks all

Hello there

Have not received any reply on this, does anyone at all have any idea?

centrehelpdesk said:

Hello there

Have not received any reply on this, does anyone at all have any idea?

Doing the DMP now but surely there must have been more than one since then upload a bunch of them if you can


Ken

Cause

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.
This bug check is usually caused by drivers that have used improper addresses.


From the BSOD NETIO.SYS is blamed usually that is caused by Zone alarm remove it and replace with Microsoft security essentials

http://download.zonealarm.com/bin/fr...cpes_clean.exe

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

Run driver verifier to identify which driver is at fault If zone alarms removal doest stop the BSOD's continue below with the drivers.

Beyond that, please run Verifier with these settings:

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"
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.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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

Run memtest to test your memory
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. 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.



Old drivers

Code:

ino_flpy.sys        fffff880`012d2000    fffff880`012dd000    0x0000b000    0x44ae4058    7/7/2006 07:07:04                        
ino_fltr.sys        fffff880`03816000    fffff880`03849000    0x00033000    0x44ae4066    7/7/2006 07:07:18                        
PROCEXP111.SYS        fffff880`0448e000    fffff300`04496000    0xfffffa8000008000    0x47194089    10/19/2007 19:40:57                        
E1G6032E.sys        fffff880`0302e000    fffff880`03051980    0x00023980    0x483de76b    5/28/2008 19:14:51                        
vmmouse.sys        fffff880`013e3000    fffff880`013eb000    0x00008000    0x48e07f25    9/29/2008 03:09:25                        
spldr.sys        fffff880`018e8000    fffff880`018f0000    0x00008000    0x4a0858bb    5/11/2009 12:56:27

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Uninstall any virtual drive apps like daemon tools/alcohol120

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
[/quote]
You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

Thankyou very much for the above, should go a long way in working out the cause.
Unfortunately this is a production terminal server so I cannot run tests till everyone is off, however will do in the next comming weeks.