[sunshinemofo]

hey ive been having the same problem with windows 7 64bit bluescreens...
i try to catch what caused the crash before it shuts down and the few that i caught were...
page_fault_in_non_page_area

and

system_service_exception

sometimes i will get a bluescreen when im sitting at the desktop, sometimes while playing an mmo game, and other times i cant remember.
i built the computer myself, maybe i did something wrong?

i tried the free scanning thing from the link above and the only error was that i couldnt clean up some registry files (dunno if that's a problem).
I also removed antivirus to see if that was the problem, but i still crash
any help is appreciated
thanks

[TerryNet]

I started a new thread for you here, as it gets too confusing trying to work on two people's problems in the same thread.

[Rollin' Rog]

When did these problems first begin, and did you ever try doing a "System Restore" to a prior date when they did?

If you are unsure visit the Control Panel > Action Center > Maintenance and look at the Reliability historical graph. Installs, uninstalls, and errors are logged there. You can click them to read details.

http://www.addictivetips.com/windows...ility-monitor/
====================
I can run a debugging utility on the dump files if you do this:

1 > create a new folder on the desktop and call it "dumpcheck" or whatever you like
2 > navigate to c:\windows\minidump and copy the last few minidump files to that folder. *this assumes 'c' is your boot drive, if it is not, subsitute accordingly
3 > close the folder and right click on it and select Send to Compressed (zipped) Folder.
4 > use the "manage attachments" in the "advanced" reply window to upload that zip file here as an attachment.

This might point us to a non Microsoft driver causing the error, if one exists for it.

If you do not see any minidumps, be sure you are not using any cache cleaner such as CCleaner. Also run sysdm.cpl and select Advanced > Startup and Recovery. Make sure "small memory dump" is the one chosen under "write debugging information" and the location should be %systemroot%\minidump

Since almost all bugchecks can be caused by faulty ram, I would recommend you perform memory tests.

On Vista and Win7 you can run: mdsched.exe -- after rebooting to the scanner press F1 for Advanced options and run the extended tests

[sunshinemofo]

alright... i attatched the minidump files..

i had to do two separate posts because there were too many for the maximum capacity for one post.

I also ran a memtest86 and that came out fine.
thanks again

[sunshinemofo]

and the second

[Rollin' Rog]

Ok, I've looked at a good sampling of these -- and from the number, frequency and variety of faults (nothing consistent flagged) -- and perhaps most importantly, that there are relatively few drivers in the back traces and trap frames of these errors, I'm going to call it ....

overheating


If you built this yourself (I take it it is not the notebook in your profile info?), then you need to look into proper cooling and heat sinking.


For what it's worth, this is from the second to last minidump -- and it does flag a graphics operation -- but as you can see there is just not much in the back trace except default drivers.

SYMBOL_NAME: dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+ff3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578

STACK_COMMAND: .cxr 0xfffff88003ed4c80 ; kb

FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+ff3

BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+ff3

Followup: MachineOwner
---------

2: kd> kd (display back trace)
*** WARNING: Unable to verify timestamp for mcupdate_GenuineIntel.dll
*** ERROR: Module load completed but symbols could not be loaded for mcupdate_GenuineIntel.dll
*** WARNING: Unable to verify timestamp for amdxata.sys
*** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
*** WARNING: Unable to verify timestamp for spldr.sys
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
*** WARNING: Unable to verify timestamp for L8042Kbd.sys
*** ERROR: Module load completed but symbols could not be loaded for L8042Kbd.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for nvBridge.kmd
*** ERROR: Module load completed but symbols could not be loaded for nvBridge.kmd
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for LHidFilt.Sys
*** ERROR: Module load completed but symbols could not be loaded for LHidFilt.Sys
*** WARNING: Unable to verify timestamp for LMouFilt.Sys
*** ERROR: Module load completed but symbols could not be loaded for LMouFilt.Sys
*** WARNING: Unable to verify timestamp for peauth.sys
*** ERROR: Module load completed but symbols could not be loaded for peauth.sys
*** WARNING: Unable to verify timestamp for secdrv.SYS
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
*** WARNING: Unable to verify timestamp for TSDDD.dll
*** ERROR: Module load completed but symbols could not be loaded for TSDDD.dll
Couldn't resolve error at 'display back trace)'

[TerryNet]

Are you using the drivers Windows installed? If so, I suggest you install the chipset and any other drivers provided by the motherboard manufacturer (their website for the latest). And for any other devices that are not part of the motherboard get the latest driver from the manufacturer's web site.

[sunshinemofo]

Ok.. Thanks for reminding me.. yes it is a desktop(i will change my profile comp)..

Since it was crashing at the win7 login screen
Here's what i did
I downloaded the new chipset drivers!
woopie!

<------- dunce
havent had a crash since
Thanks peeps for all ur responses!

[TerryNet]

You're welcome. Glad we could help.

[sunshinemofo]

ALRIGHT... sigh

so i THOUGHT this issue was solved when i installed the new drivers.
I installed the Gigabyte chpset driver, audio driver, and ethernet driver.
I also updated my graphics driver.
It seemed to work for a solid week.

Then i started crashing everyday again. Sometimes at windows login screen, sometimes while at desktop.

Quick reference to the overheating suggestion... I can play a high end MMO ("Aion" if u want to get a look at the grphics demand) for hours up to 17 hrs. at least w/out a crash sometimes. If it was overheating would it be more consistent crashing after a certain amount of play/use?

Are there more drivers i should try to find? Anything else that comes to your minds?

Ive attached the recent dump files.
Thanks again for the help

[Rollin' Rog]

The majority of these faults are "NTFS" errors, along with a smattering of "memory corruption" and "pool" (special memory) corruption

Troubleshoot drive related problems by running chkdsk

http://www.windows-help-central.com/...ta-chkdsk.html

The log will be available after reboot in the Event Viewer (run: eventvwr.msc) > Applications log > Wininit entry. This can be copied and pasted.

Also have a gander at the "System" log for "NTFS" errors.

Insecure drive cables could be an issue here as well.

http://msdn.microsoft.com/en-gb/library/ms793935.aspx

Also if you are using "readyboost" on a USB drive I would disable readyboost or remove the drive.

By the way, I don't see any antiviral software in the memory loads, but maybe I'm missing what you have.

[sunshinemofo]

ok did both those... what do i do with the info they gave me?

[Rollin' Rog]

Did you see any "NTFS" errors in the System Log?

Copy/paste the chkdsk log here.

Also run HDTUNE on the drive and see if it reports any bad blocks and check its "Health" report.

http://www.hdtune.com/