My apologies, I'll have to find out for certain later as I'm on my way to work! I bought my computer from a website called Vibox where i chose from a list of pieces and they sent me the built product. I'm fairly sure I'm running windows 7 ultimate, but I'm not 100% sure so I'll have to double check when I'm home unfortunately which will be later today. And yes there's a sticker on the side of my PC with a code, but I also found another code on my system settings next to windows so I took a photo of both to keep hold of.
Blue screen of death help!
- Thread starter Slothraki
- Start date
Your key will be the one on the sticker - the "Product ID" isn't the serial #.
Post back with the Windows edition and I can see if I can find a disc for you.
Home Premium you mean?
Bad new's as always. After doing a full and fresh reinstall of windows and a hard drive wipe, I installed the chipset drivers for my motherboard, and the graphics drivers for my gpu, installed the game again, loaded it up and surprise suprise. Blue screen. I'm done for the night but I'll leave you with the minidump I was given. Next step appears to be a case of taking it to a store to get properly examined unless anyone has any better ideas!
Edit - I didn't install any Bios drivers or anything which is what I'm hoping it is, although I have little faith.
View attachment 041915-34429-01.zip
Edit - I didn't install any Bios drivers or anything which is what I'm hoping it is, although I have little faith.
View attachment 041915-34429-01.zip
Last edited:
So much for that. I installed the newest Bios update for my mother board as well and blue screened within the first few minutes. No minidump file, but the stop code was 0x0000004A.
I've handed it over to PC world now anyway and they said it should be sorted between 5-7 days at a price of £50 plus parts. Let's see what they make of it!
I've handed it over to PC world now anyway and they said it should be sorted between 5-7 days at a price of £50 plus parts. Let's see what they make of it!
Last edited:
Joe C
Golden Master
- Messages
- 5,006
- Location
- Great Lakes State
could've saved 50.00 and replaced the motherboard yourself
Again, looks like either motherboard or CPU.
OC'ing is a primary cause of this BSOD - though if you're not overclocking, it could be a problem with either the board or the CPU (like I've said previously).
Kind of a waste that you took it into a shop IMO because you could have done it yourself...but your money
. Good luck, hopefully it gets fixed.
OC'ing is a primary cause of this BSOD - though if you're not overclocking, it could be a problem with either the board or the CPU (like I've said previously).
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa800e7e6038, 0, 0}
Probably caused by : AuthenticAMD
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: fffffa800e7e6038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:
fffff880`0335b5b0 fffff800`02d23cb9 : fffffa80`0e7e6010 fffffa80`0ce7b040 00000000`0000000a 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0335bad0 fffff800`02c033e7 : fffffa80`0e7e6010 fffff800`02c7e2d8 fffffa80`0ce7b040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0335bb00 fffff800`02b6a875 : fffff800`02cdfd00 00000000`00000001 fffffa80`0dd02930 fffffa80`0ce7b040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0335bb40 fffff800`02add6a5 : fffff880`0108fe00 fffff800`02b6a850 fffffa80`0ce7b000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0335bb70 fffff800`02d6daba : 00000000`00000000 fffffa80`0ce7b040 00000000`00000080 fffffa80`0cd97040 : nt!ExpWorkerThread+0x111
fffff880`0335bc00 fffff800`02ac5426 : fffff880`03117180 fffffa80`0ce7b040 fffff880`031220c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0335bc40 00000000`00000000 : fffff880`0335c000 fffff880`03356000 fffff880`0335b550 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_authenticamd_processor_cache_prv
FAILURE_ID_HASH: {1ad1b150-35c8-1f65-d8fb-43448eb460cb}
Followup: MachineOwner
---------Kind of a waste that you took it into a shop IMO because you could have done it yourself...but your money
. Good luck, hopefully it gets fixed.Similar threads
