Windows 7: Bsod becoming frustrating.

Fresh install of Windows 7 Home Premium 64-bit worked fine for a few weeks then started crashing.

1. Crashed while uploading images to web when Firefox was running.
2. Crashed when running IE8. (a Windows Media Player error kept popping up although WMP wasn't open?)
3. Crashed when writing data to a USB stick in a front port.
4. Crashed when writing data to a USB stick in a back port.
5. Crashed after changing HDD's (swapped out my current HDD with Home Premium to my old test HDD with Windows 7 Ultimate RC1 which I had been running since it's release with no problems but RC1 Blue Screened shortly after booting several times.)
6. Crashed when installing the latest 9.11 ATI drivers.
7. Crashed when using Windows Restore.
8. Crashed when downloading from Microsoft.
9. Crashed when typing this message.

I've gotten a least 5 different error messages (or more) out of 30-40 crashes within a couple/three weeks.

1. BAD POOL HEADER
2. PAGE FAULT IN A NONPAGED AREA
3. MEMORY MANAGEMENT
4. SYSTEM SERVICE EXCEPTION
5. IRQL NOT LESS THAN EQUAL (or something like that)

What I've tried:
Removed a recently added 4 port USB 2.0 PCI card.
Updated drivers, although I already had the latest drivers except for the ATI video, running 9.10
Flashed BIOS (successfully)
Ran MEMTEST86+ (4.00) 8x with no errors
Ran Windows Mem Check with no errors
Ran memory 8GB Ram at reduced timings 5-7-7-24
Ran memory 8GB Ram at correct settings 5-5-5-15
Copied my mirror image backup (original install) back to my HDD (wasn't smart enough to save all the minidump files before wiping.)


Still crashed and have a couple of the minidumps now and will attach.


I've removed half of my RAM and waiting to see what happens.


But my question is when Windows Blue Screens is it common to get different error messages or are they usually all the same error? (since I've gotten several different errors)

Hi.

If you're overclocking anything at all, set it/them to factory speeds.

Update these drivers:

SSPORT SSPORT.sys Thu Aug 11 19:07:32 2005
jraid jraid.sys Mon Nov 03 21:20:09 2008

The differences in the BSOD's can be due to a number of different causes. It all depends upon the types of errors that you're getting. When there's no other evidence to the contrary, a number of varying BSOD reports could be indicative of a hardware failure.

In your case the Bad Pool Caller and Memory Management errors suggest a problem with your Memory.
The PAGE FAULT IN A NONPAGED AREA and IRQL NOT LESS THAN EQUAL suggest a driver improperly accessing memory
Then the System Service Exception suggests that there may be a system service that's accessing a driver improperly - thereby causing the error.

But that's all just speculation until the memory dumps have been analyzed.

Interestingly you mention 5 different kinds of memory dumps - but only 4 have been uploaded. Could you please upload the other one (the Bad Pool Caller)?

Of the 4 memory dump files, one reports issues with your networking - so I'd suggest updating your network drivers.

BlueScreenView shows the presence of NTFS.SYS in the stack of one of the BSOD's (not confirmed by WinDbg). So, to be sure, please do the following:

1 - CHKDSK /R
Run CHKDSK /R from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

Elevated Command Prompt
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry.
Copy/paste the results into your next post.

2 - Please run a free hard drive diagnostic: HD Diagnostic

A few simple bios adjustments will usually fix these types of problems.

If you are running 8GB you can start by taking the MCH core voltage to 1.14 -1.28 volts you will need to work with this setting and find the voltage that works. (May need more as you overclock, or you may need more just to get stable with 8GB. You might also need to bump your memory voltage a bit above spec. to get stable running 8GB.


You also might try reducing the memory speed by doing this.

DRAM Performance Control
Performance Enhance...................: [STANDARD]
Extreme Memory Profile (X.M.P.).....: Disabled
(G)MCH Frequency Latch...............: [Auto] --> change to 400
System Memory Multiplier ..............: 3.20B --> change to 2.00D This will downclock your memory to 667MHz for now. You can test for stablity here, if stable you can move it up again. For 800, I would try 3.00a with 266 fsb. The MCH adjustment might be enough and you may not need to reduce the memory speed.
Memory Frequency (Mhz) ..............: 667-800
DRAM Timing Selectable ................: [Manual] Loosening the timings may also help

Attachment 40167Thanks for the replies everyone.

I am not overclocking. Everything is set to the factory speeds (CPU/Memory). All drivers were the latest Windows 7 64-bit from the web when possible as of 10/23/09

The SSPORT.sys Thu Aug 11 19:07:32 2005 (googled) looks to be for my Samsung CLP-315 printer and it appears they have a 11/27/09 driver so I will update. Seems odd they had a 2005 dated file as late as 10/22/09?

Don't know what the jraid.sys is for? RAID? (not running anything in RAID). Looking online for an update, some sites say jraid is a virus others a Windows Driver?

When I reformatted and installed my mirror image backup I lost all my minidump files (too soon old, too late smart). The dumps I posted are the only ones I have (until it BSoD's again). Unsure what the errors were on the minidumps I uploaded? I think 1 or 2 were the PAGE FAULT IN A NONPAGED AREA error.


Ran the CHKDSK/R and looks OK to me?
And I ran and had previously run Hitachi's HD Diagnostics program and another free one, both returned no HDD errors/problems.


CHKDSK log:
Checking file system on C: The type of the file system is NTFS. Volume label is HITACHI Windows 7. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 98560 file records processed. File verification completed. 62 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 134518 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 98560 file SDs/SIDs processed. Cleaning up 345 unused index entries from index $SII of file 0x9. Cleaning up 345 unused index entries from index $SDH of file 0x9. Cleaning up 345 unused security descriptors. Security descriptor verification completed. 17980 data files processed. CHKDSK is verifying Usn Journal... 34552472 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... 98544 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 55374182 free clusters processed. Free space verification is complete. CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap. Windows has made corrections to the file system. 243711999 KB total disk space. 21959708 KB in 80070 files. 49480 KB in 17981 indexes. 0 KB in bad sectors. 206083 KB in use by the system. 65536 KB occupied by the log file. 221496728 KB available on disk. 4096 bytes in each allocation unit. 60927999 total allocation units on disk. 55374182 allocation units available on disk. Internal Info: 00 81 01 00 0f 7f 01 00 3f c8 02 00 00 00 00 00 ........?....... b7 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,........... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.


Since the BSoD's happened on two independent hard drives with two different Windows installations I hope I can rule out a HHD hardware problem.


As to the Networking, I did have a Windows Media Player (WMP) Networking error pop up on my screen several times just before a crash (when surfing in IE8), but I did not have WMP running and the error made no sense?


On Downclocking, I had down clocking my memory and timings but it didn't stop the crashes, (seemed to increase them) so I reset them back to stock (picture shows my current settings). (I am not that versed in over or under clocking). The 2x2 pair (4GB) running now were installed 12/16/2008, the 2x2 pair (4GB) I removed were installed 6/12/2009.

Don't know if I really need 8GB but wanted to see if it made a difference when editing large image files (and having a large number of UNDO levels). But my photo editing software is 32-bit so I don't think it helped?

Check to ensure the old SSPORT.SYS driver is gone after you update the printer drivers.

jraid.sys is the driver for the JMicron controller on your motherboard (you've got 2 storage controllers on the motherboard - they'll have 2 different color SATA plugs on the mobo). Here's the reference for your mobo: GIGABYTE - Product - Motherboard - Overview - GA-EP45-UD3P (rev. 1.0)

The virus thing is common on the web - it's (IMO) a method for selling antivirus software, and doesn't always resemble reality. When in doubt about a particular file like this, submit the file to Jotti's malware scan for scanning. It'll tell you if it's a virus or not.

There were some issues with CHKDSK - but not seemingly major one's. I'd keep an eye on it and run CHKDSK /R on a weekly basis for the next month to see if it's a repetitive problem.
Since the BSOD's happened on 2 separate hard drives - have you run CHKDSK /R on both of the hard drives? If so, what were the results?

Please rerun the memory test for a minimum of 3 passes - overnight is better.

Because WMP is internet aware, it's likely that it was trying to connect to the web when the error occurred. This, combined with the BSOD that mentions networking, suggests that you need to:
- download the latest version of the networking drivers from the manufacturer's website
- uninstall the current networking drivers
- install the freshly downloaded network drivers.
- test to see if that has helped the BSOD situation.

From the control panel I uninstalled the Samsung print drivers, as well as Motherboard Audio, LAN and Raid. The ATI Video driver (from the ATI app) and installed the latest 64-bit MB Chipset, LAN, RAID and Audio drivers from Gigabyte . As well as the most current Samsung Printer and ATI drivers.

If the old SSPORT.sys was dated 2005 the new one is dated 8/13/2007? (located at C:Windows\System32\drivers. Search found some duplicate 2007's in C:Temp\ too but no 2005 dated or others.

Will re-run MEMTEST (only have 4GB installed at the moment) and CHKDSK for the next month and post.

I haven't run CHKDSK on my Windows Ultimate RC1 HDD. After it BSoD-ed (for good or ill) I removed/wiped the drive stuck it in a USB enclosure but will CHKDSK to see if it turns up anything. (probably too late but...)

RE-RAN CHKDSK AND LOOKS BETTER THAN MY LAST ONE.

Checking file system on C: The type of the file system is NTFS. Volume label is HITACHI Windows 7. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 113408 file records processed. File verification completed. 66 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 150146 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 113408 file SDs/SIDs processed. Cleaning up 26 unused index entries from index $SII of file 0x9. Cleaning up 26 unused index entries from index $SDH of file 0x9. Cleaning up 26 unused security descriptors. Security descriptor verification completed. 18370 data files processed. CHKDSK is verifying Usn Journal... 34328560 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... 113392 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 55531391 free clusters processed. Free space verification is complete. Windows has checked the file system and found no problems. 243711999 KB total disk space. 21315980 KB in 75224 files. 49756 KB in 18371 indexes. 0 KB in bad sectors. 220699 KB in use by the system. 65536 KB occupied by the log file. 222125564 KB available on disk. 4096 bytes in each allocation unit. 60927999 total allocation units on disk. 55531391 allocation units available on disk. Internal Info: 00 bb 01 00 a7 6d 01 00 06 ac 02 00 00 00 00 00 .....m.......... ba 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,........... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.

Until you are ready for some more bios adjustments you will continue to have problems. You only adjusted the memory settings but did nothing to the voltage settings which are even more important. The problem here is that you have an enthusiast board but have no idea how to adjust it. They aren't made to be plug and play like a Dell. The bios settings mean EVERYTHING for a board like you have.

The types of problems you are seeing all relate to a voltage shortfall in the memory controller. Until you are willing to make some adjustments in bios nothing will change.

Ignoring this type of advice is not advised. > you can start by taking the MCH core voltage to 1.14 -1.28 volts

The real problem here is that your system is not stable at all. Run Prime 95 blend test if you don't believe me, I'd be willing to bet it will fail in less than ten minutes.

I'am not just guessing when I give advice like that, I had to go to the Corsair forum and look up those numbers just for your board and memory. I suggest you do the same.

"The problem here is that you have an enthusiast board but have no idea how to adjust it."

You are right!

I'm not well versed at overclocking. When I bought this P-45 board I thought the X38/48 were more the enthusiast boards and at the time Newegg was running a special on it and the Dominator memory which made it less expensive than the lower end memory.

I just end up using the optimized default settings.

Currently pretty much everything is set to auto. The MCH Core is set at 1.10V and [auto]. Corsair lists it's DRAM voltage as 2.1V (but it's set at 1.8 and [auto] in the bios but I raised that to 2.1V)

I will try Prime95 and check out the Corsair forum then ticking up the MCH Core.

UPDATE:

Ran Prime95>Options>TortureTest>Blend for and 1 hour and 5 minutes with no issues/errors. Will run it longer when I'm able to babysit it as I don't want to leave it unattended when running.