next »

[Petah Parker]

i KEEP getting these BSODS, all the research i have done either points to memory (memtest pass, no errors) or a CPU not getting enough voltage (used RMClock, bumped up voltages, still happens.
Any help, please?

I usually get a 124 error, but now i get this one every once in a while.

Problem signature:
  Problem Event Name:   BlueScreen
  OS Version:   6.1.7600.2.0.0.768.3
  Locale ID:   1033

Additional information about the problem:
  BCCode:   f4
  BCP1:   0000000000000003
  BCP2:   FFFFFA8008497950
  BCP3:   FFFFFA8008497C30
  BCP4:   FFFFF8000317F240
  OS Version:   6_1_7600
  Service Pack:   0_0
  Product:   768_1
Minidump: http://dl.dropbox.com/u/2220265/%21Temp%20items/013010-31168-01.dmp
Minidump for previous errors: http://dl.dropbox.com/u/2220265/%21Temp%20items/012810-68328-01.dmp

[Krush]

I never learned to analyze those dump files, and I found this article. Someone else wrote you can use those information to track down the system's driver that might have been involved with the crash.

Anyway I didn't have much time and took a quick look into the dump file itself. I found some interesting looking lines beginning at line 230. I just may guess what it could mean:

Maybe you got some overheating with your CPU(/gfx card)... at least it was checking the thermal state right before.

Next line you got to read without the "NUL" symbols and it talks about some virtualized process, some CPU settings - I don't get anything from it except it might be some kernel or driver part - well, and then it goes "Terminating critical thread 0x%p (in %s)"
Three lines of the thread getting killed.
Then it seems to try to do some reconfiguring or validating of buffers (because the one thread died..). Blabla..
Next line contains one interesting word "lanman" (lead here) what might suggest the network driver crashed then... Is it not the CPU but the network card?
Right then you see how it seems to get crushed in the mess of messed up memory/buffer sections. "hotpatch" lead here. But that doesn't tell me more than the system actually tried to fix the situation...

Well, didn't get much from it. Just that it might be CPU/gfx card/controller temperature, your LAN card or some special process you are running on your system.
For the last maybe you could check your task manager for virtualized threads... oh, by that I remember it also might be about a virtualized process on one core that gets messed up like some do...
Also check for updated drivers for your system (including CPU drivers).

Well.. 
I hope you find something or someone else gets more from this. Can't help more yet. Good night and good luck!

[Petah Parker]

k, well VMware is always running so that could be the network issues.

All temps are within acceptable ranges, even during heavy gaming, the GPU peaks at about 70c, never have any issues then.
GPU runs about 60c at home, and thats not gaming, running a 22" external monitor
CPU runs about 40c under ~20% usage.

I will kill VMware, and see if it reoccurs.

[Krush]

Try that.

60°C GPU temp under low usage would get me worried. (But well, I never had one of the actual high end graphics cards...)

What I actually meant with "checking for virtualized processes/threads" - in the (Windows beginning with Vista) task manager you can right click processes and check whether they are being virtualized.

[Petah Parker]

Problem signature:
  Problem Event Name:   BlueScreen
  OS Version:   6.1.7600.2.0.0.768.3
  Locale ID:   1033

Additional information about the problem:
  BCCode:   124
  BCP1:   0000000000000000
  BCP2:   FFFFFA8007505038
  BCP3:   00000000B2000040
  BCP4:   0000000000000800
  OS Version:   6_1_7600
  Service Pack:   0_0
  Product:   768_1


And yet again, this is the 124 code.
http://dl.dropbox.com/u/2220265/%21Temp%20items/020310-28813-01.dmp
after an hour of light internet browsing, no gaming, no OC.

These are all the consistently virtual processes.

[Petah Parker]

Okay, the GPU just hit 70c doing NOTHING.
I have a comfy box for this laptop.

[Krush]

70°C doing nothing seems weird.

Yeah, I use HWMonitor, too. Leave it running all time and check for the highest temperatures it reaches.


When searching the internet for "BCCode: 124" you find some interesting discussions. This thread and especially this post looked interesting. Maybe you try the tool to see whether it's the GPU overheating.
Maybe it has to do with overheating, but I am not sure about it. I tend more to think of a configuration problem or some process causing this.
Trying debugging (to find the causing process/driver) might help. (Some threads describe how to do so easily.)


Also I like this:

Service Pack:   0_0

[Petah Parker]

tomorrow is backing up, and im getting a new one.
I dont know whats wrong with this one, but the bsod decoder that i looked at with the BB peoples pulled up a BUNCH of random stuff over the past 3 bsods.

[Krush]

Arr. Strange seemingly unsolvable problems aren't nice.
- Same with another friend except he is out of guarantee and gave trouble shooting up having to buy a new one now. (And he just had it gotten repaired some time ago.)

Well, that's just great if you get a completely new one from them then. I hope you'll not have to wait long!

[Petah Parker]

nope i waltz in, get a new one, waltz out.
the part that SUCKS? backing up about a TB of bluray movies.

[Koldar]

Yeah, lol. Backups are boring, but I was glad I had a 1TB backup outside my house when we got robbed, didn't lose one important file except my OS and programs... which the install files were on that 1TB, lol.

And I wouldn't try too much to read through BSODs, it's pretty rare you'll completely pinpoint the issue, it CAN help, but it's not rare that say, component A malfunctionned, causing driver B to work bad, and BSOD on program C that wouldn't work right, and not give you the right lead. But yeah, when it's under warranty, and a laptop, I wouldn't bother too much, and just get a new one. Got to abuse the warranty while it's still on.

[Petah Parker]

Im fairly certain its the GPU thats causing all the problems, i not have times where the screen will  go all stripey, and everything will hang for a sec, and windows will tell me im having bad graphics performance, pulled the gpu, started in safe mode, and everything was rock solid.

Edit: i cant get BSODS any more, only kernel panics. fook you winblows.