| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 91504 | 2008-07-09 08:43:00 | Blue Screen of Death BSoD | Blackflag486 (13947) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 686942 | 2008-07-09 20:43:00 | I take it you went to the MS site to download it?? I hope youre on broadband. I think this is the 64 bit version update (www.microsoft.com) And this is the 32 bit version update (www.microsoft.com) |
Speedy Gonzales (78) | ||
| 686943 | 2008-07-09 21:15:00 | Yeah, I'm on broadband, I'll do that when I get home tonight. | Blackflag486 (13947) | ||
| 686944 | 2008-07-10 04:20:00 | effing slowest download sites ever... | Blackflag486 (13947) | ||
| 686945 | 2008-07-10 04:47:00 | The extra molex by the PCIe slot is to provide extra power the PCIe bus, it MUST be plugged in to deliver smooth power under load. BSOD are nearly always a memory issue or hardware related (drivers) the graphics maybe struggling for power under load causing BSOD! PLug in the molex, its not there for show! |
SolMiester (139) | ||
| 686946 | 2008-07-11 03:01:00 | Well according to the manual, it is there just to plug your video card into.. I have a newer card that uses 6pin setup which of course it is plugged in. The slot on the motherboard is to go from the video card to the motherboard.. So from the PSU to the motherboard on that spot doesn't make sense. The manual says its for video cards only. Like I think a 9800pro or something would use this slot. or a 6600gt | Blackflag486 (13947) | ||
| 686947 | 2008-07-11 04:19:00 | Well according to the manual, it is there just to plug your video card into.. I have a newer card that uses 6pin setup which of course it is plugged in. The slot on the motherboard is to go from the video card to the motherboard.. So from the PSU to the motherboard on that spot doesn't make sense. The manual says its for video cards only. Like I think a 9800pro or something would use this slot. or a 6600gt NO, no no....the molex on the board is to provide extra power to the PCIe slots!! Try reading the manual 2-6 again!.Page 16...This connector provides an auxiliary power source for devices added on PCI Express slots., so molex from PSU to this slot!! |
SolMiester (139) | ||
| 686948 | 2008-07-11 05:52:00 | I was in a similar situation, 3 months of randomly happening BSOD events, driving me nuts (1 x reinstall, 1 x new HDD, an in the simplest of PC configuration). In the end and in desperation I changed my 10 months old 1 x 1GB memory stick (from reputable Kingston) with a no-name RAM of 1 x 1 GB and I am now 7 firm weeks without a BSOD! I agree with post replier SolMiester, look at RAM as the 1st thing you do with BSOD. Had I known this I could have saved me lots of misery. Next up, claiming the "lifetime" guarantee from Kingston ...... | Auke (4179) | ||
| 686949 | 2008-07-16 09:17:00 | Back from vacation and this is what I get.. I can't even read the dmp file. I downloaded microsoft debugger tool and I sitll cant figure it out. Problem signature: Problem Event Name: BlueScreen OS Version: 6.0.6001.2.1.0.256.1 Locale ID: 1033 Additional information about the problem: BCCode: 4e BCP1: 0000000000000099 BCP2: 000000000003E2EE BCP3: 0000000000000002 BCP4: 000000000003E2ED OS Version: 6_0_6001 Service Pack: 1_0 Product: 256_1 Files that help describe the problem: C:\Windows\Minidump\Mini071608-01.dmp C:\Users\Blackflag\AppData\Local\Temp\WER-36171-0.sysdata.xml C:\Users\Blackflag\AppData\Local\Temp\WERF9E0.tmp. version.txt Read our privacy statement: go.microsoft.com |
Blackflag486 (13947) | ||
| 686950 | 2008-07-16 09:32:00 | then I did this I did a debuglog.. check it ===================== PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000099, A PTE or PFN is corrupt Arg2: 000000000003e2ee, page frame number Arg3: 0000000000000002, current page state Arg4: 000000000003e2ed, 0 Debugging Details: ------------------ BUGCHECK_STR: 0x4E_99 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: audiodg.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80001ade3ab to fffff80001a67390 STACK_TEXT: fffffa60`05d91ef8 fffff800`01ade3ab : 00000000`0000004e 00000000`00000099 00000000`0003e2ee 00000000`00000002 : nt!KeBugCheckEx fffffa60`05d91f00 fffff800`01ac9e0d : fffff800`63416d4d 00000000`00001000 00000000`00000fc4 00000000`006f4401 : nt!MiBadShareCount+0x4b fffffa60`05d91f40 fffff800`01a4a917 : fffffa80`06417040 fffff700`00001414 00000000`00000000 fffff700`01080630 : nt! ?? ::FNODOBFM::`string'+0x1c7f0 fffffa60`05d91fd0 fffff800`01a4b090 : fffffa80`06417040 fffffa80`00000cf6 fffffa80`00000a9f 00000000`00000001 : nt!MiDeleteAddressesInWorkingSet+0x308 fffffa60`05d92890 fffff800`01d0fe1c : fffff880`05e248a0 fffff800`01c9f594 00000000`00000000 00000000`00000000 : nt!MmCleanProcessAddressSpace+0xa8 fffffa60`05d928e0 fffff800`01c9f5b1 : fffffa60`000000ff fffffa80`03834401 000007ff`fffd6000 00000000`78457350 : nt!PspExitThread+0x4f8 fffffa60`05d929a0 fffff800`01a9153b : 00000000`00000000 00000000`00000000 fffff800`01ca07d0 00000000`00000000 : nt!PsExitSpecialApc+0x1d fffffa60`05d929d0 fffff800`01a95205 : fffffa60`05d92ca0 fffffa60`05d92a70 fffff800`01ca07d0 00000000`00000001 : nt!KiDeliverApc+0x3bb fffffa60`05d92a70 fffff800`01a66edd : fffffa80`03834370 00000000`017efde8 00000000`00000000 00000000`00000000 : nt!KiInitiateUserApc+0x75 fffffa60`05d92bb0 00000000`7749722a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0xa2 00000000`017efdc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7749722a STACK_COMMAND: kb FOLLOWUP_IP: nt!MiBadShareCount+4b fffff800`01ade3ab cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiBadShareCount+4b FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4812c3f7 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4b BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4b Followup: MachineOwner |
Blackflag486 (13947) | ||
| 686951 | 2008-07-16 09:33:00 | So is this a Audio Problem??? Or Memory Corruption? I have a sound blaster audigy I can disable the onboard then use that and see what happens? | Blackflag486 (13947) | ||
| 1 2 3 4 5 6 | |||||