My first blue screen of death

[jabbok]

If you do wind up with more BSOD errors, try installing and running this utility WhoCrashed 3.03 - CNET Download.com

It will analyze the crash dump files and provides comprehensive read outs of what the cause could be related to whether it is hardware or software related. It will even provide a Google search term on occasion.

I am going to have to use this program I received my system yesterday and it has blue screened several times 1 was a memory management stop error and the rest the system just rebooted and said it recovered from an error. Also the system is hanging while trying to do the windows download and installs, I haven't changed or added anything to the system do you think I should do a factory recovery?

Specs:

i7 3920XM
8 gb ram
msata 64gb plus 500gb hdd
Crossfire 7970 gpu's

[Juscallmesteve]

These are my reports for my crashes.

On Wed 5/30/2012 12:11:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053012-22620-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8009111390, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 5/30/2012 12:11:00 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8009111390, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 5/30/2012 3:07:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052912-23431-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF8B40F3DB94C, 0x0, 0xFFFFF80002F489AE, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 5/29/2012 8:43:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052912-28813-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AADD3)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002DC8DD3, 0xFFFFF880037CB778, 0xFFFFF880037CAFD0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 5/29/2012 6:16:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052912-22776-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF6800001E1F0, 0xE1800006C3FDE867, 0xFFFFFA80199A0790)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Those are all after i did the factory recovery.....

[Mr. Fox]

As noted in the crash reports, it appears to be a driver bug. That's good news if it's not a hardware problem because driver bugs can normally be resolved.

Switch over to the Intel IGP and see if the crashes go away. Then switch back to the 7970M CrossFire and see if they return.

If it still crashes on the IGP, then it's a driver other than the AMD product.

Alternatively, you can uninstall the AMD video drivers and use the Standard VGA driver to see if the crashing stops without being on the IGP. The display will not look nice or have Aero, but that's OK for diagnostics. You can most likely adjust the resolution to 1080p even with the Standard VGA driver.

If you still get the crashing without AMD drivers involved, then it's obviously a different driver. Do you have Killer wireless? If so, try a different driver. The Killer cards are awesome, but they have had some driver issues.

[Juscallmesteve]

Ill try the integrated gpu and see how it goes, as well as no i do not have the killer n 1103

[Mr. Fox]

Another thought, if it turns out to only crash with using the AMD discrete graphics. Are you using the AMD driver that is part of your system recovery media, or did you install a newer/different AMD driver? If not the one from the recovery, did you install different drivers on top of the old, or do a thorough removal with DriverSweeper and and CCleaner registry tool for a clean driver install?

[Juscallmesteve]

I am using 12.5 beta and no i didnt do a full thorough removal.
12.4 is the one that came with the system and i updated to 12.5 but it crashed many times on 12.4 and the crashes above are all with 12.5

[Mr. Fox]

Other M18x owners (including M18x R1 6990M CF owners) are experiencing BSOD problems with Catalyst 12.3 and 12.4. Not all, but some are. That might be the problem by installing 12.5 on top of an older version. AMD drivers have been notorious for having corruption issues when installed over the top of an existing driver. Some can find success with that randomly, but more often than not the installation is corrupt, CCC refuses to launch, or the old drivers remain in place and the new drivers never actually get fully installed. AMD GPU veterans (including me) consider a clean driver installation to be a standard best practice.

[sk3tch]

Over on the Sager/Clevo side the 2nd shipment of 7970Ms were delayed because they did not pass Sager's quality control (QC) tests. I guess the bottom line was that that some of the components on the cards were bad and led to premature failure during their tests. Not saying this is what is happening to you - but you could see if you're able to disable individual 7970Ms in your system to see if the problem continues or goes away. It may help when you eventually call Dell to get assistance. Save you some phone time...

Quoting my post from page 1 that was seemingly ignored. It may not be the cause - but it is something to keep in mind. Remember - an ENTIRE shipment of 7970Ms were sent back by Sager due to QC issues. So you never know...just troubleshoot with an open mind and exhaust all potential possibilities. It's the best way to do it...also don't forget to "dumb yourself down" - sometimes we work too hard to troubleshoot and overlook simple things.

[Juscallmesteve]

Ok ive been on the intel hd 4000 integrated GPU for about an hour now, it just crashed about 10 min ago.

I cant find the crash report, but the reason i know it crashed is because when i came back to my computer it said that my laptop has recovered from an unexpected shutdown.

WhoCrashed report:
On Wed 5/30/2012 7:16:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053012-18798-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F2B32F, 0xFFFFF880067A1280, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 5/30/2012 7:16:52 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x1687)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F2B32F, 0xFFFFF880067A1280, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

[Juscallmesteve]

I think i might just return this laptop instead of for a replacement but for a refund and just wait till the 680m is released because ive never had such problems with nvidia. Im not saying AMD is bad just saying i have never had problems from them.