Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: New installation of Windows 7 and now Blue Screens

07 Feb 2012   #1
celles23

Win 7 x64 Ultimate
 
 
New installation of Windows 7 and now Blue Screens

Hello,

i have recently installed a fresh win7 x64 Ultimate on my Girlfrieds Laptop. Now it happens time and time again that the computer shows a blue Screen and restarts.

There is no specific application running when its happening, it rather hapens in a random manner.
The dump files are attached in this post.

Thanks alot


My System SpecsSystem Spec
.
07 Feb 2012   #2
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [F:\BSODDmpFiles\celles23\020712-44741-01 - Kopie.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02809000 PsLoadedModuleList = 0xfffff800`02a4e670 Debug session time: Tue Feb 7 05:01:30.753 2012 (GMT-7) System Uptime: 0 days 3:22:17.719 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {3, fffff8a009965430, ffffe8a009965430, fffff8a009965430} Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+118b ) Followup: Pool_corruption --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 0000000000000003, the pool freelist is corrupt. Arg2: fffff8a009965430, the pool entry being checked. Arg3: ffffe8a009965430, the read back flink freelist value (should be the same as 2). Arg4: fffff8a009965430, the read back blink freelist value (should be the same as 2). Debugging Details: ------------------ BUGCHECK_STR: 0x19_3 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800029b3b73 to fffff80002885c40 STACK_TEXT: fffff880`03124a38 fffff800`029b3b73 : 00000000`00000019 00000000`00000003 fffff8a0`09965430 ffffe8a0`09965430 : nt!KeBugCheckEx fffff880`03124a40 fffff800`0284ca52 : 00000000`00000000 fffff8a0`09965400 fa800725`74536d4d fffff800`00000000 : nt!ExDeferredFreePool+0x118b fffff880`03124af0 fffff800`02b2525f : fffffa80`07256800 00000000`00000011 00000000`00088081 fffffa80`041bea10 : nt!MiDeleteSegmentPages+0x112 fffff880`03124bc0 fffff800`028d318d : fffffa80`07256808 00000000`00000001 00000000`00000000 10000000`00000631 : nt!MiSegmentDelete+0x7b fffff880`03124c00 fffff800`028d3051 : 00000000`00000000 00000000`00000080 fffffa80`03cd1040 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131 fffff880`03124cc0 fffff800`02b20fee : 37b96dbc`f9ffffcf 40118000`02000210 1f6f3bff`fffffff7 01200b13`11990134 : nt!MiDereferenceSegmentThread+0x10d fffff880`03124d40 fffff800`028775e6 : fffff800`029fbe80 fffffa80`03cdf270 fffff800`02a09cc0 01003002`20101120 : nt!PspSystemThreadStartup+0x5a fffff880`03124d80 00000000`00000000 : fffff880`03125000 fffff880`0311f000 fffff880`031247f0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!ExDeferredFreePool+118b fffff800`029b3b73 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!ExDeferredFreePool+118b FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+118b BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+118b Followup: Pool_corruption ---------
  2. Loading Dump File [F:\BSODDmpFiles\celles23\020612-36785-01 - Kopie.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02812000 PsLoadedModuleList = 0xfffff800`02a57670 Debug session time: Mon Feb 6 14:53:15.132 2012 (GMT-7) System Uptime: 0 days 1:55:49.098 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff89bbcddddb8, 0, fffff80002ceab11, 5} Could not read faulting driver name Probably caused by : ntkrnlmp.exe ( nt!PfSnPrefetchSections+351 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff89bbcddddb8, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff80002ceab11, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ac1100 fffff89bbcddddb8 FAULTING_IP: nt!PfSnPrefetchSections+351 fffff800`02ceab11 418b448808 mov eax,dword ptr [r8+rcx*4+8] MM_INTERNAL_CODE: 5 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: SearchFilterHo CURRENT_IRQL: 0 TRAP_FRAME: fffff88008438490 -- (.trap 0xfffff88008438490) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffffffa47004c0 rbx=0000000000000000 rcx=fffffffeed500e40 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002ceab11 rsp=fffff88008438620 rbp=fffff88008438740 r8=fffff8a0079da4b0 r9=00000000a47004c0 r10=0000000000000001 r11=0000000000000001 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe cy nt!PfSnPrefetchSections+0x351: fffff800`02ceab11 418b448808 mov eax,dword ptr [r8+rcx*4+8] ds:0240:fffff89b`bcddddb8=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800028393bf to fffff8000288ec40 STACK_TEXT: fffff880`08438328 fffff800`028393bf : 00000000`00000050 fffff89b`bcddddb8 00000000`00000000 fffff880`08438490 : nt!KeBugCheckEx fffff880`08438330 fffff800`0288cd6e : 00000000`00000000 fffff89b`bcddddb8 fffff880`08438700 00000000`0000002c : nt! ?? ::FNODOBFM::`string'+0x44791 fffff880`08438490 fffff800`02ceab11 : 00000000`00000002 fffff8a0`014f7e60 fffff880`084386c0 00000000`0000002c : nt!KiPageFault+0x16e fffff880`08438620 fffff800`02ceae1d : fffff880`08438740 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PfSnPrefetchSections+0x351 fffff880`08438710 fffff800`02ceb25f : 00000000`a5923e75 fffffa80`0689e9b0 fffff8a0`079da000 00000000`00000000 : nt!PfSnPrefetchScenario+0x16d fffff880`08438980 fffff800`02bea2df : 00000000`00000000 00000000`77482212 fffffa80`06d50170 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f fffff880`08438a50 fffff800`02b7cfb8 : fffffa80`0483bb60 fffffa80`06d50170 00000000`14050800 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x513d0 fffff880`08438a80 fffff800`02880715 : fffff880`009ea180 00000000`00000000 fffff800`02b7ce70 fffffa80`0483bb60 : nt!PspUserThreadStartup+0x148 fffff880`08438ae0 fffff800`02880697 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16 fffff880`08438c20 00000000`76e1c500 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn 00000000`000bff28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e1c500 STACK_COMMAND: kb FOLLOWUP_IP: nt!PfSnPrefetchSections+351 fffff800`02ceab11 418b448808 mov eax,dword ptr [r8+rcx*4+8] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!PfSnPrefetchSections+351 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x50_nt!PfSnPrefetchSections+351 BUCKET_ID: X64_0x50_nt!PfSnPrefetchSections+351 Followup: MachineOwner ---------
  3. Loading Dump File [F:\BSODDmpFiles\celles23\020612-46597-01 - Kopie.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02805000 PsLoadedModuleList = 0xfffff800`02a4a670 Debug session time: Mon Feb 6 12:56:54.122 2012 (GMT-7) System Uptime: 0 days 1:40:59.089 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff8a01e16f298, 0, fffff800028add4c, 2} Could not read faulting driver name Probably caused by : memory_corruption ( nt!MmCopyToCachedPage+1dc ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff8a01e16f298, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff800028add4c, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ab4100 fffff8a01e16f298 FAULTING_IP: nt!MmCopyToCachedPage+1dc fffff800`028add4c 488b38 mov rdi,qword ptr [rax] MM_INTERNAL_CODE: 2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: msiexec.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88002bc0270 -- (.trap 0xfffff88002bc0270) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8a01e16f298 rbx=0000000000000000 rcx=0000000fffffffff rdx=fffff9801d611000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800028add4c rsp=fffff88002bc0400 rbp=fffff88002bc0440 r8=0000098000000000 r9=0000000004f45d65 r10=0000058000000000 r11=fffff88002bc0388 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc nt!MmCopyToCachedPage+0x1dc: fffff800`028add4c 488b38 mov rdi,qword ptr [rax] ds:fffff8a0`1e16f298=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000282c3f0 to fffff80002881c40 STACK_TEXT: fffff880`02bc0108 fffff800`0282c3f0 : 00000000`00000050 fffff8a0`1e16f298 00000000`00000000 fffff880`02bc0270 : nt!KeBugCheckEx fffff880`02bc0110 fffff800`0287fd6e : 00000000`00000000 fffff8a0`1e16f298 fffff800`02a09e00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x447c6 fffff880`02bc0270 fffff800`028add4c : 00000000`00000002 ffffffff`ffffffff 00000000`00000002 ffffffff`ffffffff : nt!KiPageFault+0x16e fffff880`02bc0400 fffff800`028aae3e : fffff980`1d611000 00000000`04f45d65 fffff880`00000000 00000000`00001000 : nt!MmCopyToCachedPage+0x1dc fffff880`02bc05f0 fffff800`028ab3f4 : fffffa80`040b48c0 00000000`04f45d65 fffff880`02bc0730 fffff880`00000000 : nt!CcMapAndCopyInToCache+0x20e fffff880`02bc06e0 fffff880`012d7c18 : 00000000`000557ab fffffa80`051e1f00 fffff880`02bc07d0 fffffa80`00008000 : nt!CcCopyWrite+0x194 fffff880`02bc0770 fffff880`01156102 : fffffa80`051e1f20 fffff880`011594f2 00000000`00008000 00000000`00008001 : Ntfs!NtfsCopyWriteA+0x208 fffff880`02bc0970 fffff880`011598ba : fffff880`02bc0a40 fffffa80`061aad78 00000000`04f42500 00000000`00008000 : fltmgr!FltpPerformFastIoCall+0xf2 fffff880`02bc09d0 fffff880`0117783e : 00000000`00008000 00000000`00000000 fffffa80`051e1f20 fffff880`02bc0b40 : fltmgr!FltpPassThroughFastIo+0xda fffff880`02bc0a10 fffff800`02b94a4e : fffffa80`051e1f94 fffff800`02b6ba0c fffff880`02bc0ca0 fffffa80`051e1f94 : fltmgr!FltpFastIoWrite+0x1ce fffff880`02bc0ab0 fffff800`02880ed3 : ffffffff`ffffff01 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x5ad fffff880`02bc0bb0 00000000`770a139a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`037ef7b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770a139a STACK_COMMAND: kb FOLLOWUP_IP: nt!MmCopyToCachedPage+1dc fffff800`028add4c 488b38 mov rdi,qword ptr [rax] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MmCopyToCachedPage+1dc FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x50_nt!MmCopyToCachedPage+1dc BUCKET_ID: X64_0x50_nt!MmCopyToCachedPage+1dc Followup: MachineOwner ---------
  1. Possible cause is Drivers...
  2. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...
  3. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...

Thanks to Dave76 for help understanding possible causes.



Update the following drivers from the laptop's support page. If you cannot find them via the support page, let us know the laptop make and model and we will help. The links to where you may find each driver are also provided following the driver listing in the code box.
Code:
mdmxsdk		fffff880`0276f000	fffff880`02773280	Mon Jun 19 15:27:26 2006 (449716be)	00010210		mdmxsdk.sys
xaudio64	fffff880`026f4000	fffff880`026fc000	Tue Nov 28 17:45:04 2006 (456cd810)	000119ab		xaudio64.sys
CAX_CNXT	fffff880`06a00000	fffff880`06ac8000	Fri Dec 22 13:29:46 2006 (458c403a)	000b7009		CAX_CNXT.sys
CAXHWAZL	fffff880`06af8000	fffff880`06b4c000	Fri Dec 22 13:30:47 2006 (458c4077)	00049ff4		CAXHWAZL.sys
CAX_DPV		fffff880`06c26000	fffff880`06da0000	Fri Dec 22 13:33:24 2006 (458c4114)	0017d12a		CAX_DPV.sys
ibmpmdrv	fffff880`03fea000	fffff880`03ff4000	Thu May 31 03:51:31 2007 (465e9aa3)	00007837		ibmpmdrv.sys
netw5v64	fffff880`04a2d000	fffff880`04f68000	Thu Mar 26 10:21:24 2009 (49cbab84)	00533de3		netw5v64.sys
b57nd60a	fffff880`04f68000	fffff880`04fb0000	Sun Apr 26 05:14:55 2009 (49f4422f)	0004c43c		b57nd60a.sys
ADIHdAud	fffff880`05332000	fffff880`053b2000	Mon May 18 11:31:55 2009 (4a119b8b)	000844bd		ADIHdAud.sys
mdmxsdk.sys
xaudio64.sys
CAX_CNXT.sys
CAXHWAZL.sys
CAX_DPV.sys
ibmpmdrv.sys
netw5v64.sys
b57nd60a.sys
ADIHdAud.sys



We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.
  • If you are overclocking any hardware, please stop.


  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
    Once these steps have been followed, it is safe to remove and replace components within your computer.


  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. Run Driver Verifier

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.



Please fill out the laptop specs using the steps in System Info - See Your System Specs. Also, please follow the http://www.sevenforums.com/crashes-d...tructions.html to provide us with more information about the system's hardware, software, event viewer logs, etc.
My System SpecsSystem Spec
07 Feb 2012   #3
celles23

Win 7 x64 Ultimate
 
 

Thanks for the quick reply.
I will install those drivers listed in your message and look if it helps.
My System SpecsSystem Spec
.

27 Feb 2012   #4
writhziden

Windows 7 Home Premium 64 Bit
 
 

Did you get the drivers updated? How is the system running?
My System SpecsSystem Spec
28 Feb 2012   #5
celles23

Win 7 x64 Ultimate
 
 

After the driver update i've tried to install office but the installation failed because of some corrupted archives. Then i have tried to reinstall windows and have gotten an error message just after the partitioning of the hard disk.
That made me belive that it had something to do with the installed memory. After changing the memory the errors disappeared.
Since then the systems running without bluescreens. So in the end it was obviously a hardware issue

Thanks again for the quick response and help !
My System SpecsSystem Spec
28 Feb 2012   #6
writhziden

Windows 7 Home Premium 64 Bit
 
 

You're welcome. Glad you got it sorted.
My System SpecsSystem Spec
Reply

 New installation of Windows 7 and now Blue Screens




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Various Blue Screens of Death after New Hardware Installation
Hi all, I recently installed some new hardware on my computer after my old EVGA 8800GT graphics card died. I installed a new motherboard, graphics card, processor, and RAM Complete specs are in my profile, but the quick and dirty: MB: Asus P8Z77M-Pro w/ i5 @ 3.4GHz GC: EVGA GTX650 2GB SC RAM:...
BSOD Help and Support
Rogue Blue screens/Black screens
And I'm back again giving you another annoying dilemma to help me with. Okay, the problems are on my main pc. The specs are below: Windows 7 Ult. 64bit Gigabyte 880GA-UD3H AMD Phenom II X6 1100T 4GB DDR3 PNY RAM 500GB Seagate HDD Dynex 400 Watt Power Supply
BSOD Help and Support
Windows 7 x64 Blue Screens on a new build
Hey guys, new member here. Any who, I installed Windows 7 Ultimate x64 (legit) onto this computer I was building (first build) Well I've been having some blue screen errors, initially using windbg I had thought I had traced it back to a driver error; So I thought that just for the sake of stability...
BSOD Help and Support
Blue screens, Windows 7, Need your help
Hello I am getting random blue screens, while playing games (All kind, not a specific game) and even while just browsing the net. I really don't know what is causing them, What I did was first opening the case and making sure everything seem OK there, tried reseating the GFX and the memory as...
BSOD Help and Support
Windows 7 64bit RTM Blue Screens
I have seen 2 Blue Screen crashes 7 days apart with what looks like the same cause since I installed Windows 7 64 RTM. These two are the only BSOD crashes I have experienced. This install was a clean install replacing a Windows 7 RC image. I did not experience BSOD crashes with the RC. The crash...
BSOD Help and Support
Installation fail :( blue screens
hi, i m on a amd dual core 5200, abit k9n with latest bios, ati 4830, 2gb ram 800mhz (2x1) i have downloaded from my university win7 x64 version (the free copy for students build 7600) but i have also tryed 2 other versions (rc i think, both 64 and 32) with no success. first of all, the...
Installation & Setup


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 07:48.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App