I'm getting alot of BSOD errors.

[nexpb]

Hi,
Dump files attached to thread, I wasn't able to upload health check wouldn't let me :s

My specs:

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Yes
- an OEM or full retail version? OEM

- What is the age of system (hardware)? ~ 5 Months
- What is the age of OS installation (have you re-installed the OS?) ~ 5 Months

Thanks NexPB.

 

[JMH]

Hello nexpb,

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

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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/Win7 Startup Repair feature).

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 "Special Pool", "Force Pending I/O Requests" and "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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[nexpb]

Thanks for the post. I already did the memtest and it did 100% without finding any errors now I'm doing the Driver verifier. Wich I wil post the results from later.

edit: where can I find the memory dump?
edit 2: I think I found it added to post

 

[zigzag3143]

Thanks for the post. I already did the memtest and it did 100% without finding any errors now I'm doing the Driver verifier. Wich I wil post the results from later.

edit: where can I find the memory dump?
edit 2: I think I found it added to post

This one also appears to be caused by a memory exception (probably your directX) but since this one isnt driver verified we need to wait for the next one.

 

[JMH]

It is much easier to find patterns, etc, when there are more than one crash.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.

 

[nexpb]

Thanks for the post. I already did the memtest and it did 100% without finding any errors now I'm doing the Driver verifier. Wich I wil post the results from later.

edit: where can I find the memory dump?
edit 2: I think I found it added to post

This one also appears to be caused by a memory exception (probably your directX) but since this one isnt driver verified we need to wait for the next one.

I didn't see DirectX in the list from verified.

 

[nexpb]

Weird I didn't get for 2 days blue screen and today again.

Info:


On Wed 2/8/2012 6:17:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020812-32261-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0x66, 0x68000000EC)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

[zigzag3143]

Weird I didn't get for 2 days blue screen and today again.

Info:


On Wed 2/8/2012 6:17:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020812-32261-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0x66, 0x68000000EC)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Again we need the actual DMP file.

Again memory management

 

[nexpb]

Weird I didn't get for 2 days blue screen and today again.

Info:


On Wed 2/8/2012 6:17:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020812-32261-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0x66, 0x68000000EC)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Again we need the actual DMP file.

Again memory management

I couldn't zip it with winrar it said: Can't be accesed.

 

[zigzag3143]

Weird I didn't get for 2 days blue screen and today again.

Info:


On Wed 2/8/2012 6:17:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020812-32261-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0x66, 0x68000000EC)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Again we need the actual DMP file.

Again memory management

I couldn't zip it with winrar it said: Can't be accesed.

Did you follow the directions exactly? did you save it to somewhere like your desktop?

 

[nexpb]

Again we need the actual DMP file.

Again memory management

I couldn't zip it with winrar it said: Can't be accesed.

Did you follow the directions exactly? did you save it to somewhere like your desktop?

Nvm I zipped them added to this post.

 

[zigzag3143]

I couldn't zip it with winrar it said: Can't be accesed.

Did you follow the directions exactly? did you save it to somewhere like your desktop?

Nvm I zipped them added to this post.

Newest is inconclusive and not driver verified

 

[nexpb]

Did you follow the directions exactly? did you save it to somewhere like your desktop?

Nvm I zipped them added to this post.

Newest is inconclusive and not driver verified

Weird I'm sure I did it last time when u restart your comp does it stay? btw I can't turn my pc anymore on aka its dead I'm on my old one atm.

edit: I can't redo the driver verifier cause my computer isn't responding or somthing, nothing is responding my screen, mouse, keyboard but my pc is ON.

 

[zigzag3143]

Nvm I zipped them added to this post.

Newest is inconclusive and not driver verified

Weird I'm sure I did it last time when u restart your comp does it stay? btw I can't turn my pc anymore on aka its dead I'm on my old one atm.

edit: I can't redo the driver verifier cause my computer isn't responding or somthing, nothing is responding my screen, mouse, keyboard but my pc is ON.

Try rebooting in safe mode (F8)

Try rebooting from the win 7 dvd

 

[nexpb]

Newest is inconclusive and not driver verified

Weird I'm sure I did it last time when u restart your comp does it stay? btw I can't turn my pc anymore on aka its dead I'm on my old one atm.

edit: I can't redo the driver verifier cause my computer isn't responding or somthing, nothing is responding my screen, mouse, keyboard but my pc is ON.

Try rebooting in safe mode (F8)

Try rebooting from the win 7 dvd

I can't even get in there :s my pc is tuned on but my screen is black mouse is off keyboard is off etc

 

[zigzag3143]

Weird I'm sure I did it last time when u restart your comp does it stay? btw I can't turn my pc anymore on aka its dead I'm on my old one atm.

edit: I can't redo the driver verifier cause my computer isn't responding or somthing, nothing is responding my screen, mouse, keyboard but my pc is ON.

Try rebooting in safe mode (F8)

Try rebooting from the win 7 dvd

I can't even get in there :s my pc is tuned on but my screen is black mouse is off keyboard is off etc

If the screen is black and the keyboard doesnt work how do you know it is on?

 

[nexpb]

Try rebooting in safe mode (F8)

Try rebooting from the win 7 dvd

I can't even get in there :s my pc is tuned on but my screen is black mouse is off keyboard is off etc

If the screen is black and the keyboard doesnt work how do you know it is on?

Power light is on ;p
edit: managed to get it on but before I can login it crashes, running memtest again to be sure.
edit2: memtest passed 100%, enabled driver verifier again to be sure its on.

 

[nexpb]

Ok PC did crash while running Driver verifier added dump file to attachments

 

[nexpb]

bump?

 

[writhziden]

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


Loading Dump File [E:\BSODDmpFiles\nexpb\020912-35412-01.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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03213000 PsLoadedModuleList = 0xfffff800`03458670
Debug session time: Thu Feb  9 12:54:00.795 2012 (GMT-7)
System Uptime: 0 days 0:08:45.028
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff6fc50059108, 83b00000b2e4c882, fffff6fc50059129}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkLock+f7 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fc50059108
Arg3: 83b00000b2e4c882
Arg4: fffff6fc50059129

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


BUGCHECK_STR:  0x1a_411

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  javaw.exe

CURRENT_IRQL:  2

TRAP_FRAME:  fffff880029f0f90 -- (.trap 0xfffff880029f0f90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000a rbx=0000000000000000 rcx=0000000000000005
rdx=fffff8a00b221000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800536b53b rsp=fffff880029f1120 rbp=fffff880029f12a0
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff880029f1168 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
dxgkrnl!DxgkLock+0xf7:
fffff880`0536b53b 448b4cc208      mov     r9d,dword ptr [rdx+rax*8+8] ds:fffff8a0`0b221058=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000326c96d to fffff8000328fc40

STACK_TEXT:  
fffff880`029f0c38 fffff800`0326c96d : 00000000`0000001a 00000000`00000411 fffff6fc`50059108 83b00000`b2e4c882 : nt!KeBugCheckEx
fffff880`029f0c40 fffff800`032c1001 : 83b00000`b2e4c882 fffff6fc`50059108 0000007f`fffffff8 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x6061
fffff880`029f0c90 fffff800`032ad7ef : 00000000`00000000 fffff800`034c5500 00000000`00000000 fffff800`034c55c0 : nt!MiResolveTransitionFault+0x381
fffff880`029f0d20 fffff800`0329d9db : 00000000`00000056 fffff880`00000040 83b00000`b2e4c882 00000000`00000002 : nt!MiDispatchFault+0x95f
fffff880`029f0e30 fffff800`0328dd6e : 00000000`00000000 fffff8a0`0b221058 fffff8a0`0a8f9600 fffff8a0`0a8f9660 : nt!MmAccessFault+0xe1b
fffff880`029f0f90 fffff880`0536b53b : fffff880`0536b444 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`029f1120 fffff960`001bf6f2 : 00000000`491ccfe0 ffffffff`00000200 00000000`000007db 00000000`7ef92000 : dxgkrnl!DxgkLock+0xf7
fffff880`029f11f0 fffff800`0328eed3 : fffffa80`0696bb60 00000000`000002b8 fffff880`029f11f8 fffffa80`07fb5550 : win32k!NtGdiDdDDILock+0x12
fffff880`029f1220 00000000`732a156a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`491ccfb8 fffff800`03287210 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x732a156a
fffff880`029f1600 fffff880`029f1db0 : fffff880`029f1600 fffffa80`0696bb60 00000000`00000000 00000000`00000000 : nt!KiCallUserMode
fffff880`029f1608 fffff880`029f1600 : fffffa80`0696bb60 00000000`00000000 00000000`00000000 fffff880`029f1db0 : 0xfffff880`029f1db0
fffff880`029f1610 fffffa80`0696bb60 : 00000000`00000000 00000000`00000000 fffff880`029f1db0 00000000`00000000 : 0xfffff880`029f1600
fffff880`029f1618 00000000`00000000 : 00000000`00000000 fffff880`029f1db0 00000000`00000000 00000000`00000000 : 0xfffffa80`0696bb60


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DxgkLock+f7
fffff880`0536b53b 448b4cc208      mov     r9d,dword ptr [rdx+rax*8+8]

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  dxgkrnl!DxgkLock+f7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa

FAILURE_BUCKET_ID:  X64_0x1a_411_dxgkrnl!DxgkLock+f7

BUCKET_ID:  X64_0x1a_411_dxgkrnl!DxgkLock+f7

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

Caused by DirectX, your graphics card, or your graphics card driver. Other possible causes are memory or drivers.



Still no crashes due to verifier...

Run your memory tests again. Sometimes errors do not show up the first few runs (7 passes each), but show up on a subsequent run. If memory is failing, it can be finicky and work fine some of the time but not all the time, which is why it is good to run the tests multiple times.



Disable Verifier. Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts

Alternatively:

1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts

Enable Verifier on all non-Microsoft drivers as before.