BSODs after Windows 7 reinstall

[danik2212]

Alright guys, I had to reinstall windows 7 after being infected by a bad virus who put all my files to hidden and let the door open to a lot of virus. I had some BSOD (1 per month) before, but now, I can't barely stand 10 minutes without getting one and it's always the same code, I have purchased Driver genius and ran it, so all my drivers are up to date but my fingerprint scanner which I never used or installed the driver. I changed my hard drive thinking that it was the problem and it didnt solved it. I also ran the Ram test and it says I'm good. and I don't get BSOD while running in safe mode or safe mode with networking. I hope you guys can help me out.

 

[zigzag3143]

Alright guys, I had to reinstall windows 7 after being infected by a bad virus who put all my files to hidden and let the door open to a lot of virus. I had some BSOD (1 per month) before, but now, I can't barely stand 10 minutes without getting one and it's always the same code, I have purchased Driver genius and ran it, so all my drivers are up to date but my fingerprint scanner which I never used or installed the driver. I changed my hard drive thinking that it was the problem and it didnt solved it. I also ran the Ram test and it says I'm good. and I don't get BSOD while running in safe mode or safe mode with networking. I hope you guys can help me out.

These are all virtually identical and blame hardware. I would first download malwarebytes and run it in safe mode to ensure you have gotten rid of the malware.


Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051911-43243-01.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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02e4f000 PsLoadedModuleList = 0xfffff800`0308ce50
Debug session time: Thu May 19 17:59:17.629 2011 (GMT-4)
System Uptime: 0 days 0:19:44.440
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004fe1038, b6200040, 2010a}

Probably caused by : hardware

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004fe1038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6200040, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000002010a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8a98 fffff800`02e18903 : 00000000`00000124 00000000`00000000 fffffa80`04fe1038 00000000`b6200040 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`02fd5493 : 00000000`00000001 fffffa80`04fe1ea0 00000000`00000000 fffffa80`04fe1ef0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`02e185c8 : 00000000`00000728 fffffa80`04fe1ea0 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`02e17f1a : fffffa80`04fe1ea0 fffff800`00ba8e70 fffffa80`04fe1ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`02e17dd5 : 00000000`00000002 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`02e0be88 : 00000000`040ba46c 00000000`01b921e0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`02ebdfac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`02ebde13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 00000000`6fb3641c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0052ebc4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6fb3641c


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner
---------