Random windows 7 crashes, ntoskrnl.exe+4ade0c, 0x00000124, 1035.

Hi, these bluescreens and random crashes started about 1 month ago while playing games or when using chrome, ie, firefox. I have located this error with BlueScreenView.exe and like the topic says the thing causing these crashes is ntoskrnl.exe+4ade0c and the bug check code is 0x00000124.

I visited and "fixed" my pc at the local store witch i used to purchase my current pc from, every problem i've had, they have fixed it except this one. They just don't know how to fix it or don't know what the problem is.

Tried to fix pc via installing dvd, it recognized the problem somehow saying the error is something called 1035 but thats it, even my windows installing dvd cant help me this time. any help? :)
and i attached this minidump rar to this thread.

OK so took a look at the files you provided, and right off the bat I should inform you that a 0x124 error is 9 times out of 10 a hardware problem. looking at the error record we can see that the error its self is a Bus error and in my experience this points to either a CPU failure or a mother board failure, however it could also be overheating or a BIOS bug.

Code:

kd> !errrec fffffa8007e7f6a8
===============================================================================
Common Platform Error Record @ fffffa8007e7f6a8
-------------------------------------------------------------------------------
Record Id     : 01ce5dd4a5d37641
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/31/2013 7:58:41 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007e7f728
Section       @ fffffa8007e7f800
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000100f43
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007e7f770
Section       @ fffffa8007e7f8c0
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 43 0f 10 00 00 08 04 00 - 09 20 80 00 ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8007e7f8c0

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007e7f7b8
Section       @ fffffa8007e7f940
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfa00000000070f0f

So to start if you are overclocking anything please stop, over clocking pushes hardware beyond its limmits and can often cause these kind of errors.

Next please download one of the following tools to monitor system temperatures:

HWinfo
CPU Z <- this one is for the CUP only and will not monitor any other components temperatures.

Once you have one of those installed plead download and run the following CPU stress test:

Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Large FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Keep an eye on your temperatures and report them here when the test is done/ when it crashes or starts to throw errors.

So i had this program running for the last 12 hours, no problems nor errors spotted but somehow i wasn't able to see my CPU heat. Tried 4 different CPU monitors, none of those programs were able to show me the CPU's heat, only that the CPU was running at 100% of its maximum potential. But when i put my hand on the CPU and power source, i can say it was around +50-70 °C (cos my graphs card is always around 60-70°C when playing games and i know how it feels in my hands when its hot.)

I updated my bios just 2 days ago and still having the same problem, installed win 7 64-bit over my 32-bit, same problem. So i think that can remove the BIOS bug out of the list what may cause my problems.

but lucky me, if the problem is my CPU or Motherboard i still have warranty.

Any ideas what i should do next? :)

Interesting, the fact that the CPU wont register temperature unless only two Cores are in use is...concerning, but the fact that you were not getting any errors when running Prime95 makes me want to lean more towards the motherborad or a possible PSU failure unfortunately the trio of CPU, PSU, and motherboard are very hard to diagnose without actually swapping the components out.

Well I am glad to here things are working out.