Disabled verifier and everything seemed to be working just fine. Shut the computer down this morning before going to work and it hung on the "shutting down" screen. No record of it in event viewer at all and no minidump files???
I guess I'll hope for no "next time" and if it does I'll upload the log files.
Hello again. Got another BSOD today. I've made 1 change since my last post. I updated my mouse drivers (Logitech MX518). I had noticed the USB connect and disconnect noise a few times for what seemed like no reason. Then my pointer disappeared and reappeared. I double checked and Windows was using the default driver instead of the Logitech driver. SO I updated hoping that might solve the problem for good. No dice.
Here is the log. Thanks in advance.
Bump. The error this time was BAD_POOL_HEADER. First time I've seen that...
A little help please. Thanks!
Can you plan to update the BIOS? Apparently it is the same version, but the update date is newer.
Suggested BIOS update: Driver Details | Dell US
Attachment 325787
Your BIOS info:
Let us know if it is any helpful.Code:BiosVendor = Dell Inc. BiosVersion = 2.5.3 BiosReleaseDate = 11/22/2007 SystemManufacturer = Dell Inc. SystemProductName = Dell DXP061
_________________________________________
Code:BugCheck 19, {22, 200700ebdc000, 0, 0} GetPointerFromAddress: unable to read from fffff80003913100 GetUlongFromAddress: unable to read from fffff800039131c0 GetUlongFromAddress: unable to read from fffff80003881a38 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72e6 ) Followup: MachineOwner ---------
I updated the BIOS as requested. I had considered that before but didn't notice the update version was different only saw that it was the same version number so I did not go through with it. This time I flashed it with the newer update.
I noticed something odd today as well. I had left the computer on while away and it went into powersaver mode and had shut off the hard drives. When I woke it up my second partition on one of my drives (where my XP OS resides) would not respond. First partition (where the actual XP OS is) on the same drive was active and accessible as was everything else. I decided to reboot to see if it came back online and the system went to the "shutting down" screen and would not go ahead and reboot. After waiting for quite some time I went ahead and shut it off manually. Waited for a bit and then booted back up. Checked my boot sequence and checked my XP install that is on that other drive. XP still runs like a dream when I boot into it. I rebooted again and went back into Windows 7 and everything came up fine. I noticed the event log showed that Windows 7 had "rebooted without cleanly shutting down" in the critical events section. There were also numerous occurrences on the following error:
IaStorV, Event ID = 9. And the details show this:
The device, \Device\Ide\iaStor0, did not respond within the timeout period.
Could this be causing/contributing to the problems?
Last edited by DrillHead; 16 Jul 2014 at 22:33.
I also disabled my Iomega 750MB drive in Windows 7. I only use this drive in XP so I figured it couldn't hurt to disable it under 7. I figured it could only help if this was causing my issues.
I know that making multiple changes can make it more difficult to isolate the actual cause of the problem but since I don't use it under 7 there was no need to have it enabled then anyway. One less factor in troubleshooting.
Good idea? Bad idea? I'm open to any input.
Most of the time everything seems to run flawlessly but the occasional BSOD and the occasional hang up when shutting down is irritating me. I have had such a clean running system for so long that I've become a bit OCD about these issues. I really want 7 to run as flawlessly as my XP OS always did and still does. I haven't experienced any such issues with my XP install... ever.
7 days and no crashes. So far so good Arch. Thanks for the help. I'll update again in 7 more days just to be sure.
Quote