Yeah there is actually a certain point coming out of sleep modes where a crash dump can't be collected. I would enable a complete crash dump collection instead of a kernel crash dump, find someone in Microsoft support (don't even know if this kind of service exists) that will look at your crash dump with windbg to give you details. Let me research the availability of symbol definitions for Windows. What version of Windows are you running?

The bug check number helps, in this case 3B, but it doesn't tell you everything. Graphics driver runs in kernel mode btw. I think some driver running in kernel mode is trashing memory but have no idea which one.

BTW my understanding is that the layoffs at Microsoft in Bellevue/Redmond announced yesterday hit the test teams really, really hard. Fully testing kernel mode win drivers is often challenging, particularly graphics drivers. The effectiveness of QA for Microsoft products should be interesting to observe.

I've seen this so much....

It is something to do with Intel, but cant remember exactly what off the top of my head. Gimme a few mins and I'll try to find it.

But Update your intel software from the PCs Manufacturers website - it is one of those.

Edit: Found it. It is the Intel Management Engine - updated drivers should be available from your pc manufacturer.

Adios - there are actually 2 different BSODs in here ... the 3b error was someone else.

Edit: Found it. It is the Intel Management Engine - updated drivers should be available from your pc manufacturer.

This computer does not meet the minimum requirements for instaling the software.

If it is still under some kind of return policy, return it!

meh dunno, i expected a lenovo for 1,5k to last more than a month... plus im travelling around the world undefinetelly.. i dont have time for reclamacy hassles.
just suck it up and buy a ****ing macbook i guess. all my life i had issues with windows anyways

All machines should last more than a month. However, problems occur. This is why warranties and other return schemes exist, although of course you've chosen to be beyond the reach of yours. In those circumstances a Lenovo was a decent choice - they're pretty well thought of for reliability. Still, we are where we are. You got unlucky, and can't just return it, so we need to try to fix it...

Please link to the page with the software you're trying to install. Post, too, any specs of your machine that you think are relevant here.

I would contact Amazon.de about returning it and see what they say. The worst they can say is no.

Oh, you are right adios. Last thing I remembered was when they moved it out of kernel mode into user mode, but that was long ago. LOL. Never had any problems in the past decade running NVidias. Btw, the symbols are available online. Just let the kernel symbol definiton point to the correct URL (srv*DownstreamStore*http://msdl.microsoft.com/download/symbols) and WinDbg will download the corresponding symbols from Microsoft. Since Microsoft is offering frequent updates via Windows update, this is a neccessity. Unfortunately WinDbg is not available seperately anymore -> http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx. Once it is installed just set the correct symbol search path, open the dump file (.DMP) and then enter "analyze -v".

If I get a URL to the crash dump file somewhere and you send me a PM I can have a look at it with WinDbg if you like. Please note that this will contain all the memory, so there maybe sensitive information in the dump, depending on the apps that were running at the time of the crash. Sometimes it will reveal more info about what was happening when the crash occured, sometimes it will just make you bang your head against the wall. Alternatively you can try to install WinDbg as described above and paste the result of analyze -v for us.

3B can be the graphic adapter but not neccessarily.

http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx

The GPU architecture is a bit complicated and somehow split into multiple components, am no expert at GUI stuff. Applications use GDI.DLL, running in user mode, to communicate with the GPU. GDI.DLL talks to win32k.sys, running in kernel mode. Win32k.sys then passes the data to the GPU driver. This should in theory isolate the GPU driver and make the system more secure and more stable. In this process there is multiple switches between user and kernel mode, and some unprivileged (!) code caused an exception that should never ever do that (possibly the GPU driver).

You could also try to boot in VGA safe mode with networking to rule out some 3rd party drivers running the system in VGA mode (most likely with a lower resolution).

If this works, it must be some 3rd party driver like GPU, chipset, antivirus, network or whatever.

Running Windows Update may help as well.

A person with experience doing this. Hopefully OP will get in touch with you because you could help him probably.

On the graphics driver, like you said, it is complicated with a several components. On Win 8 I was working on kernel mode issues with drivers and graphics was one of them but I concede I am not totally knowledgable about the code for that driver. You can get the DDK online for free and it has windbg, at least last time I looked it was but it has been awhile.

I still say OP should contact Amazon and see about returning it. Yes, he's not in Germany but that wouldn't prevent him from shipping it to them.