BSOD (2 types)

[ericx5]

Hey guys I've been getting a BSOD ever since I built this computer, it began about 2-3 weeks after I started using this pc. So to start off these are my specs :

CPU - Intel Core i5-4670K 3.4GHz Quad-Core Processor
MOBO - Gigabyte GA-Z87X-UD4H ATX LGA1150 Motherboard
RAM - G.Skill Sniper Series 8GB (2 x 4GB) DDR3-2400 Memory
HDD - Western Digital Caviar Blue 1TB 3.5" 7200RPM Internal Hard Drive
GPU - Sapphire Radeon HD 7970 3GB Video Card
PSU - SeaSonic G 550W 80+ Gold Certified Semi-Modular ATX

The BSOD's are completely random, sometimes I don't get them for a week, sometimes I get them twice a day. The two error messages are 0x00000124 and 0x0000003b. Also, if this is of any use, I used a USB to install my windows 7, so it is NOT genuine.

 

[ericx5]

Bump (not sure if allowed)

 

[johnbl]

using usb to insall is not really a issue, except you can get a lot of undetected data corruption from USB devices so you should check your core OS files after the install.

start CMD.exe as a admin
then run system file checker
sfc.exe /scannnow <--------- this will check and try to fix any bad core OS files


Not having your copy activated is not really a issue. You can get a free 90 evaluation version from Microsoft anyway, and rearm it to get 180 days free with the enterprise version.

What is not supported is pirate versions, these cause legal issues and just often have problems because of hidden malware and the hacks have side effects that cause issues. If you have one of these versions, i would dump it and use the evaluation version of windows enterprise to test out the machine. I have done this many times
to work out hardware problems and not have to deal with getting a license each time. In the end the machine gets wiped and a licensed retail version of windows is installed.

 

[ericx5]

using usb to insall is not really a issue, except you can get a lot of undetected data corruption from USB devices so you should check your core OS files after the install.

start CMD.exe as a admin
then run system file checker
sfc.exe /scannnow <--------- this will check and try to fix any bad core OS files


Not having your copy activated is not really a issue. You can get a free 90 evaluation version from Microsoft anyway, and rearm it to get 180 days free with the enterprise version.

What is not supported is pirate versions, these cause legal issues and just often have problems because of hidden malware and the hacks have side effects that cause issues. If you have one of these versions, i would dump it and use the evaluation version of windows enterprise to test out the machine. I have done this many times
to work out hardware problems and not have to deal with getting a license each time. In the end the machine gets wiped and a licensed retail version of windows is installed.

Thanks for the reply! I ran the command as you did, and it fixed some files but was "unable to fix some others". I'll reply here once again if it didn't help.

 

[gizzard1987]

As for the actual error codes, the 124 code suggests processor failure, have you overclocked? Assuming so since you're running 2400 ram, also assuming you're wanting to run at 2400 and not have your ram downlocked to standard 1600.
You might try resetting you CPU to see if it helps that code.

This is what I found for the 3b error code. Apparantly it's relating to Microsoft IEEE 1394 driver stack. Are you using a 1394 (uses the same hookup as your front panel USB, for the case, would use on the motherboard) compliant mobo/case? I think that's firewire but I'm not 100%. I would double check your connectors on the motherboard and make sure you're not using a 1394 port for usb or vice versa.

Microsoft Hotfix for Windows Server 2008 R2 and Windows 7
Not sure if you can use this if you don't have genuine windows.

 

[johnbl]

the sfc.exe /scannow assumes that your original copy that it backed up is good (it is in a hidden location on your hard drive) when you use a USB install the original copy of the file might be already corrupted so you need to run a different command to get a good copy of the file from a online source.

the command is (run cmd.exe as a admin)
dism.exe /online /cleanup-image /restorehealth <--- this will fix the files from a trusted online source.

after you do this, you will want to run your
sfc.exe /scannow command to verify that the file is ok.
then reboot and run the sfc.exe /scannow command again (sounds stupid but you want to do this for various reasons)

using usb to insall is not really a issue, except you can get a lot of undetected data corruption from USB devices so you should check your core OS files after the install.

start CMD.exe as a admin
then run system file checker
sfc.exe /scannnow <--------- this will check and try to fix any bad core OS files


Not having your copy activated is not really a issue. You can get a free 90 evaluation version from Microsoft anyway, and rearm it to get 180 days free with the enterprise version.

What is not supported is pirate versions, these cause legal issues and just often have problems because of hidden malware and the hacks have side effects that cause issues. If you have one of these versions, i would dump it and use the evaluation version of windows enterprise to test out the machine. I have done this many times
to work out hardware problems and not have to deal with getting a license each time. In the end the machine gets wiped and a licensed retail version of windows is installed.

Thanks for the reply! I ran the command as you did, and it fixed some files but was "unable to fix some others". I'll reply here once again if it didn't help.

 

[ericx5]

After running "dism.exe /online /cleanup-image /restorehealth I get this message..

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>dism.exe /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385


Error: 87

The restorehealth option is not recognized in this context.
For more information, refer to the help.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

And to answer your question about overclocking, no I haven't overclocked anything at all in this system.

 

[johnbl]

Sorry, the command was added to dism.exe for windows 8 and windows server 2012
it was taken from the windows 7 commnad checksur.exe

http://community.spiceworks.com/how_to/show/35822-checksur-repairing-windows-update

http://windows.microsoft.com/en-GB/windows7/What-is-the-System-Update-Readiness-Tool

After running "dism.exe /online /cleanup-image /restorehealth I get this message..

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>dism.exe /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385


Error: 87

The restorehealth option is not recognized in this context.
For more information, refer to the help.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

And to answer your question about overclocking, no I haven't overclocked anything at all in this system.