Computer Hope
Microsoft => Microsoft Windows => Windows Vista and 7 => Topic started by: SuzanG on November 01, 2016, 06:26:32 AM
-
Windows 7-desktop computer
I have had problems for months now, with my computer just going to the blue screen saying it is doing a dump. There have been different error codes, and I have tried everything that I could think of including hardware driver updates, system restore, and full memory/hard drive check that took about 4 hours, and did not tell me anything was wrong.
The most recent error code is "Stop Ox0000007e"
I hope one of you tech experts can help me to come up with a solution. It is quite an inconvenience, and cannot be good for my computer, and programs to shut down this way.
Thank you.
-
Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply
-
I deleted your post - it was the wrong info. Please try again, but you want to post the error codes. Also, since there are so many please only post the 10 most recent errors.
-
They went back to 2009 ;D 8)
-
Was it the wrong information, or you only needed the most recent 10 on that list?
Sorry, there was this one item in the tops window of the results-this is what was there;
Dump File : 110116-52640-01.dmp
Crash Time : 11/1/2016 1:59:05 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff6fc`500b9353
Parameter 3 : fffff880`0319aa68
Parameter 4 : fffff880`0319a2c0
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\110116-52640-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 287,184
Dump File Time : 11/1/2016 6:04:31 AM
==================================================
-
That's what I was looking for, thanks. Just the one?
1) Have you recently installed any new hardware or updated any drivers?
2) Please look in Device Manager - are there any yellow or red symbols?
3) Please check for a bios update.
-
No I have not installed any hardware lately, or updated the drivers. Is there a simple way to tell if there are new versions available? When I go in to Device Manager and go to drivers-to update there, it says that my drivers are up to date.
There are no yellow or red symbols. The Coprocessor had one, so I disabled it, and the Teredo Tunneling Adapter had one, so I disabled that also.
I do not know if Bios has been updated-I assume I found the version/date and it is American Megatrends Inc. V1.2, 4/23/2008
Info about my computer;
System Manufacturer=XFX
Model=MG-63MI-7059
I do not know where I would find the correct Bios update to install.
-
You may need to install the Nvidia Chipset Driver. I suggest you go to the nvidia website and let it scan your system for needed drivers (http://www.nvidia.com/Download/ScannForce.aspx?lang=en-us)
-
I did this. We will see if it worked. :)
The info that I gave you that was a 2008 driver was for the networking controller, but this update was for the display adapters.
-
What I think you need is the nvidia chipset driver, since you say there was an error listed for the coprocessor in device manager
-
She disabled it in Device Manager.
-
Understood. Still, it was showing an error and rather than disable it I'd prefer to have the correct driver for it.
Also, disabling it doesn't stop it from re-enabling on reboot.
-
We need to know more about the PC and the MBoard to locate the proper chipset drivers...
-
We already have that info in post #6 above
http://xfxstorage.com/Support/Manuals/Nforce6/630i_7159.pdf (http://xfxstorage.com/Support/Manuals/Nforce6/630i_7159.pdf)
http://sciologness.com/laptops-desktops/xfx/137121/mg-63mi-7059.html
-
My bad...i missed that...Thanx.
-
No problem :)
-
...
-
So should I update the coprocessor driver? I see a Standard open, and a Standard enhanced on the website link that was in prior post. Which one, if I do this?
Should I update the BIOS too? If so, how would I do that?
-
At this point let's wait and see if you get another blue screen error. If you do, please post it as you did the one above.
-
I would leave the BIOS alone...
-
Ok, sounds good. Thank you so much for the help. Very appreciated.
-
you're welcome :)
-
Well, I hate to come back for help so soon but...got it again a few minutes ago. Here is the info you'd asked for last time.
I hope you can help. At the bottom of this first section I've included the two lines from lower part of BlueScreenView that were highlighted in pink, after I ran it. Might be helpful.
Dump File : 110316-62593-01.dmp
Crash Time : 11/3/2016 1:10:00 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+a888a
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+6f440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\110316-62593-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,288
Dump File Time : 11/3/2016 1:12:18 PM
ntoskrnl.exe ntoskrnl.exe+ee2e fffff800`03811000 fffff800`03df7000 0x005e6000 0x57ee7d5a 9/30/2016 8:57:30 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.23564 (win7sp1_ldr.160930-0600) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe
win32k.sys win32k.sys+a888a fffff960`000c0000 fffff960`003e6000 0x00326000 0x57d711f2 9/12/2016 2:37:06 PM Microsoft® Windows® Operating System Multi-User Win32 Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\win32k.sys
-
download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.
-
This is a bit out of my comfort level. Any other ideas?
-
There's really nothing complicated about it. You're simply downloading a diagnostic utility, burning it to cd, booting to it and running it. It's the best method of testing your ram.
At this point the problem is almost certainly with your ram or some other hardware.
-
I was going to try the suggestions of booting from a cd with the diagnostic test software, but the link for the iso burning utility took me to a website that does not exist.
Also, I have tried before to access my BIOS for setting up the boot order, and was not successful trying every combination of keys that there is, it seems. Once I get an answer on how to download this software to test my memory, I will try getting to BIOS screen. Anyone know of a trick? I will try Del, F1, or F2 per a chart that I found that listed my BIOS manufacture, and said one of these should work.
-
This is from dictation.
Hello, you have spent about five days on this issue and so far you haven't been able to resolve it. If your computer is usable at all, you can load a memory test from Windows. It will do the test without the need doing BIOS settings
(I agree, MemTest86 is the ideal way to test memory. Here is an alternative.)
You may need to solicit the help of a neighbor or friend or relative that has had some experience with desktop computers. But it should not be necessary to call in a repair man to do this, it is something that most people should be able to do.
I fully understand your reluctance to try things you're not familiar with. As for myself, even though I have several years of experience working with electronic devices, but now there are some things I am just not willing to try. (One of these is trying to figure out how to use the remote control for my cable television.)
Here is some information about how to test PC memory inside Windows 7. It works good.
https://www.youtube.com/watch?v=jckpCq-XnLQ
Also read this:
https://www.cnet.com/how-to/test-your-ram-with-windows-memory-diagnostic-tool/
I do hope this helps you. :)
-
I was able to do the MemTest86 as you suggested. It found no errors.
I'd already done the simpler one that you'd suggested, with no problems found.
I have had two blue screen incidences over the weekend.
Now what?
-
Please post the errors you received this weekend.
-
Flakey PSU
-
When I tried to do a bluescreenview report, it is blank. Is there another way to find this?
thank you.
-
Take a look in c:\windows\minidump and see if there are any .dmp files dated this past weekend. If so, please upload them. Also, you can look in Event Viewer, but candidly it will probably be tough to identify what we need from there. Next time(s) the blue screen pops up just make note of the specific error message / code. If the codes are different each time then you have a piece of hardware that has failed or is failing. It could be the PSU as patio suggested or it could be the motherboard, cpu, or something else.
-
Not sure how, or why, but the minidump folder you mention below is empty, and no .dmp files shown when I do computer search.
I did write down the last error which said; System_Service_Exception
Each blue screen error has been different. So...as far as the PSU-it does run, but if there is a break in power, could it cause this? Is their a way to test the PSU for that?
-
The best test which is Free is to borrow a known good one and swap it in there...
You will know overnight whether it's the issue or not...
-
Since each error has been different it is almost certainly a piece of hardware that has failed. No harm in starting with the psu as suggested. My guess would be that or the motherboard. Unfortunately the only way to know for sure is to exchange the hardware for a version you know is good.
-
Since each error has been different it is almost certainly a piece of hardware that has failed. No harm in starting with the psu as suggested. My guess would be that or the motherboard. Unfortunately the only way to know for sure is to exchange the hardware for a version you know is good.
Right on !
Hardware is tested by substitution. The Power supply is a place to start.
-
Took this baby into a computer place, and planned to have him put in different CPU to try that. He looked inside the tower, and showed me that the capacitors were bad-rounded on the tops. He suggested we have that fixed, and give it a try then. I will go pick it up today, and will let you all know if that resolved the issue.
-
Thanks for the update. Good luck :)