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

·
Registered
Joined
·
85 Posts
Discussion Starter · #1 · (Edited)
ok so about 2 months ago i got the blue screen of death, i kept an eye on my computer to see if it happened again and it didnt for around a month. I thought it musn't be a big problem since there was a decent time frame between them, anyway another month and today i got the blue screen of death again in the middle of watching a movie. it restarted and when i logged in it froze on the welcome screen, i restarted again in safe mode with networking so i ask you guys if you have any idea whats going on!! i would take it into the shop but im a bit strapped for cash at the moment and was wondering if there are some diagnostics i can run myself?

any help is really appreciated thanx :)

p.s. im running windows 7
 

·
Registered
Joined
·
1,553 Posts
Re: blue screen of death/freezing

Hi damo125,

Could you also give us your full system specs as well. If you are unsure what your specs are, download and run Speccy, then when it's generated the information (about 10 seconds) go File>Save as text file, and attach that as well.

Could you also tell us what PSU (Powers Supply Unit) you have and what wattage it is. To find this out, turn off the computer and open it up and look for a label on it. It should tell you the make and wattage there.

Another thing you should also do is to run a test on your RAM sticks with memtest86+ There are two ways to run the test, either from a CD or USB. You will need to burn the ISO to a CD and then boot to the CD and run at least 7 passes on each stick and in each slot (only the ones that are being used). There is an auto-installer for doing it via USB (again, you will have to change the boot order to boot to the USB if you choose this method)

Both downloads can be found halfway down the page. The reason that you should run it on one stick at a time, is so, if there is a fault with one of the sticks, then it's easy to figure out which one it is.

Can you check you Device Manager for any warnings (yellow exclamation points)
Right click on 'My Computer' and select 'Manage'. In the Computer Management window, select 'Device Manager' on the left and look for any warning signs.

You could also try to run a chkdsk /r.

1] First way Windows Key+R and type CMD and hit Enter. At the command prompt type 'chkdsk /r' (without the quotes) and hit Enter. (it may ask you to reboot, so press Y and then Enter)

2] Second Way Go My Computer and Right click on Local Disk (C:) and select 'Properties'. Then under the 'Tools' tab click on 'Check Now' next to Error Checking. In the small window that opens put a tick in both boxes and press 'Start'. It will say 'Windows can't check the disk while in use'. Just click 'Schedule disk check' and then OK. Reboot, and it will run on the next startup. This will check and try to fix any bad sectors on your hard disk.

I know that may seem a lot, but it's best to be thorough.
 

·
Registered
Joined
·
85 Posts
Discussion Starter · #3 ·
hey my system specs should be under that little 'my system' tab below my name shouldnt they? if not my MOBO is an asus pq5l-pro, PSU is a corsair tx-650, graphics is a ge-force 9600gt, processor is a core 2 DUO E8500, ram is 4gb corsair, and harddrive is a seagate 1tb drive.

I've run the chkdsk before after i got the blue screen the second time and it didnt find anything but ill run it again to make sure, ill also try to the test the ram like u suggested. Device manager has no warnings either.

Thanx for the help ill run chkdsk in the morning and test my ram :D will let you know how i go thanx again
 

·
Registered
Joined
·
85 Posts
Discussion Starter · #4 ·
ok ive run the chkdsk and now ive just finished testing each of the RAM sticks individually, i let it go through at least 7 passes and there were no errors. Anything else i can test? video card etc?

thanx :)
 

·
Registered
Joined
·
1,553 Posts
Hi damo125,

Was the last time you had the error on 04-11-2011?

Can you let us know of any errors in red that show in your Event Log:-
Windows Key+R and type eventvwr.msc into the box and hit Enter. Click on 'System' on the left and then click on the 'Type' tab at the top to sort the errors into their categories. (easier to find). Where there are ones in red that relate to the time/ date area of the blue screens/ freezes, can you tell us the EventID and Source for each one (most regular ones). Action>Export List and save it as a .txt file and attach it back.
 

·
Registered
Joined
·
85 Posts
Discussion Starter · #7 ·
nah im almost certain that the blue screen and the freezing was on the 8th of april so 04-08-11

i checked the critical events on this date and there are a couple on the day, source: 'kernel power' event ID: '41'

i've also attached the event logs in text format
 

Attachments

·
Registered
Joined
·
1,553 Posts
Hi damo125,

The "kernel power' event ID: '41'" is produced when the system shuts down unexpectedly (power loss, crashing, system stopped responding etc), but I still can't get a good idea as to why. Your HDD and RAM have both passed their tests and your PSU is a good make and wattage (can't count out a power failure though)

Can you also down load this http://sysnative.com/0x8/BSOD_Windows7_Vista_v2.64_jcgriff2_.exe
and post back the results. Zip the outputted Windows7_Vista_jcgriff2 folder in My Documents and post back. You must right click on the downloaded file and choose 'Run as administrator'. It's a program written by the forums manager jcgriff2 here, and is a very good tool for isolating the reasons for the BSoD's. It may several mins to run.

Can you also do this:
Run System Health Report -
START | type perfmon /report | save as HTML file and attach that as well.

Can you download and install Autoruns and run it. Let it generate all the information (shouldn't take long) then go File>Save and save the AutoRuns.arn file to the desktop. Zip it (right click on the .arn file and select 'send to' and choose 'Compressed zipped folder) and attach it back. Basically want to have a look and see if we can figure out what may be interfering.

As for testing your video card, you should Benckmark it using FurMark.
 

·
TSF Team Emeritus
Joined
·
6,147 Posts
Hi,

Your wired networking driver (L1E62x64.sys) is blamed for a lot of your BSODs.

Update it from Asus - ASUSTeK Computer Inc. -Support- Drivers and Download

If that fails to solve it then please run this CPU stress test: CPU - Stress Test with Prime95 - Windows 7 Forums (run the Blend test as well as the SmallFFTs test)

BUGCHECK SUMMARY
Code:
[font=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Apr 11 16:32:20.002 2011 (GMT+12)
System Uptime: 0 days 0:00:27.627
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`039578f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Apr 11 16:01:25.949 2011 (GMT+12)
System Uptime: 0 days 4:37:20.619
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+7e2e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_L1E62x64+7e2e
Bugcheck code 0000000A
Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`02c177f7
SystemProductName = P5QL PRO
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Apr  8 18:35:39.529 2011 (GMT+12)
System Uptime: 0 days 7:29:53.199
BugCheck D1, {32, 2, 0, fffff8800165b87a}
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+7bcb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_L1E62x64+7bcb
Bugcheck code 000000D1
Arguments 00000000`00000032 00000000`00000002 00000000`00000000 fffff880`0165b87a
SystemProductName = P5QL PRO
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Apr  1 11:35:42.697 2011 (GMT+12)
System Uptime: 0 days 1:06:31.367
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+7e2e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_L1E62x64+7e2e
Bugcheck code 0000000A
Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`031e27f7
SystemProductName = P5QL PRO
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar 29 12:49:19.914 2011 (GMT+12)
System Uptime: 0 days 0:34:05.584
BugCheck D1, {32, 2, 0, fffff880016e687a}
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+7bcb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_L1E62x64+7bcb
Bugcheck code 000000D1
Arguments 00000000`00000032 00000000`00000002 00000000`00000000 fffff880`016e687a
SystemProductName = P5QL PRO
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Mar 20 16:40:44.829 2011 (GMT+12)
System Uptime: 0 days 7:56:32.972
BugCheck D1, {32, 2, 0, fffff880016d387a}
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+7bcb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xD1_L1E62x64+7bcb
Bugcheck code 000000D1
Arguments 00000000`00000032 00000000`00000002 00000000`00000000 fffff880`016d387a
SystemProductName = P5QL PRO
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Mar  1 11:09:48.554 2011 (GMT+12)
System Uptime: 0 days 0:49:14.224
BugCheck D1, {32, 2, 0, fffff880016e687a}
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+7bcb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_L1E62x64+7bcb
Bugcheck code 000000D1
Arguments 00000000`00000032 00000000`00000002 00000000`00000000 fffff880`016e687a
SystemProductName = P5QL PRO
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Feb 24 11:13:17.081 2011 (GMT+12)
System Uptime: 0 days 0:00:18.751
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`053cd8f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Feb 22 14:01:06.355 2011 (GMT+12)
System Uptime: 0 days 3:40:19.025
BugCheck D1, {32, 2, 0, fffff8800169587a}
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+7bcb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_L1E62x64+7bcb
Bugcheck code 000000D1
Arguments 00000000`00000032 00000000`00000002 00000000`00000000 fffff880`0169587a
SystemProductName = P5QL PRO
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Feb 20 16:21:45.852 2011 (GMT+12)
System Uptime: 0 days 5:05:16.300
BugCheck D1, {32, 2, 0, fffff8800163e87a}
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+7bcb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_L1E62x64+7bcb
Bugcheck code 000000D1
Arguments 00000000`00000032 00000000`00000002 00000000`00000000 fffff880`0163e87a
SystemProductName = P5QL PRO
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Feb 17 19:57:02.155 2011 (GMT+12)
System Uptime: 0 days 9:21:48.825
BugCheck D1, {32, 2, 0, fffff880016cf87a}
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+7bcb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_L1E62x64+7bcb
Bugcheck code 000000D1
Arguments 00000000`00000032 00000000`00000002 00000000`00000000 fffff880`016cf87a
SystemProductName = P5QL PRO
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Jan 29 11:39:56.676 2011 (GMT+12)
System Uptime: 0 days 0:00:08.346
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0522a8f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Jan 29 11:25:18.056 2011 (GMT+12)
System Uptime: 0 days 0:00:14.726
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0521f828 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Jan 29 11:22:51.044 2011 (GMT+12)
System Uptime: 0 days 0:00:12.714
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`051bb608 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan 23 08:55:09.692 2011 (GMT+12)
System Uptime: 0 days 0:00:17.362
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`052196e8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Dec 14 14:27:17.875 2010 (GMT+12)
System Uptime: 0 days 0:00:10.545
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`052c98f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/font]
 

·
Registered
Joined
·
85 Posts
Discussion Starter · #13 ·
awesome! i updated the drivers, i just updated the LAN drivers is that all i need to update?? theres one about intel chipset but i have no idea what that is lol?
 

·
Registered
Joined
·
85 Posts
Discussion Starter · #15 ·
no havent had any more blue screens which is a good sign i suppose haha, and yeh will run the stress test when i dont need my computer (i saw that you need to leave it to run for 6 hours) what does the stress test do just see if the CPU has any issues?
 

·
Registered
Joined
·
85 Posts
Discussion Starter · #17 ·
Re: [SOLVED] blue screen of death/freezing (Moved from Vista/7)

ok so i thought everything was ok but im writing to u again just after another blue screen, this time i made sure to note the exact time it happened. Should i do all those event files etc again?
 

·
Registered
Joined
·
85 Posts
Discussion Starter · #19 ·
ran the stress test for 8 hours and it found no errors, i havent had a blue screen for a fair while but i get freezes at least once a week, the freeze usually occurs after the screen saver has activated so the screen is black and then i cant do anything aka its frozen so i have to restart...
 
1 - 19 of 19 Posts
Status
Not open for further replies.
Top