Pages: 1 … 3 4 5 6 7 8

 

2010-04-26 08:00:17
Bevo
Nah
+718|6779|Austin, Texas
Well, it seems that was not the cause.

Another bluescreen this morning... i'll find the report.
edit: make that two
edit: make that six

sigh

Code:

==================================================
Dump File         : 042610-19671-01.dmp
Crash Time        : 4/26/2010 10:17:58 AM
Bug Check String  : NTFS_FILE_SYSTEM
Bug Check Code    : 0x00000024
Parameter 1       : 00000000`001904fb
Parameter 2       : fffff880`03746718
Parameter 3       : fffff880`03745f70
Parameter 4       : fffff880`012eac55
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+acc55
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\042610-19671-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 042610-20748-01.dmp
Crash Time        : 4/26/2010 10:15:41 AM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`0000888a
Parameter 2       : fffff8a0`021142b8
Parameter 3       : fffff680`000e3a23
Parameter 4       : fffffa80`01f2b1c0
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\042610-20748-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 042610-19952-01.dmp
Crash Time        : 4/26/2010 10:12:30 AM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00000403
Parameter 2       : fffff680`00069f58
Parameter 3       : f7500000`8bef1867
Parameter 4       : fffff680`00067f7a
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\042610-19952-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 042610-24866-01.dmp
Crash Time        : 4/26/2010 10:10:10 AM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 00000000`00000099
Parameter 2       : 00000000`00089845
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00089945
Caused By Driver  : dxgmms1.sys
Caused By Address : dxgmms1.sys+5ee3
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\042610-24866-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 042610-18829-01.dmp
Crash Time        : 4/26/2010 10:02:41 AM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff880`01085fa9
Parameter 3       : fffff880`03390970
Parameter 4       : 00000000`00000000
Caused By Driver  : fltmgr.sys
Caused By Address : fltmgr.sys+4fa9
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\042610-18829-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 042610-19999-01.dmp
Crash Time        : 4/26/2010 10:00:10 AM
Bug Check String  : ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug Check Code    : 0x000000fc
Parameter 1       : fffff880`064f1b72
Parameter 2       : 80000001`2760f963
Parameter 3       : fffff880`02af04a0
Parameter 4       : 00000000`00000002
Caused By Driver  : RTKVHD64.sys
Caused By Address : RTKVHD64.sys+e7b72
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\042610-19999-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================
edit: I also get some random error messages about failure to write memory this or memory blah blah that.

Last edited by Bevo (2010-04-26 08:19:48)

2010-04-26 08:17:22
SonderKommando
Eat, Lift, Grow, Repeat....
+564|6918|The darkside of Denver

Bevo wrote:

Well, it seems that was not the cause.

Another bluescreen this morning... i'll find the report.
edit: make that two

sigh

Code:

==================================================
Dump File         : 042610-18829-01.dmp
Crash Time        : 4/26/2010 10:02:41 AM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff880`01085fa9
Parameter 3       : fffff880`03390970
Parameter 4       : 00000000`00000000
Caused By Driver  : fltmgr.sys
Caused By Address : fltmgr.sys+4fa9
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\042610-18829-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 042610-19999-01.dmp
Crash Time        : 4/26/2010 10:00:10 AM
Bug Check String  : ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug Check Code    : 0x000000fc
Parameter 1       : fffff880`064f1b72
Parameter 2       : 80000001`2760f963
Parameter 3       : fffff880`02af04a0
Parameter 4       : 00000000`00000002
Caused By Driver  : RTKVHD64.sys
Caused By Address : RTKVHD64.sys+e7b72
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\042610-19999-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================
edit: I also get some random error messages about failure to write memory this or memory blah blah that.
Bevo.. RMA both the board and teh RAM. I promise that it will solve the issue.  Just email both companies with serial numbers and tell them you have narrowed the failures down to X device with extensive testing such as process of elimination and memtesting. Its prob your board but it can eb the ram as well...
2010-04-26 08:21:52
Bevo
Nah
+718|6779|Austin, Texas
I was going to test out my old RAM next, but yes RMAing the mobo and RAM is pretty close to next on the list. I even grabbed a box from home to get ready to mail em.
2010-04-26 08:26:27
SonderKommando
Eat, Lift, Grow, Repeat....
+564|6918|The darkside of Denver

Bevo wrote:

I was going to test out my old RAM next, but yes RMAing the mobo and RAM is pretty close to next on the list. I even grabbed a box from home to get ready to mail em.
Hmmm... that could help.  But did we ever get any of your ram to make at least one successful pass on memtest86 on your board?  If so, in which slots?  I REALLY think that the issue is the board, and it may be killing your memory.  I had a 680i that did EXACTLY that.  The basic flow of most data on a computer at the machine level is HDD->RAM->CPU.  Instructions are loaded from teh HDD or other sources into RAM where they are executed by the CPU, your issue is def somewhere in that last two sets of process.
2010-04-26 10:11:45
Bevo
Nah
+718|6779|Austin, Texas

SonderKommando wrote:

Bevo wrote:

I was going to test out my old RAM next, but yes RMAing the mobo and RAM is pretty close to next on the list. I even grabbed a box from home to get ready to mail em.
Hmmm... that could help.  But did we ever get any of your ram to make at least one successful pass on memtest86 on your board?  If so, in which slots?  I REALLY think that the issue is the board, and it may be killing your memory.  I had a 680i that did EXACTLY that.  The basic flow of most data on a computer at the machine level is HDD->RAM->CPU.  Instructions are loaded from teh HDD or other sources into RAM where they are executed by the CPU, your issue is def somewhere in that last two sets of process.
Yeah, each of them passed memtest in slot 0.

Hopefully I'll have some time tonight and replace the RAM and give it a few boots to see what happens. IDK though, it always seems to hate me in the mornings more than other times. I have no clue why.
2010-04-26 10:19:09
SonderKommando
Eat, Lift, Grow, Repeat....
+564|6918|The darkside of Denver
Save yourself time and RMA the board today. Don't forget to take the CPU out before you mail it off!!
2010-04-26 10:28:51
Bertster7
Confused Pothead
+1,101|6840|SE London

SonderKommando wrote:

Bevo.. RMA both the board and teh RAM. I promise that it will solve the issue.
So long as it isn't the CPU....

I'd agree most likely culprit is mobo though.
2010-04-26 10:48:04
Bevo
Nah
+718|6779|Austin, Texas
I just wiped my old HDD and I'm installing another copy of 7 on it for testing purposes. I won't have time to mail anything off today, so it's tomorrow at best.

Think I can RMA my HDD, RAM, Mobo, and CPU?
2010-04-26 10:49:05
Bertster7
Confused Pothead
+1,101|6840|SE London

Bevo wrote:

I just wiped my old HDD and I'm installing another copy of 7 on it for testing purposes. I won't have time to mail anything off today, so it's tomorrow at best.

Think I can RMA my HDD, RAM, Mobo, and CPU?
I really, really, doubt it's your hard drive.
2010-04-26 10:50:23
Bevo
Nah
+718|6779|Austin, Texas
The other 3 then? Is newegg that understanding?
2010-04-26 10:52:51
Bertster7
Confused Pothead
+1,101|6840|SE London

Bevo wrote:

The other 3 then? Is newegg that understanding?
I don't know.

Here in the UK you have a 14 day cooling off period for returning anything bought online, even if you just decide you don't want it. They have to pay the postage too.

I can't imagine Newegg complaining.
2010-04-26 10:54:13
Bevo
Nah
+718|6779|Austin, Texas
They have a 30day policy, I just don't know how accepting they will be of me throwing half of my stuff in a box and shipping it back to them asking for new stuff.
2010-04-26 10:55:41
Jaekus
I'm the matchstick that you'll never lose
+957|5437|Sydney
But if that's their policy, then surely they'd have to stand by it?
2010-04-26 10:57:35
SonderKommando
Eat, Lift, Grow, Repeat....
+564|6918|The darkside of Denver

Bevo wrote:

I just wiped my old HDD and I'm installing another copy of 7 on it for testing purposes. I won't have time to mail anything off today, so it's tomorrow at best.

Think I can RMA my HDD, RAM, Mobo, and CPU?
I think your CPU is fine.  As long as your temps are good then I wouldnt worry about it too much, your HDD is prob ok too.  I would just RMA your ram and mobo.  You may not even need to RMA the ram.  Im abotu 85% sure the issue is your mobo.   Have you flashed teh BIOS on the mobo at all since you bought it?
2010-04-26 11:02:15
Bertster7
Confused Pothead
+1,101|6840|SE London

SonderKommando wrote:

Bevo wrote:

I just wiped my old HDD and I'm installing another copy of 7 on it for testing purposes. I won't have time to mail anything off today, so it's tomorrow at best.

Think I can RMA my HDD, RAM, Mobo, and CPU?
I think your CPU is fine.  As long as your temps are good then I wouldnt worry about it too much, your HDD is prob ok too.
What are you basing that on? From what he has described the CPU coudl easily be causing it - granted it's more common to see these faults caused by the mobo, but ruling out the CPU when RMAing loads of stuff seems unwise, since it could be that.
2010-04-26 11:04:13
Bevo
Nah
+718|6779|Austin, Texas

SonderKommando wrote:

Bevo wrote:

I just wiped my old HDD and I'm installing another copy of 7 on it for testing purposes. I won't have time to mail anything off today, so it's tomorrow at best.

Think I can RMA my HDD, RAM, Mobo, and CPU?
I think your CPU is fine.  As long as your temps are good then I wouldnt worry about it too much, your HDD is prob ok too.  I would just RMA your ram and mobo.  You may not even need to RMA the ram.  Im abotu 85% sure the issue is your mobo.   Have you flashed teh BIOS on the mobo at all since you bought it?
No. I remember downloading a utility to see if I could upgrade the version, but it was already up to date. I suppose I'll just get to RMAing the mobo and RAM.

edit: (and?) CPU

Last edited by Bevo (2010-04-26 11:09:37)

2010-04-26 11:20:07
SonderKommando
Eat, Lift, Grow, Repeat....
+564|6918|The darkside of Denver

Bertster7 wrote:

SonderKommando wrote:

Bevo wrote:

I just wiped my old HDD and I'm installing another copy of 7 on it for testing purposes. I won't have time to mail anything off today, so it's tomorrow at best.

Think I can RMA my HDD, RAM, Mobo, and CPU?
I think your CPU is fine.  As long as your temps are good then I wouldnt worry about it too much, your HDD is prob ok too.
What are you basing that on? From what he has described the CPU coudl easily be causing it - granted it's more common to see these faults caused by the mobo, but ruling out the CPU when RMAing loads of stuff seems unwise, since it could be that.
Well, the surefire indicator of a CPU problem would be overheating and that seems to be ok.  We've tested the ram and it passes all DIMMS in slot 0 for at least one pass of memtest86+.  His failures begin when he tries to run dual channel, or more than one DIMM installed on the board.  Also, the bug reports seem to reference read/write issues and IRQ issues... leading me to believe that the issue lies with teh memory controller working with the board and the CPU.. I've NEVER seen a bad cpu before that just comes out of the box bad (usually someone has to fuck it up by OCing/improper installation or something).  Im just making an educated guess that its most likely the board.
2010-04-26 11:26:53
Bertster7
Confused Pothead
+1,101|6840|SE London

SonderKommando wrote:

Bertster7 wrote:

SonderKommando wrote:


I think your CPU is fine.  As long as your temps are good then I wouldnt worry about it too much, your HDD is prob ok too.
What are you basing that on? From what he has described the CPU coudl easily be causing it - granted it's more common to see these faults caused by the mobo, but ruling out the CPU when RMAing loads of stuff seems unwise, since it could be that.
Well, the surefire indicator of a CPU problem would be overheating and that seems to be ok.  We've tested the ram and it passes all DIMMS in slot 0 for at least one pass of memtest86+.  His failures begin when he tries to run dual channel, or more than one DIMM installed on the board.  Also, the bug reports seem to reference read/write issues and IRQ issues... leading me to believe that the issue lies with teh memory controller working with the board and the CPU.. I've NEVER seen a bad cpu before that just comes out of the box bad (usually someone has to fuck it up by OCing/improper installation or something).  Im just making an educated guess that its most likely the board.
Overheating is one indicator there is a problem with the CPU. It is certainly not the only one. I've seen bad CPUs straight out of the box. It does happen.

You are right that it is most likely the board, but when RMAing multiple components, why take the risk?
2010-04-26 11:29:15
Bevo
Nah
+718|6779|Austin, Texas
Worst case if the CPU is bad when I get my RMA'd mobo/RAM back, I can always replace it from AMD, they have a 3 year warranty.
2010-04-26 11:35:40
SonderKommando
Eat, Lift, Grow, Repeat....
+564|6918|The darkside of Denver

Bertster7 wrote:

SonderKommando wrote:

Bertster7 wrote:

What are you basing that on? From what he has described the CPU coudl easily be causing it - granted it's more common to see these faults caused by the mobo, but ruling out the CPU when RMAing loads of stuff seems unwise, since it could be that.
Well, the surefire indicator of a CPU problem would be overheating and that seems to be ok.  We've tested the ram and it passes all DIMMS in slot 0 for at least one pass of memtest86+.  His failures begin when he tries to run dual channel, or more than one DIMM installed on the board.  Also, the bug reports seem to reference read/write issues and IRQ issues... leading me to believe that the issue lies with teh memory controller working with the board and the CPU.. I've NEVER seen a bad cpu before that just comes out of the box bad (usually someone has to fuck it up by OCing/improper installation or something).  Im just making an educated guess that its most likely the board.
Overheating is one indicator there is a problem with the CPU. It is certainly not the only one. I've seen bad CPUs straight out of the box. It does happen.

You are right that it is most likely the board, but when RMAing multiple components, why take the risk?
I suppose I seen where you're coming from.  From my professional experience it's almost NEVER the cpu (and given the circumstances)  I figure the less hardware in RMA the better.  Personally I think his ram might be ok as well, but thats the hardware I dont want him to take the risk on.  I think you're right on with waiting on the CPU return and RMAing through AMD Bevo.  However, I dont realistically see that has happening/being necessary.

Last edited by SonderKommando (2010-04-26 11:36:58)

2010-04-26 11:42:44
Bevo
Nah
+718|6779|Austin, Texas
Sonder, if it means anything, these crashes don't really occur until I load up stuff on my drive. Whenever I have a clean install it seems to be fine, but after I load xfire, steam, etc on and boot it up a few times, it starts giving me errors.

Stupid computers.
2010-04-26 11:47:22
SonderKommando
Eat, Lift, Grow, Repeat....
+564|6918|The darkside of Denver

Bevo wrote:

Sonder, if it means anything, these crashes don't really occur until I load up stuff on my drive. Whenever I have a clean install it seems to be fine, but after I load xfire, steam, etc on and boot it up a few times, it starts giving me errors.

Stupid computers.
Are these programs running at startup?
2010-04-26 11:49:55
Bevo
Nah
+718|6779|Austin, Texas

SonderKommando wrote:

Bevo wrote:

Sonder, if it means anything, these crashes don't really occur until I load up stuff on my drive. Whenever I have a clean install it seems to be fine, but after I load xfire, steam, etc on and boot it up a few times, it starts giving me errors.

Stupid computers.
Are these programs running at startup?
Yeah. Catalyst Control Center, Xfire, Steam... among a few other things. Often they'll "die" at startup and give me memory related errors "couldn't write to xyz memory blah blah blah" or just plain crash. Sometimes some will work and then others won't, but a bluescreen ALWAYS follows 1-5 minutes after. For example if I boot up and xfire immediately hands me a crash report, most of the time if I try to open mozilla afterward it won't open either and hand me a similar crash report.

Then again other times everything is completely normal.
2010-04-26 12:24:23
SonderKommando
Eat, Lift, Grow, Repeat....
+564|6918|The darkside of Denver
Can you get into safemode or even desktop and run msconfig and disable them from starting at startup?  THen see what happens.
2010-04-26 12:35:31
Bevo
Nah
+718|6779|Austin, Texas
I don't think they're a cause, more of a result. I can try when I get back from class, I guess. I don't really know what that would accomplish tbh - as im sitting on my desktop right now and it's being completely functional.

Shrug.

 

Pages: 1 … 3 4 5 6 7 8

Board footer

Privacy Policy - © 2025 Jeff Minard