BSODS ...ntoskrnl.exe

[Gooman]

Hi all,

New to the forum. I built this Windows 7 64 bit system back in march or april. I have had random BSOD from the start. They were infrequent and for about a 2 or 3 month period, they went away and the system ran great so I figured I was home free. Unfortunately, the BSODS are back and are frequent (almost every couple of hours).

I have tested the ram and had a computer service company test it as well...seems its ok. They deleted my Norton Internet Security as they said it was causing the BSODS...not the case. I've deleted the Catylist Control Center off the system as I heard it caused issues with Win 7 64bit. I have tried to load all the latest drivers, but I'm having no luck. The errors I get are usually one of two "Page Fault in Nonpaged Area" or "Memory Management". The likely cause points to a problem with the ntoskrnl.exe (per WhoCrashed). I unfortunately am not having any luck and thought I'd post here. The dump files are attached.

Any help is appreciated.



System Info
i7 930
Win 7 Home Premium 64 bit
Gigabyte X56A-UD3r
6 Gb Corsair CMX6GX3M3A-1600C9
Video Card: Asus EAX5850
Hard Drives:
WD 300 Gb Velociraptor WD3000GLFSRTL
WD Caviar Black 1 Tb WD10000LSRTL
Power: Thermaltake Model TR2 RX-850 AP

 

[zigzag3143]

Hi all,

New to the forum. I built this Windows 7 64 bit system back in march or april. I have had random BSOD from the start. They were infrequent and for about a 2 or 3 month period, they went away and the system ran great so I figured I was home free. Unfortunately, the BSODS are back and are frequent (almost every couple of hours).

I have tested the ram and had a computer service company test it as well...seems its ok. They deleted my Norton Internet Security as they said it was causing the BSODS...not the case. I've deleted the Catylist Control Center off the system as I heard it caused issues with Win 7 64bit. I have tried to load all the latest drivers, but I'm having no luck. The errors I get are usually one of two "Page Fault in Nonpaged Area" or "Memory Management". The likely cause points to a problem with the ntoskrnl.exe (per WhoCrashed). I unfortunately am not having any luck and thought I'd post here. The dump files are attached.

Any help is appreciated.



System Info
i7 930
Win 7 Home Premium 64 bit
Gigabyte X56A-UD3r
6 Gb Corsair CMX6GX3M3A-1600C9
Video Card: Asus EAX5850
Hard Drives:
WD 300 Gb Velociraptor WD3000GLFSRTL
WD Caviar Black 1 Tb WD10000LSRTL
Power: Thermaltake Model TR2 RX-850 AP

Norton needs to be un-installed with their uninstall tool.
The video drivers also need an uninstaller.

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

The DMP's dont specifiy which driver is causing the problem so run driver verifier to narrow it down.

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:

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 a memtest memory test

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.

 

[zigzag3143]

Hi all,

New to the forum. I built this Windows 7 64 bit system back in march or april. I have had random BSOD from the start. They were infrequent and for about a 2 or 3 month period, they went away and the system ran great so I figured I was home free. Unfortunately, the BSODS are back and are frequent (almost every couple of hours).

I have tested the ram and had a computer service company test it as well...seems its ok. They deleted my Norton Internet Security as they said it was causing the BSODS...not the case. I've deleted the Catylist Control Center off the system as I heard it caused issues with Win 7 64bit. I have tried to load all the latest drivers, but I'm having no luck. The errors I get are usually one of two "Page Fault in Nonpaged Area" or "Memory Management". The likely cause points to a problem with the ntoskrnl.exe (per WhoCrashed). I unfortunately am not having any luck and thought I'd post here. The dump files are attached.

Any help is appreciated.



System Info
i7 930
Win 7 Home Premium 64 bit
Gigabyte X56A-UD3r
6 Gb Corsair CMX6GX3M3A-1600C9
Video Card: Asus EAX5850
Hard Drives:
WD 300 Gb Velociraptor WD3000GLFSRTL
WD Caviar Black 1 Tb WD10000LSRTL
Power: Thermaltake Model TR2 RX-850 AP

Norton needs to be un-installed with their uninstall tool.
The video drivers also need an uninstaller.

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

The DMP's dont specifiy which driver is causing the problem so run driver verifier to narrow it down.

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:

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 a memtest memory test

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.