Windows 7 x64 - Unknown BSOD Cause - Please Help

[rurounikamv]

Hello, I am hopeful that some of the gurus on these boards may be able to track down this mind-numbing issue that's causing these BSODs I'm having.

Some background, the issues have been persistent across several re-installs now. Each time has been after a full HD wipe, and different disk selected as the primary drive.

I have run my own tests on memory(memtest) without an errors occurring, and run it several times for long periods of time 20-30 hours again with no errors.

I have had the motherboard, all 3 drives, processor, gfx card, and all 4 sticks of memory tested in the shop, all purchased from memory express with their IPR warranty, all of the hardware came back clean without error. All of the hardware is approx. 1 year from the date of purchase.

I am running an install of Windows 7 Enterprise licensed from my job, I am an open resource developer and tend to do work well at home, which has been near impossible with the risk from them BSODs. We have tried several copies of the install on my home machine, my laptop and other desktops in the office but my desktop at home appears to be the only one affected by BSODs.

As I just came back from having all of the hardware tested, I performed a full clean rebuild and install without seeing any errors for a week. This weekend I received two BSOD's close in time to each other. Both have the same error signature as I received from the previous installs.

For Recap:
OS: Windows 7 Ent x64
Memory: Corsair Dominator 4x2gb
Mobo: GA-MA790FXT-UD5P Gigabyte
Drives: 2x 1.5TB Seagate 7200.11 (one currently not connected) , 1 x 1TB Seagate 7200.12 (primary)
GFX: Nvidia GTX 295
CPU: AMD Phenom II 955BE 3.2 Ghz
PSU: Zalaman 1000w - PSU is the only piece of hardware that was not tested.

Report From WhoCrashed:

[FONT=Segoe UI, Arial][SIZE=4][B]Analysis[/B]  [/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Crash dump  directory: C:\Windows\Minidump[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Crash  dumps are enabled on your computer.
[/COLOR][/SIZE][/FONT][/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Sat 8/7/2010 5:49:40 AM your computer  crashed[/B]
This was likely caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT]
Bugcheck code: 0x1E (0x0, 0x0, 0x0,  0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
Dump file:  C:\Windows\Minidump\080710-23649-01.dmp
[/COLOR][/SIZE][/FONT][FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]file path: C:\Windows\system32\ntoskrnl.exe
product:  [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel &  System
The crash took place in a standard Microsoft module. Your system  configuration may be incorrect, possibly the culprit is in another driver on  your system which cannot be identified at this time. 
[/COLOR][/SIZE][/FONT][FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Sat 8/7/2010 3:08:28 AM your  computer crashed[/B]
This was likely caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT]
Bugcheck code: 0x1E (0x0, 0x0, 0x0,  0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
Dump file:  C:\Windows\Minidump\080710-23306-01.dmp
[/COLOR][/SIZE][/FONT][FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]file path: C:\Windows\system32\ntoskrnl.exe
product:  [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel &  System
The crash took place in a standard Microsoft module. Your system  configuration may be incorrect, possibly the culprit is in another driver on  your system which cannot be identified at this time. [/COLOR][/SIZE][/FONT]

Minidumps and Windows 7 BSOD Tool and Perfmon report. Hopefully we can figure this thing out and thanks a lot to anyone willing to trudge through this stuff to help me.

 

[zigzag3143]

Hello, I am hopeful that some of the gurus on these boards may be able to track down this mind-numbing issue that's causing these BSODs I'm having.

Some background, the issues have been persistent across several re-installs now. Each time has been after a full HD wipe, and different disk selected as the primary drive.

I have run my own tests on memory(memtest) without an errors occurring, and run it several times for long periods of time 20-30 hours again with no errors.

I have had the motherboard, all 3 drives, processor, gfx card, and all 4 sticks of memory tested in the shop, all purchased from memory express with their IPR warranty, all of the hardware came back clean without error. All of the hardware is approx. 1 year from the date of purchase.

I am running an install of Windows 7 Enterprise licensed from my job, I am an open resource developer and tend to do work well at home, which has been near impossible with the risk from them BSODs. We have tried several copies of the install on my home machine, my laptop and other desktops in the office but my desktop at home appears to be the only one affected by BSODs.

As I just came back from having all of the hardware tested, I performed a full clean rebuild and install without seeing any errors for a week. This weekend I received two BSOD's close in time to each other. Both have the same error signature as I received from the previous installs.

For Recap:
OS: Windows 7 Ent x64
Memory: Corsair Dominator 4x2gb
Mobo: GA-MA790FXT-UD5P Gigabyte
Drives: 2x 1.5TB Seagate 7200.11 (one currently not connected) , 1 x 1TB Seagate 7200.12 (primary)
GFX: Nvidia GTX 295
CPU: AMD Phenom II 955BE 3.2 Ghz
PSU: Zalaman 1000w - PSU is the only piece of hardware that was not tested.

Report From WhoCrashed:

[FONT=Segoe UI, Arial][SIZE=4][B]Analysis[/B]  [/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Crash dump  directory: C:\Windows\Minidump[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Crash  dumps are enabled on your computer.
[/COLOR][/SIZE][/FONT][/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Sat 8/7/2010 5:49:40 AM your computer  crashed[/B]
This was likely caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT]
Bugcheck code: 0x1E (0x0, 0x0, 0x0,  0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
Dump file:  C:\Windows\Minidump\080710-23649-01.dmp
[/COLOR][/SIZE][/FONT][FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]file path: C:\Windows\system32\ntoskrnl.exe
product:  [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel &  System
The crash took place in a standard Microsoft module. Your system  configuration may be incorrect, possibly the culprit is in another driver on  your system which cannot be identified at this time. 
[/COLOR][/SIZE][/FONT][FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Sat 8/7/2010 3:08:28 AM your  computer crashed[/B]
This was likely caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT]
Bugcheck code: 0x1E (0x0, 0x0, 0x0,  0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
Dump file:  C:\Windows\Minidump\080710-23306-01.dmp
[/COLOR][/SIZE][/FONT][FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]file path: C:\Windows\system32\ntoskrnl.exe
product:  [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel &  System
The crash took place in a standard Microsoft module. Your system  configuration may be incorrect, possibly the culprit is in another driver on  your system which cannot be identified at this time. [/COLOR][/SIZE][/FONT]

Minidumps and Windows 7 BSOD Tool and Perfmon report. Hopefully we can figure this thing out and thanks a lot to anyone willing to trudge through this stuff to help me.

\


These two crashes were caused by your Realtek driver (rt64win7.sys). Hardware BSOD's are hard to diagnose but this driver appeared in both.

Unfortunately Who crashed and Blue screen view dont do a really good job with this type of crash.

I would (of course) download and install a fresh copy.

Also I would
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Let us know the results from the report at the end.

Ken

 

[rurounikamv]

Hello Ken thanks for looking!

I went to the Realtek site and grabbed the latest Realtek NIC 10/100/1000m PCIe driver 7.023 Dated:2010/7/21 hopefully this was the correct driver and solves the issue that plagued me.

I ran the SFC scan before and after the install both had the same result:

Windows Resource Protection did not find any integrity violations.