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: getting BSODs on Windows 7 64 bit

03 Nov 2009   #21
usasma
Microsoft MVP

 
 

Errors are still widely spread. Please do as H2SO4 suggests and run MemTest overnight.
Make sure the system is not overheating - if you must, open up the case and point a house fan into it.

As for the PSU - that's your call. I'm no PSU expert - but if it is the PSU, then it most likely won't show up in the memory test (because that doesn't use that much power).

Can you borrow a more powerful PSU to experiment with? Can you purchase one from a shop with a good return policy? That way, if it's not the PSU - then you can return the new PSU and get your money back.

Here's the summary of the memory dumps:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Oct 28 17:14:19.729 2009 (GMT-5)
System Uptime: 0 days 0:03:41.337
BugCheck 3B, {c0000005, fffff96000128d23, fffff8800a330340, 0}
Probably caused by : win32k.sys ( win32k!GetStyleWindow+13 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  digsby-app.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Oct 31 20:33:08.535 2009 (GMT-5)
System Uptime: 0 days 0:44:22.128
BugCheck 3B, {c0000005, fffff80002c0a327, fffff8800a765d90, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+277 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  iexplore.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov  1 09:43:33.025 2009 (GMT-5)
System Uptime: 0 days 13:09:46.007
BugCheck 34, {50830, fffff8800317e8a8, fffff8800317e100, fffff880012e2f9d}
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireScbForLazyWrite+25 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Oct 31 19:16:58.659 2009 (GMT-5)
System Uptime: 1 days 1:57:28.641
BugCheck 1A, {5003, fffff70001080000, 8c19, 665000011c32}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21bc6 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  iexplore.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov  2 11:40:34.597 2009 (GMT-5)
System Uptime: 1 days 0:44:37.201
BugCheck 3B, {c0000005, fffff80002bae327, fffff88008b53f80, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+277 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  SearchProtocol
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Nov  3 10:04:37.061 2009 (GMT-5)
System Uptime: 0 days 12:19:55.653
BugCheck 3B, {c0000005, fffff80002ab9c9b, fffff88008ca9f20, 0}
Probably caused by : memory_corruption ( nt!MiGetNextNode+43 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov  2 21:41:06.952 2009 (GMT-5)
System Uptime: 0 days 9:59:35.544
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {fffff980532f04e0, fffff8800ff34f80, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+10cf80 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System



My System SpecsSystem Spec
.
28 Nov 2009   #22
yairco

Windows 7 Ultimate 64 bit
 
 

hey guys, its me again...
quick update - I did a full memtest that came back with no errors.
I've also decided to upgrade my GPU card (GTX 275) so in the same time I upgraded
my PSU (Crosair 750W).

I still keep on getting BSODs, some I haven't seen before...
all my drivers are updated..

any leads ?
My System SpecsSystem Spec
29 Nov 2009   #23
usasma
Microsoft MVP

 
 

Please turn off Driver Verifier by following the instructions posted by H2SO4:

Quote   Quote: Originally Posted by H2SO4 View Post
....

Another of the crashes indicates a condition known as pool corruption. To try to catch the culprit at the point where it does the damage, on an elevated (run as admin) CMD prompt:

VERIFIER /FLAGS 1 /ALL
<reboot>

Please upload any minidumps from subsequent crashes for analysis.

Afterwards, when this is all over, go back to default settings by running:

VERIFIER /RESET
Please update or remove your Entech PowerStrip software. The driver is very old and could be causing issues due to incompatibility.
Code:
ENTECH64.sys Fri Mar 26 07:44:04 2004
The most significant thing (IMO) is the cause of the 3rd minidump (eamon.sys). This is a component of ESET NOD32 - and we've seen some issues with it recently. Please do the following:
- download a free antivirus for protection while testing (I suggest the free Microsoft Security Essentials: http://www.microsoft.com/Security_Essentials/ )
- uninstall the ESET NOD32 software from Control Panel...Programs...Uninstall a program
- run the ESET removal tool: ESET Knowledgebase - How do I manually uninstall my ESET security product?
- install the free antivirus and update it immediately.
- test to see if the BSOD's recur.

Summary of the memory dump analysis':
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Nov 25 12:26:38.902 2009 (GMT-5)
System Uptime: 0 days 6:12:53.884
BugCheck A, {8, 2, 0, fffff80002d9050b}
Probably caused by : memory_corruption ( nt!MiStoreSetEvictPageFile+b )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  b.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Nov 24 21:41:14.880 2009 (GMT-5)
System Uptime: 0 days 16:19:48.862
BugCheck 1000007E, {ffffffffc0000005, fffff80002df9327, fffff880031a88a8, fffff880031a8100}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+277 )
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Nov 27 16:33:26.767 2009 (GMT-5)
System Uptime: 0 days 0:41:24.749
BugCheck 1A, {5003, fffff780c0000000, 4d94, 4dc500009f28}
*** WARNING: Unable to verify timestamp for eamon.sys
*** ERROR: Module load completed but symbols could not be loaded for eamon.sys
Probably caused by : eamon.sys ( eamon+6783 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  chrome.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Nov 28 19:25:28.351 2009 (GMT-5)
System Uptime: 0 days 1:02:44.334
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpProcessInterruptReport+20 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  GTAIV.exe
My System SpecsSystem Spec
.

14 Dec 2009   #24
yairco

Windows 7 Ultimate 64 bit
 
 

quick update... I added another HD to my pc..
I formated the computer and reinstalled all the updated drivers.
I typed the Verifier cmd line and got straight 16 BSDOS in less than 24 hrs...
what I dont understand is why on a x86 os (I tried 7 and vista) everything works,
I would have use those OS long time ago but I don't want to lose the usage of my RAM memorey (4GB)
what do u think?

regards,

Yair
My System SpecsSystem Spec
14 Dec 2009   #25
usasma
Microsoft MVP

 
 

4 gB of RAM is the break even point for using 32 or 64 bit. What little you gain by using 64 bit is offset (IMO) by the loss due to the overhead of processing the extra address space.

Quote:
Less than 4 gB = use 32 bit
4 gB = use either one
More than 4 gB = use 64 bit
More to follow when the dump files finish percolatin'
My System SpecsSystem Spec
14 Dec 2009   #26
usasma
Microsoft MVP

 
 

Lot's of errors - memory, video, storage.

Try this free test for your hard drive: HD Diagnostic
Beyond that, if this is a new video card - try another one in case it's broke.
If the video card comes out OK, then I'd expect that there was a problem with the motherboard.

Here's the summary of the analysis':
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 11:09:52.768 2009 (GMT-5)
System Uptime: 0 days 0:00:39.329
BugCheck 1A, {1236, fffffa8004fed640, fffffa8004fed6e8, 108bdd}
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 14:24:51.237 2009 (GMT-5)
System Uptime: 0 days 0:00:33.798
BugCheck 1E, {ffffffff80000003, fffffa80065197e9, 0, fffff88007f96138}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+460da )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  spoolsv.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 11:19:42.767 2009 (GMT-5)
System Uptime: 0 days 0:00:20.328
BugCheck 1A, {41287, 700000017, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42c75 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 11:36:46.144 2009 (GMT-5)
System Uptime: 0 days 0:03:17.095
BugCheck 3B, {c0000005, fffff80002b84b9b, fffff880096a5040, 0}
Probably caused by : ntkrnlmp.exe ( nt!PspDereferenceQuotaBlock+17 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchFilterHo
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 14:23:51.612 2009 (GMT-5)
System Uptime: 0 days 0:02:40.173
BugCheck 3B, {c0000005, fffff80002aafc75, fffff88007c5f090, 0}
Probably caused by : memory_corruption ( nt!MiGetNextNode+15 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 16:24:46.439 2009 (GMT-5)
System Uptime: 0 days 0:01:55.390
BugCheck 1E, {ffffffffc0000005, fffff80002d66f2e, 0, 30}
Probably caused by : memory_corruption ( nt!MiFindEmptyAddressRangeDownTree+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 16:21:58.333 2009 (GMT-5)
System Uptime: 0 days 1:35:33.283
BugCheck 1A, {41287, 400, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42c75 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  digsby-app.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 20:49:42.000 2009 (GMT-5)
System Uptime: 0 days 0:49:15.560
BugCheck A, {0, 2, 1, fffff80002a7b1a4}
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+314 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec 14 08:23:55.399 2009 (GMT-5)
System Uptime: 0 days 0:13:54.960
BugCheck D1, {0, 2, 0, fffffa800655bb96}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  rundll32.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 19:12:50.608 2009 (GMT-5)
System Uptime: 0 days 0:27:33.559
BugCheck 1E, {ffffffffc0000005, fffff88009e0b220, 0, 0}
Probably caused by : NETIO.SYS ( NETIO!KfdClassify+54c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 17:18:48.718 2009 (GMT-5)
System Uptime: 0 days 0:53:38.279
BugCheck 3B, {c0000005, fffff88004e15470, fffff88007237140, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+59a470 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dirt2_game.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 18:41:03.311 2009 (GMT-5)
System Uptime: 0 days 0:52:47.873
BugCheck 3B, {c0000005, fffff8800499242a, fffff88008e6f590, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+17b42a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dirt2_game.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 18:44:53.040 2009 (GMT-5)
System Uptime: 0 days 0:03:25.601
BugCheck 1A, {41287, 2d2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42c75 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec 14 07:51:00.349 2009 (GMT-5)
System Uptime: 0 days 0:25:37.300
BugCheck 19, {3, fffffa80046e57e0, fffff8a0039adbc0, fffffa80046e57e0}
Probably caused by : Pool_Corruption ( nt!ExFreePool+780 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 17:47:50.204 2009 (GMT-5)
System Uptime: 0 days 0:28:36.767
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BugCheck 1000007E, {ffffffffc0000005, fffff88004998c65, fffff880037f3858, fffff880037f30b0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+184c65 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 20:00:01.352 2009 (GMT-5)
System Uptime: 0 days 0:46:42.302
BugCheck 3B, {c0000005, fffff880010e0b07, fffff8800943e9b0, 0}
Probably caused by : fltmgr.sys ( fltmgr!FltpGetStartingCallbackNode+97 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wsqmcons.exe
My System SpecsSystem Spec
23 Dec 2009   #27
yairco

Windows 7 Ultimate 64 bit
 
 

I swapped my os to 32 bit and the BSODs started to appear again (I guess that I just didnt spent enough time with it).
I tried 2 diffrent programs to check the hardware like HD Tune Pro and another one that I can't really remember the name, nothing turned up. the GPU is brand new and the BSODS came before the upgrade.
You suggested the problem may be with the motherboard, is there a certain way to verify it ? (other than replacing ofcourse.. ) also, I got some new randoms BSODs lately, maybe they can point a way out ??
My System SpecsSystem Spec
23 Dec 2009   #28
usasma
Microsoft MVP

 
 

There are no tests to verify the motherboard 100%. There are tests that will check certain areas of the motherboard - but they cost about $800 (US). And they're not 100% accurate.

Cheaper to replace the mobo as a test then.

Try ripping out everything else before spending money. Here's a post that may give some hints on how to proceed: Hardware Troubleshooting Via System Stripdown
My System SpecsSystem Spec
Reply

 getting BSODs on Windows 7 64 bit




Thread Tools




Similar help and support threads
Thread Forum
BSODS on Windows 7
Hi. I'm having BSOD-s on my pc and can't figure out what's wrong. I've tested my RAM (MEMTEST+) / HDD (HD TUNE 5) and run Prime95 with FurMark with no problems (15 min). I got BSOD-s especially when playing. Specs : AMD X4 945 Phenom 3 x 2GB DDR3 Corsair XMS 2 x HDD SATA2 NVIDIA 460 GTX (1...
BSOD Help and Support
Windows 7 BSODs
Hi, since 2 weeks i'm going through a BSOD disaster, appearing everytime and disturbing my works. I have attached some files and hope there will be someone who can help to fix it definetly. kind regards
BSOD Help and Support
BSODs on windows 7 and xp
Hi I had BSODs on my windows 7 so I decided to install xp and see whether it will help. It didn't. BSODs occur randomly, sometimes once a weak, sometimes every day. I provided .dmp files from windows 7 and xp. Please help me solve this problem.
BSOD Help and Support
BSODs in Windows 7 HP x64
I just finished building this system last week and I keep getting BSODs at seemingly random times. Here's the system info: Windows 7 Home Professional x64 OEM AMD Phenom II X4 965 Gigabyte G880GA-UD3H G.Skill 2x2GB DDR3 1600 WD Caviar Black 1TB Dump files attached. I'd appreciate any...
BSOD Help and Support
I'm getting BSODs on my Windows 7 too.
Well I used to.. until I installed Vista back on my laptop to figure out what the problem is with my laptop is with BSODs happening to me every one in a while when Windows 7 Home Premium 64 was installed on my laptop. I don't have the mini dump file for the BSOD errors but I do have photos of...
BSOD Help and Support


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 22:43.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App