I've tried using primetest95 to see if it's that, but it blue screens, when my cpu hits 85c~ and I'm thinking it's over heating. I'm fairly sure it might be a CPU or RAM problem, but am not sure what, or how to be sure.

Multiple BSOD's
#1
Posted 10 August 2012 - 12:54 PM

I've tried using primetest95 to see if it's that, but it blue screens, when my cpu hits 85c~ and I'm thinking it's over heating. I'm fairly sure it might be a CPU or RAM problem, but am not sure what, or how to be sure.
#2
Posted 10 August 2012 - 12:56 PM

GeeksToGo,



I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.
- Please understand we are all volunteers and we are not here all the time.
- Sometimes it may be a extended amount of time to get back to you. If it has been
more then 3 days please shoot me a PM and I will try to get back to you quickly
then. - Please do the following and supply the requested information as needed. If you
don't understand my instructions please ask and I will try to explain them
clearer for you. - Do not attempt any steps unless instructed or ask before to
make sure they will not cause any further issues. - If you are receiving assistance in any other forum site please let us know as there may be conflicting advice given.
Before we can help you need to provide the following so I can start you in the right direction.
Laptop or Desktop?
- If a name brand system then what brand, make and model is the system?
- If custom built then what brand, make and model is the motherboard
- Total memory installed
- Total hard drive capacity and free space
- What was the original issue
- What steps have you taken so far to resolve the issue
Just a couple of logs I would like to get please.
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....
Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
http://www.resplendence.com/downloads
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
Thanks to Broni for the instructions and program
#3
Posted 10 August 2012 - 01:15 PM

750 gb Hard drive, (698 actual) and 293 free,
8 Gigs of RAM installed,
Original Issue was blue screens, other then that, I don't know, that's what I'm trying to find out.
And the only steps I have taken were simply trying to diagnose. Windows Memory Diagnostic shows no errors, a run or two of Prime95, until I saw the temp was too high and shut it off, or blue screened.
I have Whocrashed, and have the free software,
11 Crash dumps:
On Fri 8/10/2012 6:45:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081012-21886-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF8, 0x0, 0xFFFFF800030C4CDC, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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.
On Fri 8/10/2012 6:45:06 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avgmfx64.sys (avgmfx64+0x12B8)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF8, 0x0, 0xFFFFF800030C4CDC, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\avgmfx64.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG Resident Shield Minifilter Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avgmfx64.sys (AVG Resident Shield Minifilter Driver, AVG Technologies CZ, s.r.o.).
Google query: avgmfx64.sys AVG Technologies CZ, s.r.o. PAGE_FAULT_IN_NONPAGED_AREA
On Fri 8/10/2012 6:30:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081012-38360-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70010)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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 Fri 8/10/2012 2:12:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081012-30981-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0xFFFFF8804D72CCE0, 0x2, 0x1, 0xFFFFF8000308A9B9)
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 Fri 8/10/2012 1:58:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081012-23727-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A4F4C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008286038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
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 a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 8/10/2012 10:39:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081012-37003-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80081E4028, 0xB64A4000, 0x175)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 8/9/2012 3:08:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080912-33275-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007C45028, 0xB4002000, 0x69000135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Tue 8/7/2012 7:55:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080712-23431-01.dmp
This was probably caused by the following module: avgtdia.sys (avgtdia+0x32463)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\avgtdia.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG Network connection watcher
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avgtdia.sys (AVG Network connection watcher, AVG Technologies CZ, s.r.o.).
Google query: avgtdia.sys AVG Technologies CZ, s.r.o. KMODE_EXCEPTION_NOT_HANDLED
On Mon 8/6/2012 8:50:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080612-41574-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007BF5028, 0xB4742000, 0x75000145)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sun 8/5/2012 12:38:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080512-33477-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0xFFFFF8804D72BEA0, 0x2, 0x1, 0xFFFFF800030DB9B9)
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 Wed 8/1/2012 4:20:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-38469-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0xFFFFF8005028DB8C, 0xC, 0x0, 0xFFFFF8000309C1E9)
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.
I have reinstalled windows to try and solve the ntoskrnl.exe thinking it may be missing or corrupt, didn't help. I have a new keyboard in the mail, because this one is cheap, but seems to work out fine. Other then that I haven't done anything else.
Edited by Sheperd, 10 August 2012 - 01:16 PM.
#4
Posted 10 August 2012 - 01:18 PM

Also can you do the following and let me know the results.
Tutorial for running chkdsk in Vista\Win 7 located HERE.
Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.
NOTE. If your hard drive is made by Toshiba, try the Hitachi DFT CD Image version of the software
Thanks to Broni for the instructions
Download Speedfan (The download link is to the right), and install it. Once it's installed, run the program and post here the information it shows.
The information I want you to post is the stuff that is circled in the example picture I have attached.
To make sure we are getting all the correct information it would help us if you were to attach a screenshot like the one below of your Speedfan results.
To do a screenshot please have click on your Print Screen on your keyboard.
- It is normally the key above your number pad between the F12 key and the Scroll Lock key
- Now go to Start and then to All Programs
- Scroll to Accessories and then click on Paint
- In the Empty White Area click and hold the CTRL key and then click the V
- Go to the File option at the top and click on Save as
- Save as file type JPEG and save it to your Desktop
- Attach it to your next reply

#5
Posted 10 August 2012 - 01:18 PM

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A
B. If you have only one RAM stick installed...
...run memtest...
1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.
To change Boot Sequence in your BIOS
Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.
The running program will look something like this depending on the size and number of ram modules installed:

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.
This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

The following image is the test results area:

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
#6
Posted 10 August 2012 - 01:43 PM

Not sure how to get the volt readings on the bottom, however.
Edited by Sheperd, 10 August 2012 - 01:45 PM.
#7
Posted 10 August 2012 - 01:49 PM

If you don't know how here are the instructions.
To change Boot Sequence in your BIOS
Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.
Hopefully you have already put the Memtest cd in the drive before all this. If everything is setup correctly you will boot directly to memtest and it will start.
OK then I would uninstall it and then get either Avast or MSE it is your choice as both are good in my opinion. I actually use both on the 5 systems I have here.And I am not loyal to AVG at all, I really just use it because it has a semi decent track record.
Please download Avast from my signature below. Please make sure you do the registration as it is good for a year or more. When it is due simply just reregister it.
Avast in my opinion is better because:
It's FREE to the Home User
It Updates it's Definitions daily
You can scan Individual Files, Folders and Drives
No buying new versions every year
http://www.avast.com...avast-home.html
Microsoft Security Essentials provides real-time protection for your home or small business PC that guards against viruses, spyware, and other malicious software.
#8
Posted 10 August 2012 - 01:52 PM

Edit: I'm having my father grab one, as he was heading to a Wal-Mart anyway, I just hope he grabs the right one.
Edited by Sheperd, 10 August 2012 - 01:59 PM.
#9
Posted 10 August 2012 - 02:06 PM


#10
Posted 10 August 2012 - 03:42 PM

On Fri 8/10/2012 9:34:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081012-27534-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000308D19E)
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.
#11
Posted 10 August 2012 - 03:44 PM

#12
Posted 10 August 2012 - 05:09 PM

#13
Posted 10 August 2012 - 05:44 PM


Have you uninstalled AVG and installed one of the others I suggested?
#14
Posted 10 August 2012 - 05:57 PM

#15
Posted 10 August 2012 - 06:16 PM

Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
As Featured On:






