Tech Support Forum banner
Status
Not open for further replies.
1 - 14 of 14 Posts

·
Registered
Joined
·
20 Posts
Discussion Starter · #1 · (Edited)
Hello, im not sure if this is a hardware problem, or a OS problem, could even be a problem in bios, though i havent modified anything and i have it saved as optimal defaults. But randomly throughout my computer use i get the infamous "blue screen of death" it happens when i try to load games or youtube mostly, but somtimes i could just be idling in desktop and get it, or loading a webpage. So basically, whenever. I have windows 7 64 bit, but it shouldnt be an issue since all my parts are compatible, i had this same problem with vista 32 bit.

CPU: AMD Phenom 9600 cuad core 2.3ghz
Harddrive: Seagate Barracuda 7200.11 500GB SATA/300 7200RPM
Motherboard: Biostar GF8100 M2+ TE GeForce 8100 Socket AM2+ mATX
2gb of installed ram (more on the way)
Evga 8800gts 512mb video card

I have reformatted my comp a few times, i may try partitioning the hard drive and only using one partition for backup files and the rest for my OS and such.

Any ideas?

Edit: Error bccode 124

Attachment are my 3 most recent crashes
 

Attachments

·
TSF Team Emeritus, Visiting Expert | Microsoft Sup
Joined
·
4,026 Posts
Hello and welcome to TSF.

All three mirror each other; bugcheck 0x124 - WHEA_UNCORRECTABLE_ERROR:
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Devin\Downloads\TSF\dom6663\120609-14664-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c57000 PsLoadedModuleList = 0xfffff800`02e94e50
Debug session time: Sun Dec  6 11:23:43.816 2009 (GMT-5)
System Uptime: 0 days 0:00:09.094
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80024248f8, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80024248f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02f6b6f0 fffff800`02f11a89 : fffffa80`024248d0 fffffa80`018d8040 fffff880`02f6bc38 00000000`00000018 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02f6bc10 fffff800`02df3547 : fffffa80`024248d0 fffff800`02e6c5f8 fffffa80`018d8040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02f6bc40 fffff800`02d5bb95 : fffff800`02ece360 fffffa80`0242d828 fffffa80`0242d820 fffffa80`018d8040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02f6bc80 fffff800`02cd6161 : fffff880`010c2e00 fffff800`02d5bb70 fffffa80`018d8040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02f6bcb0 fffff800`02f6c166 : 00000000`00000000 fffffa80`018d8040 00000000`00000080 fffffa80`0184fb30 : nt!ExpWorkerThread+0x111
fffff880`02f6bd40 fffff800`02ca7486 : fffff880`02d63180 fffffa80`018d8040 fffff880`02d6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f6bd80 00000000`00000000 : fffff880`02f6c000 fffff880`02f66000 fffff880`02f6af70 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

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

0: kd> r
rax=fffffa8002ed1000 rbx=fffffa80024248f8 rcx=fffff88002f6b730
rdx=fffffa8001812000 rsi=0000000000000000 rdi=fffffa8002ed1000
rip=fffff800030fd3cc rsp=fffff88002f6b6f0 rbp=0000000000000001
 r8=000000000000f1e0  r9=000000000000060c r10=00000000000007ff
r11=000000000000060c r12=fffff80002ece3c0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
nt!WheapCreateLiveTriageDump+0x6c:
fffff800`030fd3cc 48897c2438      mov     qword ptr [rsp+38h],rdi ss:0018:fffff880`02f6b728=fffffa8000000910
0: kd> k
Child-SP          RetAddr           Call Site
fffff880`02f6b6f0 fffff800`02f11a89 nt!WheapCreateLiveTriageDump+0x6c
fffff880`02f6bc10 fffff800`02df3547 nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02f6bc40 fffff800`02d5bb95 nt!WheapProcessWorkQueueItem+0x57
fffff880`02f6bc80 fffff800`02cd6161 nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02f6bcb0 fffff800`02f6c166 nt!ExpWorkerThread+0x111
fffff880`02f6bd40 fffff800`02ca7486 nt!PspSystemThreadStartup+0x5a
fffff880`02f6bd80 00000000`00000000 nt!KxStartSystemThread+0x16
0: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`02f6b6f0 fffff800`02f11a89 : fffffa80`024248d0 fffffa80`018d8040 fffff880`02f6bc38 00000000`00000018 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02f6bc10 fffff800`02df3547 : fffffa80`024248d0 fffff800`02e6c5f8 fffffa80`018d8040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02f6bc40 fffff800`02d5bb95 : fffff800`02ece360 fffffa80`0242d828 fffffa80`0242d820 fffffa80`018d8040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02f6bc80 fffff800`02cd6161 : fffff880`010c2e00 fffff800`02d5bb70 fffffa80`018d8040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02f6bcb0 fffff800`02f6c166 : 00000000`00000000 fffffa80`018d8040 00000000`00000080 fffffa80`0184fb30 : nt!ExpWorkerThread+0x111
fffff880`02f6bd40 fffff800`02ca7486 : fffff880`02d63180 fffffa80`018d8040 fffff880`02d6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f6bd80 00000000`00000000 : fffff880`02f6c000 fffff880`02f66000 fffff880`02f6af70 00000000`00000000 : nt!KxStartSystemThread+0x16
0: kd> lmntsm
start             end                 module name
fffff880`00ed4000 fffff880`00f2b000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`00fe2000 fffff880`00fed000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00fd9000 fffff880`00fe2000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00dd6000 fffff880`00e00000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00cba000 fffff880`00d7a000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`00c00000 fffff880`00c30000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c5c000 fffff880`00cba000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01150000 fffff880`011c3000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`013f0000 fffff880`013fe000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`013da000 fffff880`013f0000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00fed000 fffff880`00ff6000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01086000 fffff880`01092000   dump_ataport dump_ataport.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e00000 fffff880`00e13000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`010de000 fffff880`010f2000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01092000 fffff880`010de000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`013d0000 fffff880`013da000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`011c3000 fffff880`011fd000   fvevol   fvevol.sys   Mon Jul 13 19:22:15 2009 (4A5BC1A7)
fffff880`015b4000 fffff880`015fe000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02c0e000 fffff800`02c57000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`0142a000 fffff880`01433000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff800`00b97000 fffff800`00ba1000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`013a5000 fffff880`013bf000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01589000 fffff880`015b4000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:50:34 2009 (4A5BC84A)
fffff880`00c3b000 fffff880`00c48000   mcupdate mcupdate.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`00fbf000 fffff880`00fd9000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f34000 fffff880`00f3e000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`010f2000 fffff880`01150000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`01418000 fffff880`0142a000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01437000 fffff880`01529000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`01529000 fffff880`01589000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff800`02c57000 fffff800`03234000   nt       ntkrnlmp.exe Mon Jul 13 19:40:48 2009 (4A5BC600)
fffff880`01202000 fffff880`013a5000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`00f7e000 fffff880`00f93000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f3e000 fffff880`00f71000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fa8000 fffff880`00faf000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00faf000 fffff880`00fbf000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013bf000 fffff880`013d0000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00c48000 fffff880`00c5c000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`0104c000 fffff880`01086000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01410000 fffff880`01418000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01602000 fffff880`017ff000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`00f71000 fffff880`00f7e000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01400000 fffff880`01410000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00f93000 fffff880`00fa8000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00d7a000 fffff880`00dd6000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01000000 fffff880`0104c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`00e21000 fffff880`00ec5000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00ec5000 fffff880`00ed4000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f2b000 fffff880`00f34000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
Mini Kernel Dump does not contain unloaded driver list
Definitely looks like a hardware problem. Follow the instructions here: http://www.techsupportforum.com/1871981-post2.html

It will provide us with more information about your computer.
 

·
TSF Team Emeritus, Visiting Expert | Microsoft Sup
Joined
·
4,026 Posts
....Hm. Where did you get this copy of Windows 7?

The BSOD's hit you hard starting 7/17/2009, meaning that you were running the trial version. They were occurring very often - 26 times in fact - between 7/17 and 7/18, then stopped until 11/5-6, where you were hit with a few more. That then stopped until just recently, 12/5. Understand that all the while, you're getting the same BSOD - 0x124. Is there anything at all that you had removed and replaced, or even disabled between those periods? Any slots on the motherboard or USB ports, etc. that were being used then disconnected?

Also, The longest trial version was 90 days long, restricted to IT professionals only. How have you been running it for five months? Have you recently installed a serial, or...?
 

·
Registered
Joined
·
20 Posts
Discussion Starter · #6 · (Edited)
My brother gave it to me. I was having the same issue with windows vista 32 bit, so he gave me this copy of windows 7. I dont believe ive disabled anything, when i first built this computer roughly 3 months ago, it worked fine for a month, after i got my new video card and put it in, downloaded the nvidia display driver and nvidia control pannel, installed battlefeild 2, the restart it required broke somthing. as soon as i restarted my comp i started getting the bsod's

The large spread of the errors was due to the fact when i origionally got the first error i restarted my comp prolly maybe 50 times trying to do different things to solve it. I got sick of it, and over the course of 2 months continued to try it, until recently when i installed windows 7 got a decline in errors, now i can play a few games, but some websites and youtube cause crash.

Since this is a old version of windows 7 should i upgrade it? or purchase the new version? or what operating system would you reccomend i use?
 

·
Administrator, Manager, Microsoft Support, MVP
Joined
·
34,403 Posts
The last dump that DT Roberts ran shows system uptime of just 6 seconds. Some catastrophic event is obviously taking place.

I do believe there may be a problem with your Windows 7 installation.

The reports tell us that you are running Microsoft Windows 7 Ultimate, 6.1.7600 - Build 7600 - but with an OEM key. Did you use a key provided with the Windows 7 DVD by your brother - or did you obtain a key from your OEM (system manufacturer)?

Regards. . .

jcgriff2

.
 

·
Registered
Joined
·
20 Posts
Discussion Starter · #8 · (Edited)
I had my brother install it while i was at work. Ill ask him. The only reason i doubt it is the OS is because I was having the same exact issue with windows vista 32 bit, which i bought myself. I think it was my motherboard, i fear i might have shocked it while i was disassembling my computer to send the box back, found a crack in the plastic front.

My brother Max, said that he used a CD key that he had for the registration. Not sure where he got it from, but whats what he said.

Also i have not been running windows 7 for 5 months as robert stated, i had vista 32 bit running for roughly 3 months, i purchased the motherboard refurbished from Geeks.com and then only recently put windows 7 on here. I guess somehow the dump files from earlier were saved onto the motherboard, since i bought this hard drive new with the motherboard.
 

·
Administrator, Manager, Microsoft Support, MVP
Joined
·
34,403 Posts
OH.... Yeah, I agree - if same problems existed w/ Vista, then most likely the Windows 7 RTM 7600 version is OK - depending on key, though.

As DT Roberts did say, 0x124 bugcheck is more often than not hardware related.
 

·
Registered
Joined
·
20 Posts
Discussion Starter · #10 ·
I purchased the motherboard back in september, so i dont see how BSOD issues would be coming all the way from july. It was refurbished from geeks.com....is there any way to perhaps get a replacement, i dont have a warranty anymore, but if they sent me a malfunctioning product without running the proper checks on it, then i should be entitled to a refund...no?
 

·
Administrator, Manager, Microsoft Support, MVP
Joined
·
34,403 Posts
There is no doubt in my mind about the BSOD dates as mentioned by DT Roberts based on the files provided to us - look at the dates on the 44 dump files - they begin on July 16, 2009 -
Code:
[font=lucida console]
 Volume in drive A is New Volume
 Volume Serial Number is B8F7-2140

 Directory of A:\D\!!_Kernel_Dumps\dom6663_Vista_12-07-09__jcgriff2__\!_Kernel

07/16/2009  11:05 PM           262,144 071709-16099-01.dmp
07/16/2009  11:06 PM           262,144 071709-17269-01.dmp
07/16/2009  11:13 PM           262,144 071709-16208-01.dmp
07/16/2009  11:15 PM           262,144 071709-23680-01.dmp
07/16/2009  11:17 PM           262,144 071709-23696-02.dmp
07/16/2009  11:32 PM           262,144 071709-21637-01.dmp
07/17/2009  12:10 AM           262,144 071709-18189-01.dmp
07/17/2009  12:13 AM           262,144 071709-13743-01.dmp
07/17/2009  12:22 AM           262,144 071709-16239-01.dmp
07/17/2009  12:50 AM           262,144 071709-16692-01.dmp
07/17/2009  12:53 AM           262,144 071709-15787-01.dmp
07/17/2009  01:05 AM           262,144 071709-14960-01.dmp
07/17/2009  01:17 AM           262,144 071709-17955-01.dmp
07/17/2009  01:43 AM           262,144 071709-14414-01.dmp
07/17/2009  02:13 AM           262,144 071709-27705-01.dmp
07/17/2009  02:27 AM           262,144 071709-20014-01.dmp
07/17/2009  02:28 AM           262,144 071709-20888-01.dmp
07/17/2009  02:30 AM           262,144 071709-24804-01.dmp
07/17/2009  03:59 AM           262,144 071709-18579-01.dmp
07/18/2009  12:25 AM           262,144 071809-12246-01.dmp
07/18/2009  12:46 AM           262,144 071809-12277-01.dmp
07/18/2009  12:52 AM           262,144 071809-13150-01.dmp
07/18/2009  01:46 AM           262,144 071809-15272-01.dmp
07/18/2009  02:02 AM           262,144 071809-22370-01.dmp
07/18/2009  02:03 AM           262,144 071809-23337-01.dmp
07/18/2009  02:09 AM           262,144 071809-22557-01.dmp
11/05/2009  09:58 PM           284,744 110509-29452-01.dmp
11/06/2009  07:24 PM           283,144 110609-27752-01.dmp
11/06/2009  07:34 PM           283,224 110609-29359-01.dmp
11/06/2009  08:03 PM           284,248 110609-20436-01.dmp
11/06/2009  08:45 PM           283,784 110609-24554-01.dmp
11/06/2009  08:46 PM           262,144 110609-21434-01.dmp
12/05/2009  03:40 PM           262,144 120509-22666-01.dmp
12/05/2009  03:51 PM           262,144 120509-22058-01.dmp
12/05/2009  03:53 PM           262,144 120509-22729-01.dmp
12/05/2009  03:56 PM           262,144 120509-22698-01.dmp
12/05/2009  03:56 PM           262,144 120509-23212-01.dmp
12/05/2009  05:07 PM           262,144 120509-16551-01.dmp
12/06/2009  09:10 AM           301,878 120609-15397-01.dmp
12/06/2009  09:32 AM           301,878 120609-14944-01.dmp
12/06/2009  09:50 AM           301,878 120609-16348-01.dmp
12/06/2009  10:18 AM           301,878 120609-15100-01.dmp
12/06/2009  10:21 AM           301,878 120609-14679-01.dmp
12/06/2009  10:41 AM           262,144 120609-15740-01.dmp
              44 File(s)     11,841,430 bytes
               0 Dir(s)  76,388,216,832 bytes free[/font]

jcgriff2

.
 

·
Registered
Joined
·
20 Posts
Discussion Starter · #12 ·
There is no doubt in my mind about the BSOD dates as mentioned by DT Roberts based on the files provided to us - look at the dates on the 44 dump files - they begin on July 16, 2009 -
Code:
[font=lucida console]
 Volume in drive A is New Volume
 Volume Serial Number is B8F7-2140

 Directory of A:\D\!!_Kernel_Dumps\dom6663_Vista_12-07-09__jcgriff2__\!_Kernel

07/16/2009  11:05 PM           262,144 071709-16099-01.dmp
07/16/2009  11:06 PM           262,144 071709-17269-01.dmp
07/16/2009  11:13 PM           262,144 071709-16208-01.dmp
07/16/2009  11:15 PM           262,144 071709-23680-01.dmp
07/16/2009  11:17 PM           262,144 071709-23696-02.dmp
07/16/2009  11:32 PM           262,144 071709-21637-01.dmp
07/17/2009  12:10 AM           262,144 071709-18189-01.dmp
07/17/2009  12:13 AM           262,144 071709-13743-01.dmp
07/17/2009  12:22 AM           262,144 071709-16239-01.dmp
07/17/2009  12:50 AM           262,144 071709-16692-01.dmp
07/17/2009  12:53 AM           262,144 071709-15787-01.dmp
07/17/2009  01:05 AM           262,144 071709-14960-01.dmp
07/17/2009  01:17 AM           262,144 071709-17955-01.dmp
07/17/2009  01:43 AM           262,144 071709-14414-01.dmp
07/17/2009  02:13 AM           262,144 071709-27705-01.dmp
07/17/2009  02:27 AM           262,144 071709-20014-01.dmp
07/17/2009  02:28 AM           262,144 071709-20888-01.dmp
07/17/2009  02:30 AM           262,144 071709-24804-01.dmp
07/17/2009  03:59 AM           262,144 071709-18579-01.dmp
07/18/2009  12:25 AM           262,144 071809-12246-01.dmp
07/18/2009  12:46 AM           262,144 071809-12277-01.dmp
07/18/2009  12:52 AM           262,144 071809-13150-01.dmp
07/18/2009  01:46 AM           262,144 071809-15272-01.dmp
07/18/2009  02:02 AM           262,144 071809-22370-01.dmp
07/18/2009  02:03 AM           262,144 071809-23337-01.dmp
07/18/2009  02:09 AM           262,144 071809-22557-01.dmp
11/05/2009  09:58 PM           284,744 110509-29452-01.dmp
11/06/2009  07:24 PM           283,144 110609-27752-01.dmp
11/06/2009  07:34 PM           283,224 110609-29359-01.dmp
11/06/2009  08:03 PM           284,248 110609-20436-01.dmp
11/06/2009  08:45 PM           283,784 110609-24554-01.dmp
11/06/2009  08:46 PM           262,144 110609-21434-01.dmp
12/05/2009  03:40 PM           262,144 120509-22666-01.dmp
12/05/2009  03:51 PM           262,144 120509-22058-01.dmp
12/05/2009  03:53 PM           262,144 120509-22729-01.dmp
12/05/2009  03:56 PM           262,144 120509-22698-01.dmp
12/05/2009  03:56 PM           262,144 120509-23212-01.dmp
12/05/2009  05:07 PM           262,144 120509-16551-01.dmp
12/06/2009  09:10 AM           301,878 120609-15397-01.dmp
12/06/2009  09:32 AM           301,878 120609-14944-01.dmp
12/06/2009  09:50 AM           301,878 120609-16348-01.dmp
12/06/2009  10:18 AM           301,878 120609-15100-01.dmp
12/06/2009  10:21 AM           301,878 120609-14679-01.dmp
12/06/2009  10:41 AM           262,144 120609-15740-01.dmp
              44 File(s)     11,841,430 bytes
               0 Dir(s)  76,388,216,832 bytes free[/font]

jcgriff2

.
Just got in contact with geeks.com tech support, they said it was more likely a hard drive issue. Still available for warranty return. More then likely solved. Thank you for all your help guys, much appreciated.
 

·
Administrator, Manager, Microsoft Support, MVP
Joined
·
34,403 Posts
One thing still bothers me then - why the July 2009 dumps... where did they come from?

One reason - Windows 7 RTM 7600 was "somehow" installed on top of Windows 7 RC 7100 - or even Windows 7 Beta 7000.

Another reason - your version of Windows 7 RTM 7600 is suspect - please be careful about that. You didn't go to all of the trouble you did to get your system together to have a bad OS ruin things for you by causing you to spend time trying to solve something that is not solvable.

Always validate your Windows installation -

www.microsoft.com/genuine

Lastly - I can tell you without reservation that those July dumps are in fact from a Windows 7 OS - and not from a Vista OS.

I wish you the best of luck.

Regards. . .

jcgriff2

.
 

·
Registered
Joined
·
20 Posts
Discussion Starter · #14 ·
One thing still bothers me then - why the July 2009 dumps... where did they come from?

One reason - Windows 7 RTM 7600 was "somehow" installed on top of Windows 7 RC 7100 - or even Windows 7 Beta 7000.

Another reason - your version of Windows 7 RTM 7600 is suspect - please be careful about that. You didn't go to all of the trouble you did to get your system together to have a bad OS ruin things for you by causing you to spend time trying to solve something that is not solvable.

Always validate your Windows installation -

www.microsoft.com/genuine

Lastly - I can tell you without reservation that those July dumps are in fact from a Windows 7 OS - and not from a Vista OS.

I wish you the best of luck.

Regards. . .

jcgriff2

.
I think i can explain the bsod back from july. Probably in a rush while resetting the cmos battery thousands of times i didnt set the date and time properly. therefore it registered as somthing in july rather then in december or november, and i got it properly valadated. i think o.o

Validation Complete!
Thank you for completing the validation process and for using genuine Microsoft software.

By using genuine Microsoft software, you can be confident that you will have access to the latest features, security, and support, which will help to improve your productivity and expand the capabilities of your computer.

You will also have access to new innovations and offerings available only to genuine Microsoft software customers.
 
1 - 14 of 14 Posts
Status
Not open for further replies.
Top