New
#11
ok thanks ill reply back with results
Generic 0x124 stop BSOD ntoskrnl.exe
-
-
New #12
Driver verify never made his computer blue screen. as soon as he turned driver verify off, his computer bluescreen'd as soon as he was watching a video on youtube. hopefully you can see something different.
he also claims his computer never does actually blue creen, it just restarts on its own.
-
New #13
Still Hardware. Is anything in the computer overclocked? If yes, get them back to factory defaults.
A little part of the dump shows the Processor/CPU being in a problem. Lets stress it with the CPU stress utility.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8008493748, 0, 0} Probably caused by : hardware Followup: MachineOwner ---------
CPU - Stress Test Using IntelBurnTest
Let me know the results
Code:TACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV Followup: MachineOwner
-
New #14
I had tried a stress test to see temps before and nothing really happened. how long should i do the stress for? and no nothing is overclocked.
-
-
New #16
ok ill let you know the results tomorrow
-
-
New #18
Said all the tests went through. Got a new blue screen with a hal.dll. he is coming over to my house tomorrow so ill get the dump for that. I am going to try switching out video cards and hard drives to see what happens.
-
-
New #20
Yeah, but now he told me that the 3rd test restarted his computer with the ntosknrl error
Quote
Related Discussions