Still getting BSOD on startup

[Crownos]

I made a post a few days ago as my pc was experiancing BSOD on startup every morning and i had to physically turn the pc on and off again too get it to work again.

After that i was told to run Verifier to stress the drivers and report any BSOD that it might trigger which should be tagged for you to see i was also told to run Memtest which i did and let it run for 7 passes and no error was seen which is good news but im still getting BSOD every morning when i start up the pc continuously wondering if anyone can help me more on this issue ty

This is my previous post info

Ive been having this problem around a week after i built my PC.. its a weird BSOD as it only happens first thing in the morning when i turn it on.. i get continuous rolls of BSOD's slightly after the windows start log appears. to stop the BSOD from happening i physically have to turn off the pc and turn it on again which works but is very much a nuscence and i have found that as the days go by the BSOD's get more troublesome to the point i had to format my HDD and reinstall windows but this never worked...

Firstly i thought it might be my graphics card (ATI 5870) so after i reinstalled Windows i used my mates graphics card (Nvidia 8600 GT) but the same BSOD appears every morning.

my guess it might be corrupt drivers or windows updates ruining or corrupting something.

I have tried the following

Formating HDD
Reinstalling Windows
Replacing Graphics cards
Re-Downloading different compatible versions of the Graphics card drivers.

and now after all this im very sure its not my graphics card but something else Maybe the RAM? or HDD? not to sure..

One problem is i cant make the BSOD appear if i do a certain thing even if i restart my pc a million times as it only happens in the mornings i find or probably if the pc has been off for a substantial amount of time odd i know lol.

 

[zigzag3143]

I made a post a few days ago as my pc was experiancing BSOD on startup every morning and i had to physically turn the pc on and off again too get it to work again.

After that i was told to run Verifier to stress the drivers and report any BSOD that it might trigger which should be tagged for you to see i was also told to run Memtest which i did and let it run for 7 passes and no error was seen which is good news but im still getting BSOD every morning when i start up the pc continuously wondering if anyone can help me more on this issue ty

This is my previous post info

Ive been having this problem around a week after i built my PC.. its a weird BSOD as it only happens first thing in the morning when i turn it on.. i get continuous rolls of BSOD's slightly after the windows start log appears. to stop the BSOD from happening i physically have to turn off the pc and turn it on again which works but is very much a nuscence and i have found that as the days go by the BSOD's get more troublesome to the point i had to format my HDD and reinstall windows but this never worked...

Firstly i thought it might be my graphics card (ATI 5870) so after i reinstalled Windows i used my mates graphics card (Nvidia 8600 GT) but the same BSOD appears every morning.

my guess it might be corrupt drivers or windows updates ruining or corrupting something.

I have tried the following

Formating HDD
Reinstalling Windows
Replacing Graphics cards
Re-Downloading different compatible versions of the Graphics card drivers.

and now after all this im very sure its not my graphics card but something else Maybe the RAM? or HDD? not to sure..

One problem is i cant make the BSOD appear if i do a certain thing even if i restart my pc a million times as it only happens in the mornings i find or probably if the pc has been off for a substantial amount of time odd i know lol.

Well 27 seconds into the boot a driver is loaded (maybe your Nvidia 3D driver). In order to find which please run driver verifier.

Beyond that, please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- 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 click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[Crownos]

I ran verifier and restarted the pc straight after i got this BSOD which is attached

 

[CarlTR6]

Your dump shows error code 124 which is a fatal hardware error. Please read this article: Stop 0x124 - what it means and what to try.

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a0f000 PsLoadedModuleList = 0xfffff800`02c4ce50
Debug session time: Sun Nov 21 09:10:56.251 2010 (GMT-5)
System Uptime: 0 days 0:00:20.297
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8005ac3028, fa000000, 400405}

Probably caused by : hardware

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

6: 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: fffffa8005ac3028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0311db58 fffff800`02ffd903 : 00000000`00000124 00000000`00000000 fffffa80`05ac3028 00000000`fa000000 : nt!KeBugCheckEx
fffff880`0311db60 fffff800`02b95593 : 00000000`00000001 fffffa80`03689340 00000000`00000000 fffffa80`03689390 : hal!HalBugCheckSystem+0x1e3
fffff880`0311dba0 fffff800`02ffd5c8 : 00000000`00000728 fffffa80`03689340 fffff880`0311df30 fffff880`0311df00 : nt!WheaReportHwError+0x263
fffff880`0311dc00 fffff800`02ffcf1a : fffffa80`03689340 fffff880`0311df30 fffffa80`03689340 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0311dd50 fffff800`02ffcdd5 : 00000000`00000008 00000000`00000001 fffff880`0311dfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0311dd90 fffff800`02ff0e88 : 00000000`00000515 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0311ddc0 fffff800`02a7dfec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0311ddf0 fffff800`02a7de53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0311df30 fffff800`02a81913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0548f688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memset+0x83


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_VRF_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_VRF_PROCESSOR_MAE

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

Because the crash happened only 20 seconds into your boot, there is a possibility of a power supply problem. It is not unusual for a faulty power supply to cause problems at startup. Do you have another known good power supply you can try? Do you get BSOD's when you boot in the Safe Mode?

Run Memtest again from a cold boot after your computer has been off for a while. Let it run for at least 7 passes. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html.

 

[Crownos]

unfortunatley i dont have another power supply to test with this is the first time ive gotten a BSOD on a hardware issue previous to this BSOD ive had ones relating to driver failure causing my BSOD but i just dont know which one yet :-\. but ill run Memtest again

 

[CarlTR6]

Is there a computer shop where you can buy a power supply and then return it if it does not solve the problem? Do you know anyone with a power supply that you could borrow? There is a possibility that it is still a driver issue. Drivers can cause an error code 124. But usually that occurs with blatantly obsolete drivers and/or many older drivers on the system.

 

[cybercore]

Yeah, even getting rid of Avast won't help here, X64_0x124_GenuineIntel_VRF_PROCESSOR_MAE. What is the state of your PSU, did it work well before? Could it be something else other than the Power Supply? It would be hard to test the CPU if it crashes so soon (unless you can test in safe mode), but you can test memory with bootable memtest86.



http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

 

[Crownos]

never had a problem with my PSU from that i know of its never turned off randomly or had any issues with it this is the first BSOD thats come up with 124 code issue and it came up straight after i was told to use Verifier to stress the drivers as it was firstly thought my random BSOD's in the mornings were due to bad drivers all other BSOD's ive had have pointed to some driver but this is the first its pointed to a hardware issue

i guess using Verifier did something as it happened straight after verifier told me to restart my pc when i did i got that 124 code BSOD.
Ive done the memtest twice now both tests have come up with no errors so my guess is nothinsg wrong with the memory.

also i forgot to mention that i had this issue before on my previous motherboard and i thought it was a motherboard issue so i got a refund and replaced it and still i have the BSOD issue when i load my pc in the mornings hate these BSOD lol so hard to solve :-\

as for getting a new PSU have no friends that have a PSU to help replace for testing tho as for buying one for testing and sending it back i dont have money to do that at the moment... the PSU is a OCZ GameXStream 850W PSU so as for there not being enough power pumped into the pc isnt an issue its more than enough but possibly a glitch with wireing im not sure.

 

[CarlTR6]

Go ahead and run Memtest again from a cold boot after your computer has been off for a while.

Drivers can cause a 124 error code. Usually this happens when there is a really obsolete driver or a many outdated drivers. Driver Verifier sdtresses the drivers and this causes a BSOD if it finds a faulty driver. Most times, the BSO"D will point to the faulty driver. In this case, you had a 124 error code that blamed hardware. The fact that the BSOD happened so quickly is what makes me suspicious of the PSU. Your PSU has ample power - if it is not faulty. Check the connections of every cable and wire. Make sure they are all properly seated and connected.

 

[Crownos]

ok ill re run memtest on cold boot and check all the connections are seated properly ill get back to you once im done