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: Random BSOD different errors

12 Oct 2011   #1

win 7 pro x64
 
 
Random BSOD different errors

Hi,

i have win 7 pro x64 installed on new computer based on intel chipset.
motherboard is DH61BE
I have downloaded and installed newest drivers from intel website.
Still problem exist. please see attachment.

thanks in advance
Julek

My System SpecsSystem Spec
.

12 Oct 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by julek View Post
Hi,

i have win 7 pro x64 installed on new computer based on intel chipset.
motherboard is DH61BE
I have downloaded and installed newest drivers from intel website.
Still problem exist. please see attachment.

thanks in advance
Julek


1. Run an memtest.
In order to check your ram memory we going need to do a test, Please download an burn one of the following iso's on an disk.
Memtest86

When you burned the iso on an disk, please turn off your computer and put the cd in your computer. After a while you will see a black screen saying "Press any key to...". Press any key.

Now let the test run for 5-6 passes. Every time the program returns an error the memory is corrupted / bad or defect or the motherboard is bad / defect. If this occurs then please test every single ram stick individually. When you find a good one wich returns no errors then please test it in every single slot your computer has.

If you get no errors on all slots at all, then continue to step 2 of this post.

Step 2, Run the windows driver verifier.
Please read the following instructions carefully and execute them like i said.

First make an backup of your important data on your computer, and check if you have an second computer to contact us if the driver verifier goes wrong.

Then make an system restore point, You can do this by:

Open the Start menu

Open the Programs menu

Open the Accessories menu

Open the System Tools menu

Finally, start System Restore

Pick the option for setting a System Restore Point and click on the Next button

Fill in a name for the restore point so you can find it and click on the Create button

Click on the Close button when done


After you done all that please continue with the following steps. Please read them carefully

Click on your Start button (Windows Orb) and typ "verifier" and hit enter
Select the option: "Create Custom Settings ..." and click Next.
Select the option: "Select Individual settings from full list" and click Next.
Select all options except for the option "Low Resource Simulation" and click Next
Select the option: "Select driver names from a list" and click on Next
Then select all drivers EXCEPT for the drivers provided by Microsoft and click next
Then click on finish.

After doing all this reboot your system and wait for it to go to bluescreen, after the BSOD continue to use your computer normally. If you know what causes the BSOD then repeat doing this. if your system doesnt crash then let it run for atleast 48 hours.

It is normal that your system crashes here, This is because windows is stressing out all Drivers on your system to be able to test them.


Please post back to us what the problem is, memory or drivers. So we can assist you futher. It would be helpfull to know what drivers it are. Most of the time windows reports this.
My System SpecsSystem Spec
12 Oct 2011   #3

win 7 pro x64
 
 

I did the second step from you advice, because i have checked memory before with memtest.

my last mini dump looks like:



Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\101211-14976-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e52670
Debug session time: Wed Oct 12 12:11:00.879 2011 (UTC + 2:00)
System Uptime: 0 days 0:08:35.495
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880049cf13b, fffff880056b14d8, fffff880056b0d30}

Probably caused by : igdkmd64.sys ( igdkmd64+1b313b )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880049cf13b, The address that the exception occurred at
Arg3: fffff880056b14d8, Exception Record Address
Arg4: fffff880056b0d30, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
igdkmd64+1b313b
fffff880`049cf13b ff10 call qword ptr [rax]

EXCEPTION_RECORD: fffff880056b14d8 -- (.exr 0xfffff880056b14d8)
ExceptionAddress: fffff880049cf13b (igdkmd64+0x00000000001b313b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT: fffff880056b0d30 -- (.cxr 0xfffff880056b0d30)
rax=0000000000000000 rbx=0000000000000057 rcx=0000000000000000
rdx=000000000000000d rsi=fffff880056b1770 rdi=fffffa8008dea000
rip=fffff880049cf13b rsp=fffff880056b1710 rbp=fffffa8008380950
r8=000000000000040b r9=fffff880011b48dc r10=fffff880056b19e0
r11=fffff880056b15f0 r12=fffff8a00d804355 r13=0000000000000000
r14=fffffa8008e1cd01 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210282
igdkmd64+0x1b313b:
fffff880`049cf13b ff10 call qword ptr [rax] ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebc100
0000000000000000

FOLLOWUP_IP:
igdkmd64+1b313b
fffff880`049cf13b ff10 call qword ptr [rax]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffffa8008381bf0 to fffff880049cf13b

STACK_TEXT:
fffff880`056b1710 fffffa80`08381bf0 : 00000000`00000000 00000000`000ffdfc fffffa80`083ec000 fffffa80`083ec000 : igdkmd64+0x1b313b
fffff880`056b1718 00000000`00000000 : 00000000`000ffdfc fffffa80`083ec000 fffffa80`083ec000 fffff880`048459ec : 0xfffffa80`08381bf0


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: igdkmd64+1b313b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME: igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e4152eb

STACK_COMMAND: .cxr 0xfffff880056b0d30 ; kb

FAILURE_BUCKET_ID: X64_0x7E_VRF_igdkmd64+1b313b

BUCKET_ID: X64_0x7E_VRF_igdkmd64+1b313b

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880049cf13b, The address that the exception occurred at
Arg3: fffff880056b14d8, Exception Record Address
Arg4: fffff880056b0d30, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
igdkmd64+1b313b
fffff880`049cf13b ff10 call qword ptr [rax]

EXCEPTION_RECORD: fffff880056b14d8 -- (.exr 0xfffff880056b14d8)
ExceptionAddress: fffff880049cf13b (igdkmd64+0x00000000001b313b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT: fffff880056b0d30 -- (.cxr 0xfffff880056b0d30)
rax=0000000000000000 rbx=0000000000000057 rcx=0000000000000000
rdx=000000000000000d rsi=fffff880056b1770 rdi=fffffa8008dea000
rip=fffff880049cf13b rsp=fffff880056b1710 rbp=fffffa8008380950
r8=000000000000040b r9=fffff880011b48dc r10=fffff880056b19e0
r11=fffff880056b15f0 r12=fffff8a00d804355 r13=0000000000000000
r14=fffffa8008e1cd01 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210282
igdkmd64+0x1b313b:
fffff880`049cf13b ff10 call qword ptr [rax] ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: 0000000000000000

FOLLOWUP_IP:
igdkmd64+1b313b
fffff880`049cf13b ff10 call qword ptr [rax]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffffa8008381bf0 to fffff880049cf13b

STACK_TEXT:
fffff880`056b1710 fffffa80`08381bf0 : 00000000`00000000 00000000`000ffdfc fffffa80`083ec000 fffffa80`083ec000 : igdkmd64+0x1b313b
fffff880`056b1718 00000000`00000000 : 00000000`000ffdfc fffffa80`083ec000 fffffa80`083ec000 fffff880`048459ec : 0xfffffa80`08381bf0


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: igdkmd64+1b313b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME: igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e4152eb

STACK_COMMAND: .cxr 0xfffff880056b0d30 ; kb

FAILURE_BUCKET_ID: X64_0x7E_VRF_igdkmd64+1b313b

BUCKET_ID: X64_0x7E_VRF_igdkmd64+1b313b

Followup: MachineOwner
---------
My System SpecsSystem Spec
.


12 Oct 2011   #4

64-bit Windows 8.1 Pro
 
 

It seems that your system is blaming igdkmd64.sys ( Intel Graphics driver ) as a possible reason for your crashes... make sure that you follow Ken's advice, and download and install the latest driver from http://downloadcenter.intel.com/Default.aspx ... you should continue to run driver and upload the latest .dmp files for further analysis.
My System SpecsSystem Spec
12 Oct 2011   #5

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by julek View Post
I did the second step from you advice, because i have checked memory before with memtest.

my last mini dump looks like:



Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\101211-14976-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e52670
Debug session time: Wed Oct 12 12:11:00.879 2011 (UTC + 2:00)
System Uptime: 0 days 0:08:35.495
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880049cf13b, fffff880056b14d8, fffff880056b0d30}

Probably caused by : igdkmd64.sys ( igdkmd64+1b313b )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880049cf13b, The address that the exception occurred at
Arg3: fffff880056b14d8, Exception Record Address
Arg4: fffff880056b0d30, Context Record Address

Debugging Details:
------------------
Code:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
igdkmd64+1b313b
fffff880`049cf13b ff10            call    qword ptr [rax]

EXCEPTION_RECORD:  fffff880056b14d8 -- (.exr 0xfffff880056b14d8)
ExceptionAddress: fffff880049cf13b (igdkmd64+0x00000000001b313b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT:  fffff880056b0d30 -- (.cxr 0xfffff880056b0d30)
rax=0000000000000000 rbx=0000000000000057 rcx=0000000000000000
rdx=000000000000000d rsi=fffff880056b1770 rdi=fffffa8008dea000
rip=fffff880049cf13b rsp=fffff880056b1710 rbp=fffffa8008380950
 r8=000000000000040b  r9=fffff880011b48dc r10=fffff880056b19e0
r11=fffff880056b15f0 r12=fffff8a00d804355 r13=0000000000000000
r14=fffffa8008e1cd01 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210282
igdkmd64+0x1b313b:
fffff880`049cf13b ff10            call    qword ptr [rax] ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebc100
 0000000000000000 

FOLLOWUP_IP: 
igdkmd64+1b313b
fffff880`049cf13b ff10            call    qword ptr [rax]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffffa8008381bf0 to fffff880049cf13b

STACK_TEXT:  
fffff880`056b1710 fffffa80`08381bf0 : 00000000`00000000 00000000`000ffdfc fffffa80`083ec000 fffffa80`083ec000 : igdkmd64+0x1b313b
fffff880`056b1718 00000000`00000000 : 00000000`000ffdfc fffffa80`083ec000 fffffa80`083ec000 fffff880`048459ec : 0xfffffa80`08381bf0


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  igdkmd64+1b313b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e4152eb

STACK_COMMAND:  .cxr 0xfffff880056b0d30 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_VRF_igdkmd64+1b313b

BUCKET_ID:  X64_0x7E_VRF_igdkmd64+1b313b

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880049cf13b, The address that the exception occurred at
Arg3: fffff880056b14d8, Exception Record Address
Arg4: fffff880056b0d30, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
igdkmd64+1b313b
fffff880`049cf13b ff10            call    qword ptr [rax]

EXCEPTION_RECORD:  fffff880056b14d8 -- (.exr 0xfffff880056b14d8)
ExceptionAddress: fffff880049cf13b (igdkmd64+0x00000000001b313b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT:  fffff880056b0d30 -- (.cxr 0xfffff880056b0d30)
rax=0000000000000000 rbx=0000000000000057 rcx=0000000000000000
rdx=000000000000000d rsi=fffff880056b1770 rdi=fffffa8008dea000
rip=fffff880049cf13b rsp=fffff880056b1710 rbp=fffffa8008380950
 r8=000000000000040b  r9=fffff880011b48dc r10=fffff880056b19e0
r11=fffff880056b15f0 r12=fffff8a00d804355 r13=0000000000000000
r14=fffffa8008e1cd01 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210282
igdkmd64+0x1b313b:
fffff880`049cf13b ff10            call    qword ptr [rax] ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS:  0000000000000000 

FOLLOWUP_IP: 
igdkmd64+1b313b
fffff880`049cf13b ff10            call    qword ptr [rax]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffffa8008381bf0 to fffff880049cf13b

STACK_TEXT:  
fffff880`056b1710 fffffa80`08381bf0 : 00000000`00000000 00000000`000ffdfc fffffa80`083ec000 fffffa80`083ec000 : igdkmd64+0x1b313b
fffff880`056b1718 00000000`00000000 : 00000000`000ffdfc fffffa80`083ec000 fffffa80`083ec000 fffff880`048459ec : 0xfffffa80`08381bf0


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  igdkmd64+1b313b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e4152eb

STACK_COMMAND:  .cxr 0xfffff880056b0d30 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_VRF_igdkmd64+1b313b

BUCKET_ID:  X64_0x7E_VRF_igdkmd64+1b313b

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

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier

Quote:
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable
My System SpecsSystem Spec
Reply

 Random BSOD different errors





Thread Tools



Similar help and support threads for2: Random BSOD different errors
Thread Forum
random BSOD errors BSOD Help and Support
random BSOD errors BSOD Help and Support
Random BSOD errors happening at random times BSOD Help and Support
Solved Getting random BSOD errors need help to know why BSOD Help and Support
Solved Random 109 BSOD errors BSOD Help and Support
random BSOD with different errors 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 04:45 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33