Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSoD, multiple reasons - Windows 7 x64


  • Please log in to reply

#1
AdrienM

AdrienM

    New Member

  • Member
  • Pip
  • 2 posts
Hello!

I built a new computer 5 months ago and I have BSoD since the first day. About 2 weeks ago I did a fresh reinstallation of Windows 7 Ultimate 64bit but it's still crashing, even with the most updated drivers and bios. So, I decided to collect my Crash Dumps. Here are the analysis by WhoCrashed :

On Sun 21/02/2010 22:03:29 your computer crashed
This was likely caused by the following module: tcpip.sys
Bugcheck code: 0xD1 (0x88, 0x2, 0x0, 0xFFFFF88001A7D30B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\022110-14944-01.dmp
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Fri 19/02/2010 18:05:02 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF960000FBEC7)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\021910-15022-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Wed 17/02/2010 18:11:10 your computer crashed
This was likely caused by the following module: wdf01000.sys
Bugcheck code: 0xD1 (0x18, 0x2, 0x0, 0xFFFFF88000F2491B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\021710-19531-01.dmp
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Wed 17/02/2010 16:02:26 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002837B5C, 0xFFFFF880031D8F98, 0xFFFFF880031D87F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\021710-16723-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Mon 15/02/2010 00:33:08 your computer crashed
This was likely caused by the following module: iastor.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880012B57D8, 0xFFFFF880035719B8, 0xFFFFF88003571210)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\021510-22776-01.dmp
file path: C:\Windows\system32\drivers\iastor.sys
product: Intel Matrix Storage Manager driver
company: Intel Corporation
description: Intel Matrix Storage Manager driver - x64



On Sun 14/02/2010 20:49:59 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x50 (0xFFFFF1000C4C94F0, 0x1, 0xFFFFF960000E99D3, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\021410-14523-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Sat 13/02/2010 17:21:04 your computer crashed
This was likely caused by the following module: iastor.sys
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF8800124AE27)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\021310-16005-01.dmp
file path: C:\Windows\system32\drivers\iastor.sys
product: Intel Matrix Storage Manager driver
company: Intel Corporation
description: Intel Matrix Storage Manager driver - x64



On Sat 13/02/2010 15:45:31 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF800028C2301)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\021310-15428-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.


I already googled every keywords about my problem but never found a solution.

Here is my system :
Windows 7 Ultimate x64
Asus P5Q Deluxe
Intel Core 2 Duo E8500
Sapphire Radeon HD 4870 1GB GDDR5 Vapor-X
Kingston HyperX 4 Go (2*2) PC6400 CL4 - KHX6400D2LLK2/4G
2*SAMSUNG HD501LJ RAID 0
Antec Sonata III 500

How I can avoid those recurrent blue screens? What is my computer suffering from?

Thanks in advance for your precious help :)

Edited by AdrienM, 22 February 2010 - 04:51 PM.

  • 0

Advertisements


#2
AdrienM

AdrienM

    New Member

  • Topic Starter
  • Member
  • Pip
  • 2 posts
After having noticed BSoDs come up only after sleep mode, I found the solution :)

The ratio DRAM:FSB must be 1:1!

Thank you xaris33 (http://www.sevenforu...er-sleep-3.html)
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP