Constant crashes

[whiskey212]

I apologize if this has already been addressed elsewhere but I haven't found it, so here goes: my system has been running just fine for a long time now and all ofa sudden I have had a whole series of BSODs. I've seen "Bad Pool Header", "Page file in non-paged area", and a few others but the most common one is "Memory Management". I went in and removed the most recent item I had installed (a PCI SATA expansion card) and the accompanying drivers but this had no effect. I downloaded/ran memtest for hours and found not even a single error. I have used several different HDDs with fresh Windows installs and again the problem recurs. I have eliminated memory/hard drives/corruption/bad drivers as the causes but the problem persists. I am at my wits end here, if anyone can help me with this problem I would be most grateful. Thanks, Kris.

 

[Jonathan_King]

Welcome to SF!

Please upload your dmps: http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums-analysis.html

 

[whiskey212]

update

I believe I have traced the problem to a faulty driver for an external USB hub (Belkin 7 port part #F5U237v1). There is no driver to install from the manufacturer ,or if there is I can't find it, so the bad driver originated from Microsoft itself, thanks Bill. Anyways, I have removed the offending item and have been running for almost a day without incident. I will post again in a day or two with an update and will try again with the SATA expansion card I falsely assumed to be the original issue. Oddly, all through running Vista for years this hub showed in my device manager as being problematic but never once caused a problem and actually worked as advertised for years every time i used it, weird.

 

[Jonathan_King]

Well I hope that's it. USB hubs do cause BSODs at times.

Let us know if you need more help.

 

[HMonk]

Just for kicks, you might review EV to see if the crashes were logged and, if so, follow the link to determine if the issue has been addressed. In the BKG, I run WhoCrashed (freeware), which you can find here. I do so because it often gives me crash data and solutions that EV will not.

Monk

 

[whiskey212]

So, no sooner do I return from work that I have found yet another BSoD. For s**ts and giggles I installed to a known functional hdd and not long after getting that running ( including Kaspersky, updates, etc.) it crashed again, only this time it refused to boot, AT ALL! Went back to my previous configuration and installed BlueScreenView and the really odd thing is that it seems all the probs are caused by some file or another in the Windows kernel itself. The drivers at fault are: hal.dll, ntoskrnl.exe (several times) and nvstor.sys I went through and did a system file check on the off chance of a corruption but none was found. I am wondering now if there is a corruption of the Windows installation disc itself as that seems to be the only real connection between all my problems installs. Anyone heard of this cause/effect situation? Anyone have any other thoughts or ideas? For what its worth, I can usually run for a day or so before the first crash then if I reboot immediately the next one comes much sooner and they seem to proceed exponentially faster until I let it sit for a while. None of my testing (Prime95, etc.) seem to indicate any heat-related issues that this sequence would first indicate.

 

[Tews]

[1 - Novice] How to ask for help with a BSOD problem

 

[whiskey212]

As requested here is a zipped file containing the 6 dump files...

 

[whiskey212]

Thanks for the assistance.

[1 - Novice] How to ask for help with a BSOD problem

 

[Jonathan_King]

I was going to suggest to suggest a memory test, but it looks like you already have that covered.

Let's take a look at your bugchecks:

Bugcheck code 00000050
Bugcheck code C0000221
Bugcheck code 0000001A
Bugcheck code 0000001A
Bugcheck code 00000050
Bugcheck code 00000019

Here is the summary for BC 50:

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

C0000221:

Usual causes: Device driver, System DLL corruption, Faulty hardware in I/O path (a disk error, faulty RAM, or a corrupted page file), BIOS

1A:

Usual causes: Device driver, memory, kernel

19:

Usual causes: Device driver

Taken from here: http://www.carrona.org/bsodindx.html#The_BSOD_Listing

I'd say we can assume it is a device driver. The dmps do not tell us which one caused the problem:

[FONT=lucida console]
BugCheck 50, {fffffba011207ae8, 0, fffff8800131b603, 7}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushUserStream+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck C0000221, {fffff8a000145130, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5ff )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {41790, fffffa8001986b10, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {5003, fffff70001080000, 1a6d, 1a6f0000345a}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b86 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {fffffa7fffffffea, 0, fffff80002cb3deb, 7}
Probably caused by : memory_corruption ( nt!MiMapPageInHyperSpaceWorker+1b )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 19, {3, fffffa8009cae310, 0, fffffa8009cae310}
Probably caused by : Pool_Corruption ( nt!ExFreePool+75b )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/FONT]

Let's run a stress test on all of your 3rd party drivers and see which ones break. Please follow these instructions: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Once that's running, just go about your normal work and post the new dmps.

In the mean time, update these old drivers. They may or may not be causing the issue, but still...

fffff880`01600000 fffff880`01617000   tifsfilt tifsfilt.sys Wed Aug 29 08:37:29 2007 (46D56889)
fffff880`016f8000 fffff880`017a8000   timntr   timntr.sys   Wed Aug 29 08:38:23 2007 (46D568BF)
fffff880`01a40000 fffff880`01ad4000   tdrpman  tdrpman.sys  Mon Nov 12 08:36:33 2007 (473856E1)
fffff880`01adc000 fffff880`01ae3000   speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798)
fffff880`01ae3000 fffff880`01b1e000   snapman  snapman.sys  Thu Nov 22 03:19:33 2007 (47453B95)
fffff880`05248000 fffff880`0525c380   pcouffin pcouffin.sys Tue Dec 05 09:39:30 2006 (457584A2)
fffff880`052f7000 fffff880`0535ad80   nvm62x64 nvm62x64.sys Fri Oct 17 17:01:06 2008 (48F8FD12)
fffff880`058f5000 fffff880`059a3000   ctac32k  ctac32k.sys  Wed Jul 02 04:38:22 2008 (486B3E7E)
fffff880`08c71000 fffff880`08c7b980   LVUSBS64 LVUSBS64.sys Sat Jul 26 11:06:36 2008 (488B3D7C)
fffff880`09200000 fffff880`092bf580   lvrs64   lvrs64.sys   Sat Jul 26 11:09:02 2008 (488B3E0E)
fffff880`092f5000 fffff880`09574180   LV302V64 LV302V64.SYS Sat Jul 26 11:09:08 2008 (488B3E14)
fffff880`09575000 fffff880`09577380   lv302a64 lv302a64.sys Sat Jul 26 11:06:31 2008 (488B3D77)
fffff880`08c71000 fffff880`08c7b980   LVUSBS64 LVUSBS64.sys Sat Jul 26 11:06:36 2008 (488B3D7C)

Updating your Logitech camera software will take care of most of them.

 

[whiskey212]

Now i've got a real problem; I can't login to any of my Windows installs now (currently in my Linux distro). Bluescreens after the splash screen, just before windows actually loads. I am getting an odd notice at the bottom of the screen at that point, something about a ROM error I believe the exact wording was: "Warning: Have option ROM cannot be invoke", whatever the hell that means. Basically I'm screwed here: I can't access my system in normal or safe mode which means I can;t even get to the dump files to offer them as a tool to diagnose the problem. I'm desperate here, any help at all would be amazing, thanks.

 

[Jonathan_King]

Try a system restore from the repair or install disc.

 

[HMonk]

At this point I am not clear as to what you are able to access and is it the issue related to your OS, BIOS (ROM error), or ODD (ROM error). It appears that you would like to avoid a clean install.

Again, not knowing what works and does not, one route you can take, if only as a diagnostic step, is to boot to the BIOS setup, select you other ("storage") HDD as the boot drive and boot from the Windows disc. Then install Windows on that HDD.

Once accomplished you have full access to your original boot drive which you can check for errors, read log/dmp files, etc. as a means of trying to figure out what is going on. If all else fails, you can recover (copy) files that are not part of the OS per se (e.g., FF profile, IE bookmarks, Outlook *.pst, DT files, saved games, etc.) which would be lost if you have to accomplish a clean install. I used this technique for many years dual booting 2000/XP much to my relief. Another less precise option would be to boot with a Linux boot disc (I'm thinking primarily of Knoppix which is based on the Debian platform). If you are able to repair you present OS, then go back to the BIOS, reset it as the boot disk and then delete the trial install from your storage disk.

I mention this only because I ask myself, "Why not just do a clean install?" Perhaps I am missing something.

Monk

 

[whiskey212]

So, now I had manged to reinstall Windows, again, and had it running for a few days with no issues. By the way, I flashed the BIOS to the latest version provided by XFX. I have installed all the most up to date drivers for my components directly from the manufacturers. Now I'm getting a bluescreen immediately after boot, right before the Windows login appears (page fault in non paged area) this time. It also failed to boot at all once, presenting 5 beeps at POST and crashing right away without presenting a bluescreen at all. At this point I am at a complete and total loss; it HAS to be the windows install somehow as there are absolutely zero issues when I am using Linux. Beyond that, I haven't got a clue. I hate to say this but I think I'll just go back to Vista, that ran for 2 years without this crap happening.

 

[whiskey212]

At this point I am not clear as to what you are able to access and is it the issue related to your OS, BIOS (ROM error), or ODD (ROM error). It appears that you would like to avoid a clean install.

Again, not knowing what works and does not, one route you can take, if only as a diagnostic step, is to boot to the BIOS setup, select you other ("storage") HDD as the boot drive and boot from the Windows disc. Then install Windows on that HDD.

Once accomplished you have full access to your original boot drive which you can check for errors, read log/dmp files, etc. as a means of trying to figure out what is going on. If all else fails, you can recover (copy) files that are not part of the OS per se (e.g., FF profile, IE bookmarks, Outlook *.pst, DT files, saved games, etc.) which would be lost if you have to accomplish a clean install. I used this technique for many years dual booting 2000/XP much to my relief. Another less precise option would be to boot with a Linux boot disc (I'm thinking primarily of Knoppix which is based on the Debian platform). If you are able to repair you present OS, then go back to the BIOS, reset it as the boot disk and then delete the trial install from your storage disk.

I mention this only because I ask myself, "Why not just do a clean install?" Perhaps I am missing something.

Monk

I have done this already, on 2 other discs that I know to be functional and the problem repeats on all of them. As for the Linux idea: I already use Kubuntu fairly often and have it installed on another drive. When I wok from there I have had none of the problems that Windows have shown.

 

[HMonk]

If you are able to do a clean install of Windows, do so, first reformatting the install partition. Once the reinstall is accomplished, DO NOT upgrade any drivers. Next launch the mobo install disc and let it install the mobo drivers. Then use the computer for a while to see if the BSOD recurs. If not, I think you may rightfully assume yours is a driver issue. Then, one-by-one, upgrade drivers, saving any graphics drivers for last. Pause between each upgrade to observe performance for a while. Lastly, using your install disc, install your gfx drives/software. DO NOT upgrade the gfx driver at this point other than that which is on the original install disc. Observe performance for a while. Lastly, if there is a driver upgrade available, uninstall your current gfx driver, then install the upgrade, i.e., NEVER overwrite an existing gfx driver with an upgrade. If the system is still stable after all of this, one-by-one, start reinstalling any apps and endure the wait-and-see strategy after each.

I appreciate your frustration but I think it fair to say that there is no inherent incompatibility between Windows 7 and your system. So it remains to tweak the BIOS, OS, drivers, and other SW until you ID the culprit.

Go back to Vista? Nah. You've crossed the Rubicon, lad: there's no turning back now.

Monk