Windows 7 Build 7600 Blue Screen help, Minidump included

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

hawtbox

Thread Starter
Joined
Jan 12, 2011
Messages
1
Hello,

This is my first time posting, I will try to be as comprehensive as possible. I have recently built my own machine using all parts from Newegg and I am having a problem with blue screens.

The build is as follows:

Antec Three Hundred Case
AMD Phenom II X4 965 CPU
650W Corsair PSU
4g (2+2) G.Skill Ripjaw Ram
M4A79XTD Evo Asus Motherboard
640gb Western Digital Cavalier Black HD
Sapphire Toxic Radeon HD5850 2GB video card

Peripherals:

Microsoft Wireless Comfort Keyboard 4000
Kensington USB Mouse
Cyber Acoustics Headset (not usb)
D-Link USB Network Connector

After putting all of the components together, I ran the windows 7 .iso to install windows. As soon as that was finished I ran the cd's that came with the video card and motherboard to update the drivers. I have fully updated Windows 7 to build 7600, downloading everything but the language packs. The programs I have installed are as follows:

Microsoft Office 2010 (only powerpoint, excel, word)
Adobe CS5 Master Suite
World of Warcraft
Fraps
Ventrilo
7-zip
WhoCrashed
Firefox

Performance:

Everything runs beautifully. The first blue screen I received when randomly surfing the internet, the next several occurred overnight while I was sleeping but letting World of Warcraft run. Several have happened when opening Firefox and trying to scroll up and down using mousewheel.

What have I done?:

Not much. I have gone into Msconfig and unchecked all startup programs and still bluescreened. I have googled a couple of the errors but didnt really know what they were talking about. Some people suggested it is necessary to update something from Asus, other threads suggest upping the northbridge voltage, the list goes on and on.

Here is the WhoCrashed Log:

[FONT=Segoe UI, Arial]On Wed 1/12/2011 8:57:07 AM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\011211-24835-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFCE802EE752A0, 0x0, 0xFFFFF80002DA081D, 0x7)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]


[FONT=Segoe UI, Arial]On Wed 1/12/2011 8:57:07 AM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\memory.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFCE802EE752A0, 0x0, 0xFFFFF80002DA081D, 0x7)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
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.
[/FONT]


[FONT=Segoe UI, Arial]On Wed 1/12/2011 3:32:35 AM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\011111-17425-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFA80504985C0, 0x1, 0xFFFFF88000FB9B00, 0x5)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]


[FONT=Segoe UI, Arial]On Tue 1/11/2011 9:49:19 AM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\011111-12261-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0xF1C7C)
Bugcheck code: 0xD1 (0xFFFFF8800133DC7C, 0x2, 0x8, 0xFFFFF8800133DC7C)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT File System Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
[/FONT]


[FONT=Segoe UI, Arial]On Tue 1/11/2011 9:23:13 AM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\011111-12620-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x70710)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 which cannot be identified at this time.
[/FONT]


[FONT=Segoe UI, Arial]On Mon 1/10/2011 6:22:47 PM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\011011-11232-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]rdbss.sys[/FONT] (rdbss+0x11782)
Bugcheck code: 0x27 (0xBAAD0073, 0xFFFFF8800465A9A8, 0xFFFFF8800465A210, 0x0)
Error: [FONT=Segoe UI, Arial]RDR_FILE_SYSTEM[/FONT]
file path: C:\Windows\system32\drivers\rdbss.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Redirected Drive Buffering SubSystem Driver
Bug check description: This indicates that a problem occurred in the SMB redirector 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 which cannot be identified at this time.
[/FONT]


[FONT=Segoe UI, Arial]On Mon 1/10/2011 6:01:13 PM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\011011-12261-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x70740)
Bugcheck code: 0x109 (0xA3A039D89570A5D8, 0xB3B7465EE7ED77CE, 0xFFFFF80002ABC140, 0x1)
Error: [FONT=Segoe UI, Arial]CRITICAL_STRUCTURE_CORRUPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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.
[/FONT]


[FONT=Segoe UI, Arial]On Mon 1/10/2011 5:58:03 PM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\011011-12901-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x70740)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000053C78, 0x89A00001166B8847, 0xFFFFFA8008FA3FC0)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]


[FONT=Segoe UI, Arial]On Fri 1/7/2011 6:40:57 PM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\010711-15490-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x70740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002AACD18, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 which cannot be identified at this time.
[/FONT]


[FONT=Segoe UI, Arial]On Fri 1/7/2011 6:09:50 PM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\010711-15834-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x70740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A96D18, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 which cannot be identified at this time.
[/FONT]


[FONT=Segoe UI, Arial]On Fri 1/7/2011 5:39:17 PM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\010711-17503-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF880079BB128, 0x0, 0xFFFFF80002DA02CB, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]


[FONT=Segoe UI, Arial]On Fri 1/7/2011 5:33:50 PM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\010711-17830-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x70740)
Bugcheck code: 0x1A (0x8886, 0xFFFFFA80035A02D0, 0xFFFFFA80035A6300, 0x205)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]


[FONT=Segoe UI, Arial]On Fri 1/7/2011 10:22:01 AM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\010711-15678-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x70740)
Bugcheck code: 0x109 (0xA3A039D8968A5B4B, 0xB3B7465EE9072D51, 0xFFFFF80002824268, 0x1)
Error: [FONT=Segoe UI, Arial]CRITICAL_STRUCTURE_CORRUPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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.
[/FONT]


Minidump: (See Attachment Below)
 

Attachments

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Staff online

Top