Computer Hope
Microsoft => Microsoft Windows => Windows Vista and 7 => Topic started by: DrSatanDracula on July 30, 2015, 08:37:50 AM
-
Dear everyone,
I have recently begun to have infrequent, but somewhat regular, BSODs on my PC. Just this morning, I had one after boot up, and previously the BSOD occurred rather randomly throughout regular work, with no noticable cause or alteration in my behaviour that would warrant it.
Here are my specs:
Windows 7 home premium
Service Pack 1
12.00 GB RAM
64-Bit Operating System
Intel Cor i7 2600 CPU @ 3.40 ghz
Nvidia GeForce GT 620 @ 1024 mb.
I run Malwarebytes Pro and Microsoft Security Essentials for my malware software.
I have also attached the Blue Screen View files on all three of the BSODs in question.
A potentially related problem that occasionally pops up, with no harm, is a weird bug where my video driver will crash, resulting in about a 5 second black screen and a recovery of the video driver. As this problem has occured, I have uninstalled and reinstalled my video driver to apparently no result in stopping any BSODs.
You will see the BSODs are spread out from 7-10, 7-17, and 7-30 - so somewhat regularly, but not following a specific pattern.
Thanks in advance for your help.
[attachment deleted by admin to conserve space]
-
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
-
Allan,
Okay. This was already in the .zip, but here it is c/ped.
The one from this morning:
==================================================
Dump File : 073015-17160-01.dmp
Crash Time : 7/30/2015 10:06:53 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`00fcb087
Parameter 3 : fffff880`03746808
Parameter 4 : fffff880`03746060
Caused By Driver : NDProxy.SYS
Caused By Address : NDProxy.SYS+1b025d56
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : partmgr.sys+e087
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\073015-17160-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 302,113
Dump File Time : 7/30/2015 10:07:58 AM
==================================================
The others mentioned:
==================================================
Dump File : 071015-18938-01.dmp
Crash Time : 7/10/2015 4:52:45 AM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`0000109b
Parameter 3 : 00000000`05030304
Parameter 4 : fffff8a0`151dc780
Caused By Driver : mwac.sys
Caused By Address : mwac.sys+a26a780
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071015-18938-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 302,369
Dump File Time : 7/10/2015 4:53:24 AM
==================================================
==================================================
Dump File : 071715-21980-01.dmp
Crash Time : 7/17/2015 10:01:15 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`0000109b
Parameter 3 : 00000000`05030102
Parameter 4 : fffff8a0`09d94690
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071715-21980-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 302,113
Dump File Time : 7/17/2015 10:01:54 PM
==================================================
-
Disable MalwareBytes and see if the problem persists
-
Thanks. It will take at least a week to be sure.
-
So, after a whole month of not having a blue screen (since the last post) I just got one.
This occurred shortly after bringing Malwarebytes back onto my system and running a scan.
==================================================
Dump File : 090115-18018-01.dmp
Crash Time : 9/1/2015 12:37:15 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`0000109b
Parameter 3 : 00000000`05030304
Parameter 4 : fffff8a0`0bb483e0
Caused By Driver : nvlddmkm.sys
Caused By Address : nvlddmkm.sys+197fa98
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090115-18018-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 302,241
Dump File Time : 9/1/2015 12:37:52 PM
==================================================
Can ya help me figure out how to resolve this so this doesn't happen again?
-
First of all, if the problem was resolved by not running MBAM, don't run MBAM. Second, the above bsod relates to your NVIDIA driver. You can try downloading and installing the latest driver for your display adapter. Use the nvidia uninstall tool to completely uninstall your current driver first.
-
...
I have recently begun to have infrequent, but somewhat regular, BSODs on my PC.
...
A potentially related problem that occasionally pops up, with no harm, is a weird bug where my video driver will crash, resulting in about a 5 second black screen and a recovery of the video driver. As this problem has occured, I have uninstalled and reinstalled my video driver to apparently no result in stopping any BSODs.
...
I would disagree. Video issues can related to what would seem to be another problem. Modem PCs have a complexity that most of us are not familiar with. It is almost like have an automobile that will not start because somebody does not have a seat belt in place. Very unexpected.
I would suggest you try other video card, even an older model with less performance. Make sure windows finds the correct driver for the alternative card.
-
The BSOD is back and does not appear related to the fully upgraded (through the Nvidia software) video driver.
Those are completely uninstalled and reinstalled and my latest BSOD has nothing to do with that it appears.
==================================================
Dump File : 092915-18501-01.dmp
Crash Time : 9/29/2015 9:12:51 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`0000109b
Parameter 3 : 00000000`05030309
Parameter 4 : fffff8a0`0be1a260
Caused By Driver : CompositeBus.sys
Caused By Address : CompositeBus.sys+6687260
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\092915-18501-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 351,265
Dump File Time : 9/29/2015 9:13:28 PM
==================================================
MBAM hasn't been run in several days, so my previous idea that it could somehow be related has nothing to do with this.
Computer had been freshly turned on after coming home from work. I had just opened chrome to begin browsing.
Sorry that it takes weeks between replies. This problem is infrequent enough that I need to wait for it to replicate, and as I cannot trigger it, I have to wait for it to do so naturaly.
How should I proceed in stopping this problem entirely? http://www.dlltool.com/vsksoft/dll/Jul-2015/21/CompositeBus-sys/ - Is this remotely legitimate? It looks illegitimate, so I have not downloaded anything from this company.
-
Did you check your Device Manager for any yellow warnings?
-
Never use online DLL fixit tools...bad way to go.
-
Never use online DLL fixit tools...bad way to go.
I assumed so. I never have, but I thought I'd ask in case my BS detector wasn't working right.
-
Did you check your Device Manager for any yellow warnings?
None have that yellow triangle with the exclamation point next to them.
-
It could be a flakey PSU...to test borrow a known good one of the same or greater wattage and swap it in there for a day or so....
-
It could be a flakey PSU...to test borrow a known good one of the same or greater wattage and swap it in there for a day or so....
I don't have a spare PSU off hand. Is there something I can do to identify this problem as potentially a PSU one to get my service warranty to cover a replacement?
I'd need some sort of tangible proof in order to get them to pony up the part.
-
Some things to consider. When everything else fails.
Are all fans running?
Reduce the number of items that require power. Remove the CD.DVD drive.
Remove one or two sticks of RAM. Remove any USB devices that are not needed for most work. Such as a printer. A USB hub. A smartphone charger..
Check to see if the default settings for the BIOS are right for the CPU and RAM type. Check to see if any settings seem odd.
Check to see if the CPU model is supported by the chaise.
*Explanation, rare, but it is possible somebody replaced the CPU with a model that almost right fro the chip-set. Verify the CPU is really in the chip set list.
-
Some things to consider. When everything else fails.
Are all fans running?
Reduce the number of items that require power. Remove the CD.DVD drive.
Remove one or two sticks of RAM. Remove any USB devices that are not needed for most work. Such as a printer. A USB hub. A smartphone charger..
All fans are running. Computer load has no effect on this, as it often will occur before there is even anything running, as with the last thing. The computer does have woring fans, though.
I will remove my phone charger and only plug it in when necessary. Good idea. It may have something to do with that!
Check to see if the default settings for the BIOS are right for the CPU and RAM type. Check to see if any settings seem odd.
Check to see if the CPU model is supported by the chaise.
*Explanation, rare, but it is possible somebody replaced the CPU with a model that almost right fro the chip-set. Verify the CPU is really in the chip set list.
How would I do the BIOs check? That is one thing I am not sure of.
-
Since the BSOD's are wide and varied i suspect a flakey PSU...just sayin.