BSOD suddenly, after I reinstall Windows

[Insomn1a]

If a hard drive makes more noise than it used to, it's a sign that the internal mechanism is slowly failing. But only if it is really making a noise, like if you have a case that cancels most of the noise and you can hear the hard drive quite well, in that kind of a situation the mechanics of the drive is slowly failing and it is then usually advised to change the drive.

As that is something internal with the drive, doing things with the drivers, power and connection won't change anything. Additionally, any test you throw at the drive may show no sign of failure, because that is yet to come.

But why that noise is happen when I changed power supply?
I don't know if was in that moment or after but about then.

 

[Insomn1a]

Can be something wrong if I have before on motherboard that source with 20 pins and now I connect from power supply and that 4 pins (20+4)?
To separate that 4 pins?

 

[axe0]

I'm not sure I understand what you're saying, could you clarify?

 

[Insomn1a]

Which part you don't understand?

My new power supply have 20+4 pins which comes on motherboard.You understand about I say?
Ok so far, my old source have 20 pins, my motherboard have 24.Can be some problem if I connect all pins in the motherboard?
I can receive BSODs from this or from this Hard-disk is noisy?

 

[axe0]

20+4 is just for reverse compatibility with older motherboards that only support 20 pins connections, it won't cause any problems when you connect everything.

 

[Insomn1a]

I can do some tests for power supply?
Maybe he use more power energy or what can be?When I changed the power supply the noise on HDD appeared I think.I don't know if before to "fry" so when Windows start (bootup) or when I upload something or download on HDD then will appear that noise but isn't very strong that sound, maybe sometimes.
I want to know if to return power supply, I have this option.Maybe is something incompatible between other components...
To check voltage what I can do?
Something is because shouldn't be that BSODs and noise to HDD.

 

[axe0]

Is the PSU listed in your specs the one you're currently using?

 

[Insomn1a]

Is the PSU listed in your specs the one you're currently using?

Yes, that is.

 

[axe0]

I've never heard of that brand before, doing research it looks like quite a lot don't like the brand because many hardware vendors from China don't provide high quality products.
Honestly, to me it does sound a little like the PSU may be causing some trouble if the hard drive started to make noises after installing the PSU.

 

[wither 2]

I'm guessing it's Seasonic

 

[Insomn1a]

But before I have a power supply very cheap, like 10 euro.
With that source why I don't have issues like this?This have protections, certificate bronze, modular.
To test again with that power supply to see if is problems with noise at hdd?

 

[axe0]

Lots of the fancy stuff describing the features of the PSU don't really say much about the actual quality of the PSU.

Please note that you should not try to save money on the PSU, that is something you will regret. Also, a PSU for 10 euro's sounds a little difficult to believe, because if you buy a proper one second hand I estimate it to cost around 50 euro depending on how much it was used and the original price.

 

[Insomn1a]

To be processor at fault?Why can't be seen CPU or motherboard in that dump archive which I gave?

What tests I can do to processor to see if works better or can be him fault?

 

[axe0]

A dump is mainly meant as a tool for diagnosing software problems and not hardware.

 

[Insomn1a]

I can do again that test to see what is happen if is the same thing?Maybe now is different something.

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-GJY49-VJBQ7-HYRR2
Windows Product Key Hash: W5/6nm6F2UPXrCkY5xUhXb/+21g=
Windows Product ID: 00426-OEM-8992662-00006
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010100.1.0.001
ID: {8A1E0171-A974-449D-99A5-D0E98D105F54}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Ultimate
Architecture: 0x00000009
Build lab: 7601.win7sp1_ldr_escrow.190305-1700
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{8A1E0171-A974-449D-99A5-D0E98D105F54}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-HYRR2</PKey><PID>00426-OEM-8992662-00006</PID><PIDType>2</PIDType><SID>S-1-5-21-4103039494-805482309-3500066891</SID><SYSTEM><Manufacturer>To Be Filled By O.E.M.</Manufacturer><Model>To Be Filled By O.E.M.</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>P2.00</Version><SMBIOSVersion major="2" minor="5"/><Date>20091012000000.000000+000</Date></BIOS><HWID>6C653807018400F4</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GTB Standard Time(GMT+02:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>ACRSYS</OEMID><OEMTableID>ACRPRDCT</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, Ultimate edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: 7cfd4696-69a9-4af7-af36-ff3d12b6b6c8
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00426-00178-926-600006-02-1033-7601.0000-0842019
Installation ID: 015226815242825900884161667074590750081660643383087750
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: HYRR2
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 3/25/2019 7:44:23 PM

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: MgAAAAEABAABAAEAAAACAAAAAQABAAEA6GEmUb6YQigGmMK3mGBix2zimogiEv7LGHk=

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information: 
  ACPI Table Name	OEMID Value	OEMTableID Value
  APIC			101209		APIC1141
  FACP			A M I 		OEMFACP 
  MCFG			101209		OEMMCFG 
  OEMB			101209		OEMB1141
  AAFT			101209		OEMAAFT 
  NVHD			101209		NVHDCP 
  SSDT			A M I 		POWERNOW
  SLIC			ACRSYS		ACRPRDCT

 

[Insomn1a]

Bump!

 

[Bonnie Zhang]

Here are some ways to diagnose, prevent or fix blue screen in Windows 7
1. Install the latest drivers
2. Install updates
3. Run startup repair
4. System Restore
5. Fix memory or hard disk errors
6. Fix Master Boot Record
7. Reinstall Windows 7

 

[Insomn1a]

Here are some ways to diagnose, prevent or fix blue screen in Windows 7
1. Install the latest drivers
2. Install updates
3. Run startup repair
4. System Restore
5. Fix memory or hard disk errors
6. Fix Master Boot Record
7. Reinstall Windows 7

How to:
3.Run startup repair
4.System Restore
5.Fix memory or hard disk errors (I just test for these and didn't find anything).
6.Fix Master Boot Record?

 

[wither 2]

For 4.0- Go to Control Panel, System, Advanced System Settings, System Protection. You can set a System Restore point there.

If you have a recovery disk you can do a startup repair from there. Similarly, you can also select a Command Prompt and run commands to fix the MBR. I'm not going to go into details on these items.

Someone else might add their experience.

 

[Paul Black]

Hi Insomn1a,

If you have a recovery disk you can do a startup repair from there.

Further to wither 2's suggestion above...

Win 7 System Recovery Options - With Installation Disk

Any Win 7 installation disk [regardless of version] contains ALL the versions of Win 7 [Home, HomePremium, Professional, Ultimate]. What differentiates the version ID is the mode that is set as the default in the \sources\ei.cfg file. Removing or renaming this file allows all the versions of Win 7 to become available during re-installation. This is very useful if you want to create an all-in-one installation media.

Also contained within the installation disk [regardless of version] is the \sources\boot.wim folder. This folder contains two wizards [they are identical for all the versions], the Installation wizard and the Maintenance wizard. Therefore, any Win 7 installation disk, as long as it is the SAME bit type as the one installed, can be used to access the repair tools.

Boot into the DVD installation disk and run Startup Repair from the System Recovery Options menu.

I hope this helps!