bsod multiple times daily

[Jonathan_King]

Did you mess with the page file at all? I see a PF date of 2010/08/01 (the first of this month). Original OS install date is 6/12/2010. The latter number agrees with the date you bought the computer.

Page File is allocated 8191 MB. You have 8192 MB RAM. The recommended page file size for your amount of RAM (3x) is 24GB.

Is the page file set to System Managed? If not, you should set it that way.

We suspect your outdated nForce networking drivers are the cause, but no updates can be found for your chipset.

I suggest giving these drivers a try: http://us.download.nvidia.com/Windows/nForce/15.53/15.53_nforce_win7_64bit_international_whql.exe

No guarantees, those are for the nForce 5 series, and you have the nForce 4 chipset.

You may contact HP for support here. Is the computer still under warranty? You may see if they will replace your motherboard with a newer one.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 18 05:14:40.364 2010 (UTC - 4:00)
System Uptime: 0 days 5:59:55.722
BugCheck 3B, {c0000005, fffff80002f9574d, fffff88004d11770, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  MsMpEng.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 18 05:23:55.044 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:43.777
BugCheck 3B, {c0000005, fffff80002f44304, fffff88005679cb0, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpDeleteKeyObject+184 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Aug 17 23:14:09.938 2010 (UTC - 4:00)
System Uptime: 0 days 13:41:54.670
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : storport.sys ( storport!RaidpAdapterTimerDpcRoutine+38 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[socrgy9]

well, i remember messing with the page filing to try and solve a computer issue some weeks ago in a different thread, although i don't remember exactly when. at the end of it all, i reset the page filing to system managed and then checked the check box at the top that says "automatically manage paging file size for all drives."

as of now it says its set at 7935mb

i installed the driver you posted and ill change the paging file to 24Gb

 

[CarlTR6]

Very good. Let us know what happens.

 

[cluberti]

Page File is allocated 8191 MB. You have 8192 MB RAM. The recommended page file size for your amount of RAM (3x) is 24GB.

Well, that's a relic from the NT3.x/4.x days when 16MB of RAM was a lot. The Windows 7 default is minimum set to 1.5x RAM if 1GB of RAM or less in the system, RAM otherwise; maximum is 3x RAM or 4GB, which ever is larger. Even this is *way* too much for most uses, especially desktop machines.

The more RAM you have in Windows 7, the smaller the paging file needed - you want to base your paging file based on workload and usage of committed virtual memory, rather than use the old NT4 algorithms. I've posted here the ways to determine this, but basically, these old paging file algorithm recommendation are nonsense, especially on x64 systems with 6GB+ RAM. Run your box as you would at it's hardest, and check your peak system commit in process explorer, and see how high it is. If it's less than total RAM, you could probably run without a paging file entirely, although having at least a smallish one (512MB, 1GB) can be a nice safety net for crash dumps or to back modified private memory as necessary (files on disk, images, mapped files, etc).

If you have 8GB of RAM, you really do NOT want to create a 24GB paging file, but follow some of Mark Russinovich's guidelines - test the system's load, and pad if you need it. Don't just pick an algorithm from forever ago and blindly use it.

 

[socrgy9]

ok so either way on the paging file i still have random shutdowns while gaming.

i've got paging file set as system managed size without the checkbox checked at the top to auto manage size for all drives.

its still currently allocated at 7935mb

i'm still running my integrated graphics nvidia geforce 6150 SE nforce 430.

attaching dump files, let me know if theres anything else to try.

as of now just waiting on new mobo, gfx cards and case to arrive. <-- will those new parts solve the problems possibly?

ive also been considering just re-installing windows 7 from the ground up and then restoring my system image from backup...could that do any good?

 

[cluberti]

Well, these are all over the place. The first dump is a nvidia timer crash (DirectX timed out waiting for the driver to respond, causing an expected crash), the second is a pool corruption crash (the kernel was told to ExAllocatePoolWithTag, but the memory address in pool that was attempted to be allocated was invalid or corrupt), and the third is a register fail caused either by a filter driver or a pool allocation failure. Given we have one known pool alloc failure and a second suspected one, along with a third failure that appears unrelated, I'd say you perhaps have two separate issues with this install. One, the nvidia driver (or the card underneath) is misbehaving, and two, you have a filter driver corrupting pool. In that second case, if it was memory corruption and not the same type of potential pool alloc failure I'd say potentially bad RAM. However, in this case it's more likely a filter driver issue given the apparent consistency of the failure. With that said, you *should* be checking your system RAM for faults just in case. It might also be useful to enable driver verifier if your RAM checks out ok to see if the pool alloc faults can be captured.

 

[socrgy9]

ill run driver verifier again. through working with this problem i've checked ram roughly 10 times total with no problems.

thanks!! ill let ya know what driver verifier says.

 

[socrgy9]

ok, i was finally able to run driver verifier. i let it bsod 3 times before ending it. i'm including those 3 dumps, plus the handful more in the past day or so before i could get to driver verifier.

 

[Jonathan_King]

I wonder if your Logitech keyboard is causing the problem. Could you try a different one?

I see your CD drive is reported as a "Problem Device". Try disconnecting it, and see what happens.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 22 06:42:27.260 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:14.650
BugCheck 1000007E, {ffffffffc0000005, fffff80002f464bd, fffff880031aeda8, fffff880031ae610}
*** WARNING: Unable to verify timestamp for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
Probably caused by : volmgr.sys ( volmgr!VmpApplyHotplugProtection+3fc )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 22 06:41:33.059 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:48.432
BugCheck C9, {23b, fffff88004810818, fffff9800bd8adc0, 0}
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
BUGCHECK_STR:  0xc9_23b
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[neo101]

ok so either way on the paging file i still have random shutdowns while gaming.

i've got paging file set as system managed size without the checkbox checked at the top to auto manage size for all drives.

its still currently allocated at 7935mb

i'm still running my integrated graphics nvidia geforce 6150 SE nforce 430.

attaching dump files, let me know if theres anything else to try.

as of now just waiting on new mobo, gfx cards and case to arrive. <-- will those new parts solve the problems possibly?

ive also been considering just re-installing windows 7 from the ground up and then restoring my system image from backup...could that do any good?

You reminded me of this: "Random freezes"

“A computer that is running Windows Server 2008 R2 or Windows 7 stops responding randomly,” Microsoft stated.

“Applications or services that are running on the computer stop working correctly. Additionally, you cannot log on to the computer by using the remote desktop connection utility,” the company explained.

Microsoft noted that it has identified the problem, but offered very little information to customers.

“This issue occurs because of a deadlock condition between the Lsass.exe process, the Redirected Drive Buffering Subsystem (Rdbss.sys) driver, and the Winsock kernel,” the company said.

M/soft 'HotFix' >
http://www.sevenforums.com/news/104118-windows-7-random-freezes-fix-available.html

 

[cluberti]

It's a network-related hang, given the components that are updated because of the hang as per the KB (name resolution proxy and netbios helper for TCP/IP). Not a bad idea to install though, just in case.

 

[socrgy9]

well, once again i'd like to thank everyone for their help. my new mobo, gfx cards and case arrived in the mail today and i will be putting that all together right away. however this thread needs to be closed please do

thanks again!
colin

 

[CarlTR6]

Congratulations on your new hardware and thank for reporting back. You will soon have a brand new computer. Let us know when it is up and running.

To mark a thread as solved, you click on the triangle in the upper right and ask the moderators to mark the treas as solved. I will do so.

And again, I thank you for your service.

 

[socrgy9]

well, i'm up and running again! my first PC build from scratch was a success and took forever LoL! i finally got most of my software loaded back on and i don't have any bsod problems!

thanks again for everyone's support and knowledge. ill never buy a pre-packaged pc again hahaha.

ill update all my system specs shortly.

colin

 

[CarlTR6]

Excellent, Colin; and very good news. Thanks for reporting back. Happy computing and don't be a stranger to the forum.