Solved BSOD Windows Vista Home (Premium) Help Needed!

Criz213 · Feb 7, 2015

Hello,

I am having a problem with my computer a Blue Screen Issue that has been ongoing over the past 2 years dealing with this same problem. I fixed it temporarily with re-installing the whole computer with my windows vista CD and that helped to solve it temporarily. But after a while it will start failing over again and having lots of bluescreens. I posted here a while back and one of the guys helped me which solved it for a bit but than it failed again over a while. My computer is a Windows Vista Home Premium x64 bit, my system specs are noted down on my profile. I really need help on this problem which I want to get resolved. I also did a /chkdsk using cmd and it ran a chkdsk scan and no corruptions or problems on the driver was found. I have attached some .txt files when I went to EventViewer and attached them on here including the errors found on the computer that caused the BSOD. I also ran the SF Scan and but I had to run it on Safe Mode Networking because I couldn't really boot up the computer. Sometimes my computer crashes a lot sometimes it don't but it still crashes.

Also here are some bluescreen error codes that I noted down:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000003451
BCP2: FFFFF6FD3003CB48
BCP3: FFFFFA8007159060
BCP4: 0000000000000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini020715-01.dmp
C:\Users\Cortez\AppData\Local\Temp\WER-74490-0.sysdata.xml
C:\Users\Cortez\AppData\Local\Temp\WER1219.tmp.version.txt

Read our privacy statement:
Privacy Statement for the Microsoft Error Reporting Service

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: f7
BCP1: 0000FA600105D030
BCP2: 0000FA600105D031
BCP3: FFFF059FFEFA2FCE
BCP4: 0000000000000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini020715-02.dmp
C:\Users\Cortez\AppData\Local\Temp\WER-84146-0.sysdata.xml
C:\Users\Cortez\AppData\Local\Temp\WER925F.tmp.version.txt

Read our privacy statement:
Privacy Statement for the Microsoft Error Reporting Service

Thank You So Much!

richc46 · Feb 7, 2015

To be helped with BSODs, it is important that you follow these instructions
http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html
I know that you are having problems getting the reports, can you try again?
Without those reports we can only guess.

Criz213 · Feb 7, 2015

Yes I attached the reports but somehow it did not show up but I'll reattach them right now.

I pasted the links here just in case it doesn't attach.

SF Diagnostic Tool: http://www.vistax64.com/attachment.php?attachmentid=28809&d=1423337264

Error Major: http://www.vistax64.com/attachment.php?attachmentid=28807&d=1423337264

EventViewer: http://www.vistax64.com/attachment.php?attachmentid=28808&d=1423337264

richc46 · Feb 8, 2015

OK Criz. Lets see if I can help.
From the reports, this appears to be a hardware problem. I have found in this situation the best thing to do is rule out drivers, which is the most common cause, although not hardware.

We will start with the driver verifier.

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 "Force Pending I/O Requests" 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.

Sorry for the delay. Our team is working on several other BSOD problems at the moment.

Criz213 · Feb 8, 2015

Okay I will try when it boots up because it really won't let me boot up the computer at all right now

richc46 · Feb 8, 2015

Can you boot in safe mode?

Criz213 · Feb 8, 2015

No its not letting me go on safe mode anymore it just runs the drivers after that when its going to go to login window it just crashes to the bluescreen.

richc46 · Feb 8, 2015

Do you have a vista install DVD?

Criz213 · Feb 9, 2015

Yes I have the Vista CD but right now I got it to boot up I pressed F8 while windows loads and disabled automatic restart and it booted up. I am backing up my data right now with my external hard drive. So after the back up do you want me to run the verifier ?

richc46 · Feb 9, 2015

Criz213 · Feb 12, 2015

Sorry about the late reply Rich. I reinstalled my whole computer and backed up all my data on my external hard drive. It was working fine and everything it did help a lot with the reinstallation but in case of anything I created a system restore point in case I need to go back to it if its failing. But right now it just crashed into a bluescreen again. I am going to run verifier right now like you told me and wait for it to crash. So when it crashes while running verifier I post back here right?

richc46 · Feb 12, 2015

Just give the reports like you did the last time.

Criz213 · Feb 13, 2015

Hey Rich I have the files you needed I ran the SFC Scan again. I attached the files. I ran verifier.exe and it crashed about 4 times until I just shut it down and deleted the verifier settings. It crashes approximately 20 mins after I ran the verifier and crashed about 20 minutes after each time as an estimate.

SFC Scan Attachment:

http://www.vistax64.com/attachment.php?attachmentid=28817&d=1423849495

richc46 · Feb 13, 2015

You did a good job with the reports
Here is a copy of the report that gave us important clues.

Code:

 Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_SF_13-02-2015.zip\SF_13-02-2015\Mini021215-14.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18881.amd64fre.vistasp2_gdr.130707-1535
Machine Name:
Kernel base = 0xfffff800`01a12000 PsLoadedModuleList = 0xfffff800`01bd6e30
Debug session time: Thu Feb 12 18:10:44.739 2015 (UTC - 5:00)
System Uptime: 0 days 0:29:37.714
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff880171dfd40, 2, 0, fffffa6008f19ed7}
Unable to load image \??\C:\Windows\system32\drivers\mwac.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [B]mwac.sys[/B]
*** ERROR: Module load completed but symbols could not be loaded for [B]mwac.sys[/B]
Probably caused by : mwac.sys ( mwac+7ed7 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff880171dfd40, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffa6008f19ed7, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001c39080
 fffff880171dfd40 
CURRENT_IRQL:  2
FAULTING_IP: 
mwac+7ed7
fffffa60`08f19ed7 ??              ???
CUSTOMER_CRASH_COUNT:  14
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD1
PROCESS_NAME:  mbamservice.exe
TRAP_FRAME:  fffffa60095df740 -- (.trap 0xfffffa60095df740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff9800cecaf00 rbx=0000000000000000 rcx=fffff9800cecafcf
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6008f19ed7 rsp=fffffa60095df8d0 rbp=0000000000000000
 r8=fffff880171dfd40  r9=fffffa60095df7d0 r10=fffff9800ceca010
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
mwac+0x7ed7:
fffffa60`08f19ed7 ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80001a68eee to fffff80001a69150
STACK_TEXT:  
fffffa60`095df5f8 fffff800`01a68eee : 00000000`0000000a fffff880`171dfd40 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffa60`095df600 fffff800`01a67dcb : 00000000`00000000 00000000`00000000 00000000`6961776d 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`095df740 fffffa60`08f19ed7 : 00000000`00000000 fffffa60`08f205f0 00000000`0000002c fffff800`01cf6100 : nt!KiPageFault+0x20b
fffffa60`095df8d0 00000000`00000000 : fffffa60`08f205f0 00000000`0000002c fffff800`01cf6100 00000000`00000000 : mwac+0x7ed7

STACK_COMMAND:  kb
FOLLOWUP_IP: 
mwac+7ed7
fffffa60`08f19ed7 ??              ???
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  mwac+7ed7
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: mwac
IMAGE_NAME:  mwac.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  53a0f410
FAILURE_BUCKET_ID:  X64_0xD1_VRF_mwac+7ed7
BUCKET_ID:  X64_0xD1_VRF_mwac+7ed7
Followup: MachineOwner
---------

I have bolded the cause MWAC.sys. It is a bit of a surprise, but that is Malwarebytes. MB does not usually cause problems. The only situation that I have encountered is when you have the trial of premium and the trial period expired.
In any case make a system restore point, uninstall MB, boot and see if you work any better.

If I do not hear from you before tomorrow morning, I will be off line until about Monday. Hey its Valentines Day in cyber land too.
Wish you luck, buddy.

Criz213 · Feb 14, 2015

Thank You So Much Rich! Yes I never would have imagined that Malwarebytes could have caused this crash. Yeah well I had the premium version but I guess I'll have to find out another anti-virus program. Is Microsoft Security Essentials any good? I will uninstall Malwarebytes right now, and see what happens. An okay thanks and Happy Valentines Day too :D Hope You Have A Good One. If any other problems occur I'll post back!

Criz213 · Feb 16, 2015

Hey Rich my computer crashed 2 days ago in bluescreen again. To delete malwarebytes completely I just formatted my hard drive. But yet I received a crash. I have the updated file attached here of the SFC Scan. But I will continue to use the computer to see if it crashes again, and also I turned the verifier.exe on and it crashed there its included in the attached file.

File:

http://www.vistax64.com/attachment.php?attachmentid=28821&d=1424108131

richc46 · Feb 16, 2015

Turn off verifier. If you still crash, I am sorry to say it is probably a hardware problem. If it is you will have to fix it yourself or bring it into a shop. Let me know if you do crash with verifier and if you do, we will test your memory to start.

Criz213 · Feb 17, 2015

Well its weird it crashed, but now the computer is working after I turned off verifier.exe it hasn't crashed at all. But I'll see if it crashes. But for this instance I am going to mark it as solved, as that malwarebytes antivirus removing that helped my computer. Thanks a lot Rich For The Help :D ! As of right now my computer has been on and no crash. I really appreciate the help.

richc46 · Feb 17, 2015

I think that Malwarebytes solved the problem. Verifier clearly indicated that was the cause. Verifier causes crashes, even if you would not normally have one. I even showed you the report. If the problem does continue after a reformat, it is hardware. We have to go step by step to find the cause. In any case, I am glad that it appears that I helped solve the problem and I wish you luck.
Rich

Solved BSOD Windows Vista Home (Premium) Help Needed!

Attachments

My Computer

My Computer

Attachments

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

Attachments

My Computer

My Computer

My Computer

Attachments

My Computer

My Computer

My Computer

My Computer