Three computers in my household (all brand new, all on Windows 7 Home Premium 64-bit) are experiencing the same problem, they all experience blue screens of death every so often. The frequency of these crashes varies from once a week to several times a day with little rhyme or reason, and it seems to happen regardless of what I'm doing at the time. The most common bugcheck code is 0x0000007F, but I've seen others as well. I downloaded the Windows Debugging Tools and opened up my memory.dmp in WinDbg, hoping it would point me to a solution. Little of what I saw made sense to me, except for the part at the bottom that says "Probably caused by : NETIO.SYS". In one of the forum threads I read on a similar issue, someone recommended setting up driver verifier to fish for crashes and help pinpoint the cause, so I did just that. I set it up with these settings: verifier > create standard settings > select driver names from a list > selected all non-microsoft drivers Sure enough that seemed to expedite things and I got another crash soon after restarting. The minidump file associated with that crash can be found here: http://www.mediafire.com/?c9ng5384jkc9o7x Interestingly, it says the problem is probably caused by "ntoskrnl.exe". Also, FYI, the security programs I'm using on all three affected systems are: Avast anti-virus ZoneAlarm firewall Spybot Search & Destroy resident protection I've been told that ZoneAlarm can cause this issue, so I'll probably try removing that on at least one of the computers and see if that helps. I've also been told that disabling NetBIOS over TCP/IP can fix the problem, so I'll probably try that too. In the meantime, however, I'd appreciate some insight into what may be causing this problem. I really don't know how to properly analyze that minidump.

It is mostly caused by ZoneAlarm. remove it, please. The minidumps are not useful for UNEXPECTED_KERNEL_MODE_TRAP bug checks. Configure your system to creat a kernel dump [1]. If the system crashes again after removing ZoneAlarm, upload the zipped Kernel dump to your SkyDrive [2] and post a link here. André [1] http://www.brighthub.com/computing/windows-platform/articles/81867.aspx [2] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Understood, I'll let you know how it goes. :)

I removed ZoneAlarm on all three affected PCs, they've been fine for the most part but one of them (the one that was crashing most frequently previously) has blue screened again. It has a different error code now, though: 0x0000001e. I tried to upload the memory dump to Skydrive, but it's too big, so here it is on Mediafire. I hope that's not a problem.

// // MessageId: STATUS_ACCESS_VIOLATION // // MessageText: // // The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. // #define STATUS_ACCESS_VIOLATION ((NTSTATUS)0xC0000005L) check the RAM for errors, please. It happens while running thunderbird.exe which doesn't load any drivers."A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

That was one of the first things I tried, weeks ago now. I ran Windows memory diagnostic off the Windows 7 CD. It completed many passes (24, I believe) and found no errors. I also tested the memory with memtest86 (10 passes), no errors reported. Just to be sure, I also swapped out both memory sticks with some fresh replacements I had laying about, but the problem persisted so I reversed the change. Of course, Zone Alarm was still installed at that time, but still, I'm pretty confident there's nothing wrong with the memory. By the way, the same computer got another blue screen after a few hours. Again, with a different error message, this time 0x00000024. A bit of quick research indicates that this is some kind of file system issue. This makes me think that the previous crashes (all code 7F, probably caused by ZoneAlarm) have broken something, so I'll do a checkdisk at the earliest convenience. Here's the memory dump associated with this crash. I'm willing to test the RAM again if you think it's worth it, but I'm fairly sure that's not the cause. Also, you should know that I plan to reinstall Windows on the machine in question (the one that has crashed after ZoneAlarm's removal) anyway, so I don't have qualms about that either.

By the way, the same computer got another blue screen after a few hours. Again, with a different error message, this time 0x00000024. A bit of quick research indicates that this is some kind of file system issue. Bug Check 0x24: NTFS_FILE_SYSTEM - This indicates a problem occurred in ntfs.sys , the driver file that allows the system to read and write to NTFS drives. run chkdsk /r /f to detect and fix issues with your HDD."A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

After the disk check the computer in question went for two weeks without any trouble, but today it started giving some errors such as "X has stopped working and has to close". This is a second-hand report because I wasn't there to see what applications crashed, but the person who was using the computer at the time told me they were Windows components of some sort. About an hour after those error messages, it blue screened with the code 0x0000003b. Memory dump here . Upon starting up after this the system took much longer than it usually does to get up and running after I logged in, and various applications that usually come up right away took several minutes to begin functioning. Also, Event Viewer crashed twice while I was trying to use it to look at the details of the crash, and other Windows background components crashed (with "X has stopped working" error messages), I don't recall what they were called exactly, one of them may have been "Windows Update Module". Anyway, I then ran a system file check (run: sfc /scannow), but it seemed to finish prematurely and gave no report, so I ran it again and watched it this time, it stopped at 27% and gave some kind of message (perhaps an error) before disappearing an instant later. Not a good sign. A short time later it blue screened a second time, with the error code 0x00000019. Insight into what caused these crashes would be helpful. Neither of the other two computers have given any problems since I removed ZoneAlarm from all three, so I'm thinking that perhaps the previous blue screens have simply crippled this Windows installation in some way, causing it to continue to be unstable. If that's the case I'll probably reinstall Windows.