Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Video card memory vs system memory conflict?


  • Please log in to reply
12 replies to this topic

#1 Allensfilm

Allensfilm

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:06:39 AM

Posted 04 June 2011 - 11:28 PM

I installed the Nvidia 9500GT got the Blue screen of death after many headaches I took it back and got the Nvidia GT520 still got BSOD I have done a complete hardware diagnostic test on every piece of hardware on the computer and everything checks out good. I have the latest Video card and mother board drivers installed and keep getting the blue screen of death on random things mostly DRIVER_IRQL_NOT_LESS_OR EQUAL
a theory I have is maybe the Video card memory speed is conflicting with the Video card memory runs faster then the System memory and I've read that Vista has problems with ram that runs at different speeds. could that be the issue?
Just a quick update I just uninstalled the Nvidia HD Audio Driver I have a feeling it was conflicting with the Realtek High Definition Audio Driver...
We will see...
Any help or info from you guys will be helpful, thanks

Here are my system specs:
System Information
Saturday, June 04, 2011 9:13:24 PM
-----------------------------------------------------------------------------
Model Information
-----------------------------------------------------------------------------
Model Name m8300f
Product Number GX611AA-ABA
Software Build 81NAv3PrA1
Serial Number XXXXXXXXXX
-----------------------------------------------------------------------------
System Information
-----------------------------------------------------------------------------
Manufacturer HP-Pavilion
Total Number of Logical CPUs 2
Total Physical Memory 3.00 GB
Total Number of Optical Drives 2
Total Number of Hard Drives 2
Total Number of Video Cards 1
Total Number of Memory Modules 4
Total Number of DIMM slots 4
-----------------------------------------------------------------------------
Motherboard
-----------------------------------------------------------------------------

System Board
Chipset nVidia MCP61

Base Board
Manufacturer ECS
Product Nettle2

BIOS
Vendor Phoenix Technologies, LTD
Release Date 10/03/2007
BIOS Version String 5.20
ROM Size 512.00 kB

AMD Athlon™ 64 X2 Dual Core Processor 6000+ CPU:0
Specification AMD Athlon™ 64 X2 Dual Core Processor 6000+
Size 128.00 kB
Size 1.00 MB

AMD Athlon™ 64 X2 Dual Core Processor 6000+ CPU:1
Specification AMD Athlon™ 64 X2 Dual Core Processor 6000+
Size 128.00 kB
Size 1.00 MB
-----------------------------------------------------------------------------
Memory
-----------------------------------------------------------------------------

System Memory
Total Physical Memory 3.00 GB
Free Physical Memory 1.16 GB

512 MB DDR2-SDRAM (PC2-5300 / 667 MHz)
Memory Size 512.00 MB
Memory Type DDR2-SDRAM (PC2-5300 / 667 MHz)
Memory Manufacturer Hyundai Electronics
Memory Manufacture Date Week 35, Year 2007
Memory Part Number HYMP564U64CP8-Y5
Memory Revision Code 4241

512 MB DDR2-SDRAM (PC2-5300 / 667 MHz)
Memory Size 512.00 MB
Memory Type DDR2-SDRAM (PC2-5300 / 667 MHz)
Memory Manufacturer Hyundai Electronics
Memory Manufacture Date Week 35, Year 2007
Memory Part Number HYMP564U64CP8-Y5
Memory Revision Code 4241

1024 MB DDR2-SDRAM (PC2-5300 / 667 MHz)
Memory Size 1.00 GB
Memory Type DDR2-SDRAM (PC2-5300 / 667 MHz)
Memory Manufacturer Hyundai Electronics
Memory Manufacture Date Week 34, Year 2007
Memory Part Number HYMP112U64CP8-Y5
Memory Revision Code 4141

1024 MB DDR2-SDRAM (PC2-5300 / 667 MHz)
Memory Size 1.00 GB
Memory Type DDR2-SDRAM (PC2-5300 / 667 MHz)
Memory Manufacturer Hyundai Electronics
Memory Manufacture Date Week 34, Year 2007
Memory Part Number HYMP112U64CP8-Y5
Memory Revision Code 4141
-----------------------------------------------------------------------------
Local Disk
-----------------------------------------------------------------------------

Hitachi HDT725032VLA SCSI Disk Device
Model Number Hitachi HDT725032VLA
Firmware Revision V54O
Total Capacity 298.09 GB
Driver c:\windows\system32\drivers\disk.sys
Driver Version 6.0.6002.18005, 6-21-2006

Hitachi HDT725032VLA SCSI Disk Device
Model Number Hitachi HDT725032VLA
Firmware Revision V54O
Total Capacity 298.09 GB
Driver c:\windows\system32\drivers\disk.sys
Driver Version 6.0.6002.18005, 6-21-2006

HP - C:
Drive Letter C
Volume Name HP
Volume Serial Number 2630-AAC3
File System NTFS
Volume Capacity 288.57 GB
Volume Free Space 119.39 GB
Volume Used Space 169.18 GB

FACTORY_IMAGE - D:
Drive Letter D
Volume Name FACTORY_IMAGE
Volume Serial Number 8874-071C
File System NTFS
Volume Capacity 9.51 GB
Volume Free Space 1.29 GB
Volume Used Space 8.22 GB

Stuff - E:
Drive Letter E
Volume Name Stuff
Volume Serial Number 2EE2-3822
File System NTFS
Volume Capacity 298.09 GB
Volume Free Space 206.03 GB
Volume Used Space 92.06 GB
-----------------------------------------------------------------------------
CD-ROM Drive
-----------------------------------------------------------------------------

TSSTcorp CDDVDW SH-S203N SCSI CdRom Device
Model Number TSSTcorpCDDVDW SH-S203N
Serial Number SH-S203NFirmware
Firmware Revision SB01
Drive Letter F
Readable Media CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL
Writable Media CD-R, CD-RW, DVD-RAM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL
Write Strategy TAO, SAO, RAW, RAW-MS
Driver c:\windows\system32\drivers\cdrom.sys
Driver Version 6.0.6002.18005, 6-21-2006

TSSTcorp CDDVDW SH-S203N SCSI CdRom Device
Model Number TSSTcorpCDDVDW SH-S203N
Serial Number SH-S203NFirmware
Firmware Revision SB01
Drive Letter L
Readable Media CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL
Writable Media CD-R, CD-RW, DVD-RAM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL
Write Strategy TAO, SAO, RAW, RAW-MS
Driver c:\windows\system32\drivers\cdrom.sys
Driver Version 6.0.6002.18005, 6-21-2006
-----------------------------------------------------------------------------
Display
-----------------------------------------------------------------------------

M220VA (Generic PnP Monitor)
Mode 1600 x 900 (32-bit) (60 Hz)
Signal Type Analog
-----------------------------------------------------------------------------
Video Card
-----------------------------------------------------------------------------

NVIDIA GeForce GT 520
Manufacturer NVIDIA
Driver c:\windows\system32\drivers\nvlddmkm.sys
Driver Version 8.17.12.7533, 5-20-2011
-----------------------------------------------------------------------------
Modem
-----------------------------------------------------------------------------

PCI Soft Data Fax Modem with SmartCP
Model PCI Soft Data Fax Modem with SmartCP
Driver c:\windows\system32\drivers\modem.sys
Driver Version 7.74.0.0, 5-6-2008
-----------------------------------------------------------------------------
Sound Card
-----------------------------------------------------------------------------

Realtek High Definition Audio
Manufacturer Realtek
Driver c:\windows\system32\drivers\rtkvhda.sys
Driver Version 6.0.1.5789, 2-11-2009

NVIDIA High Definition Audio
Manufacturer NVIDIA
Driver c:\windows\system32\drivers\nvhda32v.sys
Driver Version 1.2.23.3, 5-10-2011
-----------------------------------------------------------------------------
Network Card
-----------------------------------------------------------------------------

NVIDIA nForce 10/100 Mbps Ethernet
MAC Address 00:1b:b9:fd:0a:04
IP Address 192.168.0.10
Gateway IP Address 192.168.0.1
Current Speed 100.00 Mbps
Driver c:\windows\system32\drivers\nvmfdx32.sys
Driver Version 67.8.9.0, 8-1-2008
-----------------------------------------------------------------------------
Printers
-----------------------------------------------------------------------------

Product Version: 5.00.4589.14

Edited by Allensfilm, 04 June 2011 - 11:30 PM.


BC AdBot (Login to Remove)

 


#2 Allensfilm

Allensfilm
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:06:39 AM

Posted 05 June 2011 - 02:28 AM

Just tried this:
http://www.evga.com/forums/tm.aspx?m=586183&mpage=1
Hopefully this will fix the BSOD issue,
I'm sick of getting the BSOD on my system when nothing is wrong with the hardware. I work to hard to keep it running like new, don't want something simple to take it down. but this has been going on for weeks hopefully this will fix.
I'll know in the morning.

This is also interesting:
http://forums.nvidia.com/index.php?showtopic=190995

Edited by Allensfilm, 05 June 2011 - 02:35 AM.


#3 Allensfilm

Allensfilm
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:06:39 AM

Posted 05 June 2011 - 11:34 AM

Still having problems.... 4 BSOD screens on me on 4 boots in a row.... This is driving me crazy...
Here are is what it gave me after the latest BSOD.... Seems stable now... but...

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 00008885
BCP2: 83771BF0
BCP3: 837720F8
BCP4: 00000500
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\WINDOWS\Minidump\Mini060511-02.dmp
C:\Users\Allen\AppData\Local\Temp\WER-47689-0.sysdata.xml
C:\Users\Allen\AppData\Local\Temp\WERB29B.tmp.version.txt

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,293 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:39 AM

Posted 05 June 2011 - 09:01 PM

Let's try this.

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html.

Double-click BlueScreenView.exe file.

When scanning is done, click Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis

#5 Allensfilm

Allensfilm
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:06:39 AM

Posted 06 June 2011 - 01:05 AM

Thanks Louis,
Before you posted, I ran fixcleaner http://softwareindustryreport.com/report/fix-cleaner.html (it found and cleaned a bunch of registry junk) the program cleans junk files. It viewed all the the dmp files as junk and cleaned them out, that was hours ago and I've only had one BSOD sense then.
Here it is:

==================================================
Dump File : Mini060511-01.dmp
Crash Time : 6/5/2011 9:23:19 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x81a4bd18
Parameter 3 : 0xaf1b2278
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+770c
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Crash Address : ntoskrnl.exe+18d18
Stack Address 1 : ntoskrnl.exe+237199
Stack Address 2 : ntoskrnl.exe+4ac7a
Stack Address 3 : ntoskrnl.exe+49625
Computer Name :
Full Path : C:\Windows\Minidump\Mini060511-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 159,707
==================================================

The others were things like
MEMORY_MANAGEMENT
PFN_LIST_CORRUPT
nvmfdx32.sys
CLASSPNP.SYS
PAGE_FAULT_IN_NONPAGED_AREA,

Took pics of those BSODs with my camera sorry the dmp files got cleaned out...
In the morning if there are more BSODs I'll post the bluescreen view logs.
It seems I get these BSODs mostly every morning for the last few months before the computer warms up then randomly throught the day. don't know why that is... I'll keep you posted.
Today after cleaning the registry, I played Batman Arkham with the graphic settings nearly maxed for a few hours with no BSOD problems at all.

Edited by Allensfilm, 06 June 2011 - 01:06 AM.


#6 hamluis

hamluis

    Moderator


  • Moderator
  • 56,293 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:39 AM

Posted 06 June 2011 - 09:13 AM

Bleeping Computer DOES NOT recommend the use of registry cleaners/optimizers for several reasons:
  • Registry cleaners are extremely powerful applications that can damage the registry by using aggressive cleaning routines and cause your computer to become unbootable.

    The Windows registry is a central repository (database) for storing configuration data, user settings and machine-dependent settings, and options for the operating system. It contains information and settings for all hardware, software, users, and preferences. Whenever a user makes changes to settings, file associations, system policies, or installed software, the changes are reflected and stored in this repository. The registry is a crucial component because it is where Windows "remembers" all this information, how it works together, how Windows boots the system and what files it uses when it does. The registry is also a vulnerable subsystem, in that relatively small changes done incorrectly can render the system inoperable. For a more detailed explanation, read Understanding The Registry.
  • Not all registry cleaners are created equal. There are a number of them available but they do not all work entirely the same way. Each vendor uses different criteria as to what constitutes a "bad entry". One cleaner may find entries on your system that will not cause problems when removed, another may not find the same entries, and still another may want to remove entries required for a program to work.
  • Not all registry cleaners create a backup of the registry before making changes. If the changes prevent the system from booting up, then there is no backup available to restore it in order to regain functionality. A backup of the registry is essential BEFORE making any changes to the registry.
  • Improperly removing registry entries can hamper malware disinfection and make the removal process more difficult if your computer becomes infected. For example, removing malware related registry entries before the infection is properly identified can contribute to system instability and even make the malware undetectable to removal tools.
  • The usefulness of cleaning the registry is highly overrated and can be dangerous. In most cases, using a cleaner to remove obsolete, invalid, and erroneous entries does not affect system performance but it can result in "unpredictable results".

Unless you have a particular problem that requires a registry edit to correct it, I would suggest you leave the registry alone. Using registry cleaning tools unnecessarily or incorrectly could lead to disastrous effects on your operating system such as preventing it from ever starting again. For routine use, the benefits to your computer are negligible while the potential risks are great.
As for your topic title...I don't see where it would be possibly for system RAM...to "conflict" with video RAM. Two different functions, two different animals, IMO.

Please...follow the directions I provided for posting the entire BSOD.txt file. More data provides a better picture of what's going on with your system and for how long.

Louis

Edited by hamluis, 06 June 2011 - 09:15 AM.


#7 Allensfilm

Allensfilm
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:06:39 AM

Posted 06 June 2011 - 10:38 AM

Thanks for the tip, here are the two that I got this morning:
==================================================
Dump File : Mini060611-02.dmp
Crash Time : 6/6/2011 8:18:25 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x81beedec
Parameter 3 : 0x8c7fb724
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+40c0
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Crash Address : ntoskrnl.exe+1e0dec
Stack Address 1 : ntoskrnl.exe+89ed1
Stack Address 2 : ntoskrnl.exe+1a742b
Stack Address 3 : ntoskrnl.exe+1f047
Computer Name :
Full Path : C:\Windows\Minidump\Mini060611-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 159,707
==================================================

==================================================
Dump File : Mini060611-01.dmp
Crash Time : 6/6/2011 8:16:30 AM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 0x00000099
Parameter 2 : 0x0006b522
Parameter 3 : 0x00000000
Parameter 4 : 0x0003e913
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+cdb3f
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Crash Address : ntoskrnl.exe+cdb3f
Stack Address 1 : ntoskrnl.exe+96b6d
Stack Address 2 : ntoskrnl.exe+635c6
Stack Address 3 : ntoskrnl.exe+2cf16c
Computer Name :
Full Path : C:\Windows\Minidump\Mini060611-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 159,707
==================================================

Also ran more hardware tests, everything passed...

Edited by Allensfilm, 06 June 2011 - 10:46 AM.


#8 Allensfilm

Allensfilm
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:06:39 AM

Posted 06 June 2011 - 09:54 PM

Here is the latest crash from about 15 minutes ago.
Don't know what's causing it... it's so random...
==================================================
Dump File : Mini060611-03.dmp
Crash Time : 6/6/2011 7:40:18 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00000403
Parameter 2 : 0xc0028f70
Parameter 3 : 0x7dd6a867
Parameter 4 : 0xc0012608
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+b6ba8
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Crash Address : ntoskrnl.exe+b6ba8
Stack Address 1 : ntoskrnl.exe+b671c
Stack Address 2 : ntoskrnl.exe+855b3
Stack Address 3 : ntoskrnl.exe+4ac7a
Computer Name :
Full Path : C:\Windows\Minidump\Mini060611-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 159,707
==================================================

#9 Allensfilm

Allensfilm
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:06:39 AM

Posted 06 June 2011 - 10:12 PM

Minutes after that last post I got another BSOD out of nowhere it's strange how it always happens when doing nothing that is demanding of the system.
==================================================
Dump File : Mini060611-04.dmp
Crash Time : 6/6/2011 7:58:37 PM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 0x0000008d
Parameter 2 : 0x0002488f
Parameter 3 : 0x00000020
Parameter 4 : 0xc002df61
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+cdb3f
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Crash Address : ntoskrnl.exe+cdb3f
Stack Address 1 : ntoskrnl.exe+5bd85
Stack Address 2 : ntoskrnl.exe+15936e
Stack Address 3 : ntoskrnl.exe+1d5f7a
Computer Name :
Full Path : C:\Windows\Minidump\Mini060611-04.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 159,707
==================================================

#10 Allensfilm

Allensfilm
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:06:39 AM

Posted 06 June 2011 - 11:12 PM

And another.... :blink:
==================================================
Dump File : Mini060611-05.dmp
Crash Time : 6/6/2011 8:55:25 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x8192796c
Parameter 2 : 0x0000001b
Parameter 3 : 0x00000000
Parameter 4 : 0x81ae4e18
Caused By Driver : hal.dll
Caused By Address : hal.dll+7468
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+4dfd9
Stack Address 1 : ntkrnlpa.exe+abe18
Stack Address 2 : ntkrnlpa.exe+47f0b
Stack Address 3 : win32k.sys+c8bbc
Computer Name :
Full Path : C:\Windows\Minidump\Mini060611-05.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 150,528
==================================================

#11 Allensfilm

Allensfilm
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:06:39 AM

Posted 06 June 2011 - 11:32 PM

Just found something strange in device manager called ISATAP adaptor so I disabled them sense they were not working anyway. I'm pretty sure these BSOD errors I've been getting are related to some kind of driver issue. The ISATAP adapters all had Exclamation points next to them so I did some research and found they are not really needed and appear in windows device manager for no reason.

Wish I had titled this thread differently it was just one of my many theory's at the time I posted but I've learned that's not the problem...
I get my hopes up with each little thing I've tried, the BSOD errors are not as frequent so maybe I'm moving in the right direction.

Edited by Allensfilm, 07 June 2011 - 01:02 AM.


#12 Allensfilm

Allensfilm
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:06:39 AM

Posted 07 June 2011 - 11:33 AM

It continues... Here are 2 more from this morning:
==================================================
Dump File : Mini060711-02.dmp
Crash Time : 6/7/2011 9:25:47 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x00336e33
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x81a96c88
Caused By Driver : hal.dll
Caused By Address : hal.dll+40c0
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+4dfd9
Stack Address 1 : ntkrnlpa.exe+95c88
Stack Address 2 : ntkrnlpa.exe+95eaf
Stack Address 3 : ntkrnlpa.exe+80ad1
Computer Name :
Full Path : C:\Windows\Minidump\Mini060711-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 150,480
==================================================

==================================================
Dump File : Mini060711-01.dmp
Crash Time : 6/7/2011 9:18:17 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8f477eac
Parameter 3 : 0x97cd5b20
Parameter 4 : 0x97cd581c
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+3aeac
File Description : DirectX Graphics Kernel
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 7.0.6002.18107 (vistasp2_gdr_win7ip_dgt(wmbla).090924-1550)
Processor : 32-bit
Crash Address : dxgkrnl.sys+3aeac
Stack Address 1 : dxgkrnl.sys+3b197
Stack Address 2 : dxgkrnl.sys+3a24b
Stack Address 3 : dxgkrnl.sys+39d32
Computer Name :
Full Path : C:\Windows\Minidump\Mini060711-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 146,400
==================================================

#13 Allensfilm

Allensfilm
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:06:39 AM

Posted 08 June 2011 - 12:04 AM

I'm biting the bullet and sense I know it's not the hardware I'm doing a COMPLETE SYSTEM recovery Back to the factory pre sets... this is going to SUCK... The only thing I can think of is some kind of undetectable VIRUS got into the system somehow...
The ONE THING that will piss me off is if I go through all this and STILL get the BSOD... At least then I'll be sure it was some kind of hidden hardware issue...




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users