Sign in with
Sign up | Sign in
Your question
Closed

Blue screen. Minidump. Help!

Last response: in Windows 7
Share
September 1, 2011 6:40:38 AM

Hello. I really hope someone can help me..

I am experiencing random system crashes. I can't seem to figure out what triggers the crash. It can happen as frequent as twice a in a day or as seldom as twice in a month.

I figure a good way to determine the problem would be to analyze the minidump files. Am I right? If so, can someone assist me with that?

I have noticed the crashes tend to happen while playing games such as Call of Duty MW2 & Black Ops. But, like I said, it is intermittent. Sometimes I can play for a solid 4 hours straight with no problems, and other times it happens much sooner.

Here are my system specs:

OS: Windows 7 Ultimate x64
Mobo: MSI 870-G45 (MS-7599)
CPU: AMD Athlon II x4 620 @ 3.12 GHz
RAM: 8 GB DDR3
GPU: MSI R5770 Hawk

Text from 2 recent crashes:
Quote:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF80002CDB8CD
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\083011-10732-01.dmp
C:\Users\Eric\AppData\Local\Temp\WER-13930-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Quote:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF80002CDF8CD
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\090111-9516-01.dmp
C:\Users\Eric\AppData\Local\Temp\WER-12979-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

More about : blue screen minidump

September 1, 2011 7:02:57 AM

Do you have a third party firewall installed? Such as Zone Alarm? Also, the first parameter suggests a hardware issue. Open your case and re-seat ALL cards, RAM, and cables and run memtest.

Also, download, install, and run WhoCrashed and let us know what driver it narrows it down to. Once installed, launch the program and click analyze. Then copy and past the results.
http://www.resplendence.com/download/whocrashedSetup.ex...
Score
0
September 1, 2011 7:14:21 AM

Thanks for the quick response!

No I do not have a third party firewall.

I will reseat and run a memtest (it's just run the "memtest" command in cmd prompt, right?)

In the mean time, I pulled up Event Viewer and exported the events labeled "Critical", "Error" and "Warning" (I didn't bother with the "Information" events)

Put them in a zip file, here's the link: http://www.filedropper.com/eventfiles
Score
0
Related resources
September 1, 2011 7:42:41 AM

I ran the Windows 7 memory diagnostic tool. It said there were no memory issues.

Here's the WhoCrashed report:
Quote:
System Information (local)
--------------------------------------------------------------------------------

computer name: ERIC-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II X4 620 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8589074432 total
VM: 2147352576, free: 1949331456



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 9/1/2011 6:19:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090111-9516-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002CDF8CD)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 9/1/2011 6:19:29 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002CDF8CD)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 8/30/2011 7:24:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083011-10732-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002CDB8CD)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Score
0
a b $ Windows 7
September 1, 2011 8:00:34 AM

How many times did you run memtest? once, twice? i would really run it 20 to 30 times to make certain, could also be an issue with your HDD or PSU seeing its happening at random times.
Score
0
September 1, 2011 9:40:58 AM

fowang said:
How many times did you run memtest? once, twice? i would really run it 20 to 30 times to make certain, could also be an issue with your HDD or PSU seeing its happening at random times.


I ran it once, after post outside of the Windows environment.

It just crashed again.

Here's what WhoCrashed has to say about it:
Quote:
On Thu 9/1/2011 9:06:10 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFFA80540505FB, 0x0, 0xFFFFF80002CD08CD, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

I Googled the "page fault in nonpaged area" error and it looks like there could be something wrong with my system drive (which is an 80 GB SSD)

I ran CHKDSK. Don't think there were any problems there...
Quote:
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
154368 file records processed. File verification completed.
367 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
212016 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
154368 file SDs/SIDs processed. Cleaning up 444 unused index entries from index $SII of file 0x9.
Cleaning up 444 unused index entries from index $SDH of file 0x9.
Cleaning up 444 unused security descriptors.
Security descriptor verification completed.
28825 data files processed. CHKDSK is verifying Usn Journal...
37554104 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
154352 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
7365566 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

78046207 KB total disk space.
48249904 KB in 122526 files.
73256 KB in 28826 indexes.
0 KB in bad sectors.
260779 KB in use by the system.
65536 KB occupied by the log file.
29462268 KB available on disk.

4096 bytes in each allocation unit.
19511551 total allocation units on disk.
7365567 allocation units available on disk.

Internal Info:
00 5b 02 00 43 4f 02 00 2f 48 04 00 00 00 00 00 .[..CO../H......
73 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 s...,...........
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.


Thoughts?
Score
0
September 1, 2011 12:51:18 PM

First is your cpu and videocard fan heatsink free of dust and spinning?
Second do a visual inspection of capacitors on your motherboard and video card.
A good cap is flat and clean a bad cap is raised and may have a hole or resin leaking out.




Third is your chipset drivers and video drivers up to date?.
Score
0
September 18, 2011 9:12:23 PM

techguy911 said:
First is your cpu and videocard fan heatsink free of dust and spinning?
Second do a visual inspection of capacitors on your motherboard and video card.
A good cap is flat and clean a bad cap is raised and may have a hole or resin leaking out.

http://www.thenakedpc.com/dan/Bulging_Capacitors/close-up.jpg
http://1.bp.blogspot.com/_-Oo0AA-EgTM/TKa8Au5iokI/AAAAAAAABTM/z1OK49XkalA/s1600/IMG_0173-722036.JPG

Third is your chipset drivers and video drivers up to date?.

Yes, heatsinks are clean and keeping my components nice and cool
No leaking capacitors that I can see.
Video drivers are up to date.
I do not know if my chipset drivers are up to date or if my BIOS is up to date. Can you help me with either of those?
Score
0
September 18, 2011 9:13:59 PM

Thanks to everyone who posted previously. My issue is still unresolved. See the 2 most recent WhoCrashed reports:
Quote:
On Sun 9/18/2011 2:03:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091711-9609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFF88003310BB8, 0x2, 0x0, 0xFFFFF80002CE4299)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 9/18/2011 2:03:33 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF88003310BB8, 0x2, 0x0, 0xFFFFF80002CE4299)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


Seems the offending executables are "ntoskrnl.exe" and "ntkrnlmp.exe". Both show the error being "IRQL_NOT_LESS_OR_EQUAL"
My research indicates this error has to do with memory access? I also found an article that suggested I run SFC /SCANNOW to scan system files and repair any missing or corrupted files. The scan told me that it found some errors, but it could not fix some of them. Here's the log output: http://www.filedropper.com/cbs

Can someone help me make heads or tails of this mess?
Score
0

Best solution

September 23, 2011 1:22:16 AM

try to re install your windows 7 ultimate but chose 32bit not, 64 bit hope it works,,,,,
Share
September 30, 2011 5:23:03 AM

Best answer selected by meeksdoteric.
Score
0
a c 416 $ Windows 7
September 30, 2011 12:54:20 PM

This topic has been closed by Area51reopened
Score
0
!