Windows 7: My system keeps crashing!

kimboviper · 14 Jun 2010

i have tried everything, new mobo, fresh installs, memtest. Everything and nothing stops these BSOD from happening. It is really frustating.

I am running a:

Phenom X4 955
HD5770
Intel 40gb SSD
MSI 890gxm-g65 motherboard
Corsair XMS DDR3 1600mhz RAM

Please help!

usasma · 14 Jun 2010

There's only 2 of them - do you have any more?
When do they occur?

Try running Driver Verifier according to these directions:

Quote:

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/Windows 7 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"
- 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:

Code:

Delete these registry keys (works in XP, Vista, Windows 7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Jun 14 17:03:45.056 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:14.882
BugCheck E3, {fffffa80054c2c70, fffffa80057d1060, 0, 2}
Probably caused by : win32k.sys ( win32k!CreateXlateObject+78f )
BUGCHECK_STR:  0xE3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Jun 14 17:03:08.563 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:29.389
BugCheck 18, {0, fffffa8005bedf90, 2, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46661 )
BUGCHECK_STR:  0x18
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

kimboviper · 15 Jun 2010

this is a very random BSOD

over the past month i probably have 20+ BSOD's but i keep reinstalling windows 7. Maybe i should try XP.

ttran · 15 Jun 2010

keep re-installing window 7 without updating drivers will give u same results, I mean BSODs. Everytime your computers get BSOD, it will create minidump files. Please keep uploading them to forum. I used to think the same way as u do. I love window xp and when my computer with window 7 crashed, i thought of installing window xp. But I visited this forum, and I learnt that updating driver could help me to use window 7, which is great operating system.
Please don't give up, if u have more BSOD, please upload them

kimboviper · 16 Jun 2010

here are some more recent BSOD's

also they usually happen when i boot the system. usually i get a win explorer crash and then i get the BSOD. I am running Steam but i also run it on my thinkpad edge laptop and it never crashes!!

I am overclocking my desktop to 3.8ghz but it still occurs if i set back to the stock clock speed.

thanks in advance!

CarlTR6 · 16 Jun 2010

You have five mini dumps with five different stop error codes. This usually indicates hardware problems. It will take me a few minutes to look at these.

Quote:

STOP 0x00000018: REFERENCE_BY_POINTER

Usual causes: Device driver, kernel, hardware

BSOD Index

STOP 0x000000E3: RESOURCE_NOT_OWNED

Usual causes: Device driver

BSOD Index

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

BSOD Index

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION

Usual causes: System service, Device driver, graphics driver, ?memory

BSOD Index

STOP 0x00000024: NTFS_FILE_SYSTEM

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

BSOD Index

CarlTR6 · 16 Jun 2010

Here are the results of the mini dumps.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 18, {0, fffffa8005bedf90, 2, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46661 )

Followup: MachineOwner

******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck E3, {fffffa80054c2c70, fffffa80057d1060, 0, 2}

Probably caused by : win32k.sys ( win32k!CreateXlateObject+78f )

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, 100, fffff880031e8148, fffff880031e79a0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+448f7 )

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002fe2121, fffff88004420160, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+51 )

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800317e898, fffff8800317e0f0, fffff88001342dc1}

Probably caused by : Ntfs.sys ( Ntfs!TxfDeleteTxfFo+11 )

Followup: MachineOwner

Did you follow John's recommendation above to run Driver Verifier? If not, please do so and we will go from there.

ttran · 16 Jun 2010

Hi there
In one of the five parameter above indicated memory exception (ffffffffc0000005), so I would suggest download third party called memtesst86, burn it to cd and let it run for at least 7 passes

Bugcheck for that one:

Code:

BugCheck 1000007E, {ffffffffc0000005, 100, fffff880031e8148, fffff880031e79a0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+448f7 )
Followup: MachineOwner
---------

Regard
T

kimboviper · 16 Jun 2010

i have already done memtest and driver verifier.

kimboviper · 16 Jun 2010

i already ran bluescreenview and it is always the same files that crash but i have researched those files and they are very vague to what is truly causing the crashes. this is so frustrating that i want to throw my desktop out the window!

Windows 7: My system keeps crashing!

My system keeps crashing! problems?