Quantcast
Channel: Tech Support Guy - Windows 7
Viewing all articles
Browse latest Browse all 6058

Windows 7 various BSODs

$
0
0
Hi there,

I am having BSOD's intermittently of various sorts. I have done a lot of research into these issues and unfortunately none of the solutions are working. This may be because of my system configuration:

Machine: Apple Inc. - MacBookPro8,2
Operating System: Microsoft Windows 7 Home Premium (64-bit) SP1
RAM: 4GB
Processor: Intel(R) Core(TM) i7-2820QM CPU @ 2.30GHz
Motherboard: Apple Inc. - Mac-94245A3940C91C80
Video Card: AMD Radeon 6750M
Monitor: Color LCD
Hard Disk: ST750LX003-1AC154 ATA Device (750.0 GB)
Network Card: Broadcom 802.11n Network Adapter

I am using a 2011 MacBook Pro to run Windows as a primary partition. I am not sure if this is a incompatibility issue or just regular windows issue.

So far I have done:
Memory test 6 passes 0 errors
Reseated Memory
atikmdag.sys fix (related to some BSOD's that I had before related to this file, I don't think its truly fixed but haven't had it nearly as often)
updated drivers
Scanned for malware

Here are the most recent WhoCrashed reports:
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 8/25/2013 2:16:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082413-17628-01.dmp
This was probably caused by the following module: cng.sys (0xFFFFF880014DE644)
Bugcheck code: 0x50 (0xFFFFF8A008578000, 0x0, 0xFFFFF880014DE644, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 8/25/2013 2:16:58 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cng.sys (cng!SslImportKey+0x2A04)
Bugcheck code: 0x50 (0xFFFFF8A008578000, 0x0, 0xFFFFF880014DE644, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 8/25/2013 12:15:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082413-12963-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20E26)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880045BAE26, 0xFFFFF880061C1568, 0xFFFFF880061C0DC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 8/24/2013 10:32:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082413-14742-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20E1D)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880044D5E1D, 0xFFFFF88006A79568, 0xFFFFF88006A78DC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 8/24/2013 10:13:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082413-12058-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20E26)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88005368E26, 0xFFFFF88006870568, 0xFFFFF8800686FDC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 8/24/2013 7:28:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082413-9999-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20E1D)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800533EE1D, 0xFFFFF88006872568, 0xFFFFF88006871DC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 8/24/2013 6:44:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082313-12823-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008F48098, 0xFFFFF88008F478F0, 0xFFFFF80002CEB3EF)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 that cannot be identified at this time.



On Sat 8/24/2013 4:03:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082313-14398-01.dmp
This was probably caused by the following module: ci.dll (0xFFFFF88000D89AC4)
Bugcheck code: 0x50 (0xFFFFF88004226000, 0x0, 0xFFFFF88000D89AC4, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ci.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Code Integrity Module
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 8/24/2013 3:59:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082313-14414-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20EC8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003F22EC8, 0xFFFFF88002137568, 0xFFFFF88002136DC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 8/23/2013 9:52:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082313-11403-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x45BA0A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004D4DA0A, 0xFFFFF880069B2F88, 0xFFFFF880069B27E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Fri 8/23/2013 2:10:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082213-13026-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C5FD23, 0xFFFFF88008BE1910, 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 that cannot be identified at this time.



On Thu 8/22/2013 5:46:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082213-13946-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 that cannot be identified at this time.



On Wed 8/21/2013 6:53:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082113-13634-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x34 (0x55F, 0xFFFFFFFFC0000420, 0x0, 0x0)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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 that cannot be identified at this time.



On Wed 8/21/2013 6:40:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082113-12152-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x45BA0A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004C69A0A, 0xFFFFF88006B60870, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode 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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_SERVICE_EXCEPTION



On Wed 8/21/2013 4:57:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082013-13384-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800971A098, 0xFFFFF880097198F0, 0xFFFFF80002CDD3EF)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 that cannot be identified at this time.


Please I would seriously appreciate any help, this is driving me nuts, and I am going to start school this week and need a computer that functions. Apple has really let me down on their OS X developments, I can't even buy a proper boot disk from them and Lion just looks awful.

They are absolutely 0 help even though my computer is under warranty and expect me to buy a boot disk from a 3rd party so I would really appreciate if any help did not include mention of going back to OS X as Windows should work properly.

-Andrew

Viewing all articles
Browse latest Browse all 6058

Trending Articles