63 replies to this topic

[eniparadoxgma]

m.oreilly, on Sep 29 2007, 09:57 PM, said:

the asus was a board i had had the chipset hsf issue with: it was barely noticable. i caught it before i installed the mobo. actually, the only real bluescreen issues i have ever had were with asus boards. i won't buy another one. bios and driver conflicts were the norm. i ended up pulling the drives on it and transplanting them to a dfi. after a hal fix, i never had issues. heck, the last time i saw a bluescreen was two years ago, with the a8n sli...i hope it is just some simple thing.

EDIT: sorry to sound so caviler/flip. i just really didn't like the asus stuff i had. i could be a very isolated case, and you might just be having probs caused by running a sata optical...

No thang, mane. I opened her up and took her apart. Well, as far as the cpu socket goes, there seemed to be some very minute discoloration. It could've been a little dust or some errant thermal paste. Either way it was barely noticeable. However, the heatsink itself and my case in general had been overrun by the dust bunnies of doom. I took it all apart, cleaned off all the AS5, and blew out all the dust with a can of air and a paintbrush. I really had to work on that monster Zalman.

This time, when installing the cpu, I used the "spread the thermal paste out" method as opposed to the "throw the glob in the middle and hope for the best". Even though the AS5 hasn't had the time to settle, my temps seem to be down a little bit. Whether it's from the cleaning out of the whole box or the fresh cpu install I'm not sure. Temps now are: Idle- cpu 36C, MB 35C and Folding 100% load- 49C, MB 41C.

One thing I did notice in passing that may have been the culprit is that the top screw holding the Zalman onto the CPU seemed really easy to unscrew, as if it wasn't tight at all...

Regardless, I did everything right, got it cleaned up, and screwed that monster of a HS back on tightly. Now it's time to play the waiting game.

Btw, all the temps and everything are while OC'd at 2.815/DDR512 where I usually keep it. It's pretty cool considering the crappy airflow in my case.

Thanks for the help, and here's to no more BSOD's.

[m.oreilly]

the "easy to unscrew" is worrisome, though i bet the cleaning will do wonders for all the rest of the mobo components. a cooler cap is a happy cap

[banj0]

dude, get a Mac.

Shite, I'm in so much trouble now.....

[m.oreilly]

banj0, on Sep 30 2007, 12:23 AM, said:

dude, get a Mac.

Shite, I'm in so much trouble now.....

[eniparadoxgma]

banj0, on Sep 30 2007, 03:23 AM, said:

dude, get a Mac.

Shite, I'm in so much trouble now.....

You are such a

[m.oreilly]

[eniparadoxgma]

While it seems to have calmed down a bit, I have still got an occasional BSOD. Just got an IRQL NoT LESS OR EQUAL blah blah blah.

I was wondering if anyone could tell me if my IRQ stuff looks alright. I notice that my RAID is sharing an IRQ with some PCI to USB thingie. Whatcha think?

[stormrosson]

don worry homey IRQ sharing is common and neccessary in any modern setup as 16 physical interrupts is obviously not enuff , this feat is a bios assigned task using the automatic programable interrupt controller (or somethin close to that)....irq errors these days can often be traced to memory glitches or faulty drivers ....usually,........sometimes........ I think......hmmmmmmmmmmmmm

[eniparadoxgma]

stormrosson, on Oct 18 2007, 09:27 PM, said:

don worry homey IRQ sharing is common and neccessary in any modern setup as 16 physical interrupts is obviously not enuff , this feat is a bios assigned task using the automatic programable interrupt controller (or somethin close to that)....irq errors these days can often be traced to memory glitches or faulty drivers ....usually,........sometimes........ I think......hmmmmmmmmmmmmm

Given that my memory passes memtest for like 12 hours (though I know it isn't always accurated) combined with the fact that I did not get these errors/BSOD's in Vista 64 Ultimate I am thinking it has to be some kind of driver thingimabob. I thought that since one of the symptoms was that apparently a USB port or two is no longer operable that perhaps it had something to do with the PCI to USB/RAID controller (where my RAID array is) IRQ sharing. I've seen errors ranging from IRQ to memory corruption to blah blah blah.

WHAT IS IT MAN?!?!?!

[m.oreilly]

heck, i'd tend to go back to vista x64, or try raidless. i don't like the jib on them sata opticals, at least in winders xp...

[stormrosson]

I finally got a sata dvdrw....samsung , called TSSTcorp by my pc, and although the setup probs and stuff we previously saw with sata optical drives, seems to have been solved, I had to reflash the firmware in the drive to cure some write errors when burning dvd disks. Now it does work flawlessly oh yeah Eni are u oc'ed at all?

[m.oreilly]

hey bro, i think eni did a clean install w/o an OC, though he might 'ave got a wild hair or sumtin afterward

[eniparadoxgma]

m.oreilly, on Oct 19 2007, 01:50 PM, said:

hey bro, i think eni did a clean install w/o an OC, though he might 'ave got a wild hair or sumtin afterward

Keerect, sir. However, these errors have occurred when there was no OC at all. I think it has to be something software/driver based because of the problems not occurring on Vista. However...w/Vista I saw an approximate 50% decrease in FPS in Steam games and that is a definite no-no for me.

[stormrosson]

:clarky:u mite at the clean install stage and testing between each driver install, and eventually at every app install, tedious and boring but it may be what it takes broheim and don forget MO's idea about installing raid-free too

Edited by stormrosson, 20 October 2007 - 03:50 AM.

[eniparadoxgma]

stormrosson, on Oct 19 2007, 11:47 PM, said:

:clarky:u mite at the clean install stage and testing between each driver install, and eventually at every app install, tedious and boring but it may be what it takes broheim and don forget MO's idea about installing raid-free too

Ya see, the problem with that is the BSODs are so intermittent. I've had two in the last three days, so there would be no way to tell by waiting after every driver install unless I gave each one like a week.

Anyhow, here's the last two BSOD debugs if anyone thinks they can decipher 'em. I'm telling ya, I always get the most ambiguous, hard to track down PC issues. For the record, this RAM I have was tested by Super Talent themselves for over 24 hours and had no errors, but that was a year or two ago. (That's back when I found out it I had a brand new Asus mobo with faulty DIMM slots) I guess it's possible that it went haywire, but if it's hardware I'd be quicker to blame the mobo.


For your viewing enjoyment:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 804cdfb2, memory referenced.
Arg2: 00000008, value 0 = read operation, 1 = write operation.
Arg3: 804cdfb2, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: 804cdfb2

FAULTING_IP:
+ffffffff804cdfb2
804cdfb2 ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: hl2.exe

LAST_CONTROL_TRANSFER: from 804ee9ae to 804cdfb2

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
a4dd1c38 804ee9ae 879dd020 85ee2858 85ee2868 0x804cdfb2
a4dd1c4c 804ee9d5 873ef020 85ee280f 85ee2870 nt!IopPageReadInternal+0xf4
a4dd1c6c 80512a30 868327a8 85ee2890 85ee2870 nt!IoPageRead+0x1b
a4dd1ce8 8051c77c e12541d8 30233a4c c0181198 nt!MiDispatchFault+0x286
a4dd1d4c 8053f90c 00000000 30233a4c 00000001 nt!MmAccessFault+0xf90
a4dd1d4c 3000b4c0 00000000 30233a4c 00000001 nt!KiTrap0E+0xcc
00122c00 00000000 00000000 00000000 00000000 0x3000b4c0


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!IopPageReadInternal+f4
804ee9ae 5f pop edi

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9c

SYMBOL_NAME: nt!IopPageReadInternal+f4

FAILURE_BUCKET_ID: 0x50_W_nt!IopPageReadInternal+f4

BUCKET_ID: 0x50_W_nt!IopPageReadInternal+f4

Followup: MachineOwner
---------


Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {80000004, 8064ad86, ba503c9c, ba503998}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: 80000004, The exception code that was not handled
Arg2: 8064ad86, The address that the exception occurred at
Arg3: ba503c9c, Exception Record Address
Arg4: ba503998, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - No such interface supported

FAULTING_IP:
nt!ExpTimeRefreshWork+ae
8064ad86 55 push ebp

EXCEPTION_RECORD: ba503c9c -- (.exr 0xffffffffba503c9c)
ExceptionAddress: 8064ad86 (nt!ExpTimeRefreshWork+0x000000ae)
ExceptionCode: 80000004 (Single step exception)
ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT: ba503998 -- (.cxr 0xffffffffba503998)
eax=8064ac1d ebx=8a3b9020 ecx=000000db edx=80010031 esi=8055a3fd edi=8055a4e1
eip=8064ad86 esp=ba503d64 ebp=ba503d74 iopl=2 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00042202
nt!ExpTimeRefreshWork+0xae:
8064ad86 55 push ebp
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x7E

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0x80000004 - {EXCEPTION} Single Step A single step or trace operation has just been completed.

LAST_CONTROL_TRANSFER: from 80533fe6 to 8064ad86

STACK_TEXT:
ba503d74 80533fe6 00000000 00000000 8a3b9020 nt!ExpTimeRefreshWork+0xae
ba503dac 805c4cce 00000000 00000000 00000000 nt!ExpWorkerThread+0x100
ba503ddc 805411c2 80533ee6 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
222 errors : !nt (8064a002-8064aff2)
8064a000 7d 47 *01 c2 83 c1 f8 3b c1 89 46 e4 7e 07 3b d1 }G.....;..F.~.;.
8064a010 89 4e *46 7d 34 8b 55 20 8b 45 0c 52 57 50 e8 0d .NF}4.U .E.RWP..
...
8064a030 11 f8 *8f 48 07 c1 f9 03 2b c1 83 f8 10 7f b9 8b ...H....+.......
8064a040 55 18 *2b f2 e9 7f 00 00 00 8b 56 dc 3b 56 e0 7d U.+.......V.;V.}
8064a050 48 8b *64 dc 8b 4e ec 8a 04 08 8b 56 c8 88 02 8b H.d..N.....V....
8064a060 5e c8 *0b 4e d0 43 85 c9 89 5e c8 8d 04 09 7d 16 ^..N.C...^....}.
8064a070 8b 4e *6e 89 01 8b 46 c8 89 46 cc 83 c0 04 89 46 .Nn...F..F.....F
8064a080 c8 b8 *89 00 00 00 8b 4e dc 41 89 46 d0 89 4e dc .......N.A.F..N.
8064a090 8b 46 *6a 8b d1 3b d0 7c b8 e8 42 f2 ff ff 8b 46 .Fj..;.|..B....F
8064a0a0 c8 8b *76 c4 8b 4d 10 2b c2 3b c1 72 07 8b 55 18 ..v..M.+.;.r..U.
...
8064a0c0 bc 8b *d5 18 2b c1 8b f0 85 ff 74 07 8b 45 20 52 ....+.....t..E R
8064a0d0 50 ff *f5 8b c6 5f 5e 5b 5d c2 20 00 33 c0 5d c2 P...._^[]. .3.].
8064a0e0 20 00 *ce cc cc cc cc cc cc cc cc cc cc cc cc cc ...............
8064a0f0 8b ff *77 8b ec 57 8b 7d 10 85 ff 0f 84 9e 00 00 ..w..W.}........
8064a100 00 8b *df 08 8d 42 ff 3d ff ff 00 00 89 45 10 0f .....B.=.....E..
8064a110 87 8a *a2 00 00 53 8b 5d 14 33 c9 83 fb 09 b8 d8 .....S.].3......
8064a120 2b 00 *22 7e 07 bb 09 00 00 00 eb 05 83 fb 01 7c +."~...........|
8064a130 12 83 *f9 02 b8 00 00 01 00 7c 08 8d 04 12 b9 00 .........|......
8064a140 00 01 *82 56 8d b1 94 01 00 00 8b 4d 0c 83 e6 e0 ...V.......M....
8064a150 8d 44 *10 38 50 51 ff d7 85 c0 75 07 5e 5b 5f 5d .D.8PQ....u.^[_]
8064a160 c2 10 *8a 8b 55 10 8b f8 89 50 10 89 58 14 c7 00 ....U....P..X...
...
8064a180 20 00 *08 00 2b d1 03 c2 8d 0c 30 89 4f 08 89 47 ...+.....0.O..G
8064a190 0c e8 *2a f0 ff ff 5e 5b 8b c7 5f 5d c2 10 00 33 ..*...^[.._]...3
8064a1a0 c0 5f *f7 c2 10 00 cc cc cc cc cc cc 8b ff 55 8b ._............U.
8064a1b0 ec 66 *21 7d 08 00 75 16 8b 45 0c c7 00 10 80 00 .f!}..u..E......
8064a1c0 00 8b *ed 10 c7 00 00 10 00 00 33 c0 eb 18 66 81 ..........3...f.
8064a1d0 7d 08 *a2 01 75 0b 8b 45 0c c7 00 10 00 00 00 eb }...u..E........
8064a1e0 e0 b8 *39 00 00 c0 5d c2 0c 00 cc cc cc cc cc cc ..9...].........
8064a1f0 8b ff *77 8b ec 83 ec 20 8b 45 10 83 65 f8 00 53 ..w.... .E..e..S
8064a200 8b 5d *0e 8d 8b 00 10 00 00 3b c8 56 57 c6 45 fe .].......;.VW.E.
8064a210 00 73 *af 89 4d 10 8b c1 8b 55 14 8b 75 18 8d 8a .s..M....U..u...
8064a220 ff 0f *22 00 3b ce 89 4d f0 72 03 89 75 f0 8b 7d ..".;..M.r..u..}
8064a230 20 83 *ed f4 00 8d 72 02 89 75 e0 89 75 e8 46 39 .....r..u..u.F9
...
8064a250 08 02 *90 00 00 0f 83 e2 01 00 00 8d 46 01 c7 45 ............F..E
8064a260 e4 e4 *43 67 80 89 45 20 8b 45 e4 eb 1b ff 45 f8 ..Cg..E .E....E.
8064a270 8b 45 *78 c1 e0 02 8b 88 c0 e3 67 80 8d 80 e4 e3 .Ex.......g.....
8064a280 67 80 *23 4f 08 89 45 e4 8b 00 03 45 0c 3b c3 72 g.#O..E....E.;.r
8064a290 dc 8d *41 03 3b 45 10 77 0c 57 53 ff 55 08 85 c0 ..A.;E.w.WS.U...
...
8064a2b0 f4 b0 *0b d2 e0 f6 d0 20 45 ff 8a 03 08 45 fe 88 ....... E....E..
8064a2c0 06 46 *77 45 20 43 e9 ec 00 00 00 8b 4d 20 3b 4d .FwE C......M ;M
8064a2d0 f0 0f *a3 12 01 00 00 8b 4d f4 8b d3 2b 57 0c b3 ........M...+W..
8064a2e0 01 d2 *c3 8b 4d f8 08 5d ff 85 c9 75 12 8d 48 fd ....M..]...u..H.
8064a2f0 81 e1 *fd 0f ff ff 4a c1 e2 0c e9 a2 00 00 00 83 ......J.........
8064a300 f9 01 *77 12 8d 48 fd 81 e1 ff 07 ff ff 4a c1 e2 ..w..H.......J..
...
8064a320 ff 03 *f5 ff 4a c1 e2 0a eb 77 83 f9 03 75 0f 8d ....J....w...u..
8064a330 48 fd *2b e1 ff 01 ff ff 4a c1 e2 09 eb 63 83 f9 H.+.....J....c..
8064a340 04 75 *af 8a c8 80 e9 03 66 0f b6 c9 fe ca 8a ea .u......f.......
8064a350 eb 51 *01 f9 05 75 10 33 c9 8a c8 80 e9 03 83 e1 .Q...u.3........
8064a360 7f 4a *69 e2 07 eb 3a 83 f9 06 75 10 33 c9 8a c8 .Ji...:...u.3...
8064a370 80 e9 *ab 83 e1 3f 4a c1 e2 06 eb 25 83 f9 07 75 .....?J....%...u
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output.

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

STACK_COMMAND: .cxr 0xffffffffba503998 ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

BUCKET_ID: MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption










One more thing: It's pretty important for me to find out if it's a hardware problem because if it is then what I'll probably do is jet my 175 back to Newegg and start saving for a full upgrade sooner rather than later. I don't need to be buying a 939 cpu AND ram or mobo. That's just crazy.

Edited by eniparadoxgma, 23 October 2007 - 02:00 PM.