Windows 7 BSOD

[Eal2357]

I get the BSOD when copying files to my pendrive or watching a video.

Basic System Specs:
Windows 7 x64 Home Premium (SP1)
Intel Pentium 4 CPU 3.00GHz
Kingstone 1GB
PSU 450W
XFX Geforce 7600GT 256MB DDR3


System is Three year old. i was used windows xp pro then, i installed windows 7 full retail version in january.Thank you in advance for any help you can provide.
View attachment 156162

View attachment 156163

 

[zigzag3143]

I get the BSOD when copying files to my pendrive or watching a video.

Basic System Specs:
Windows 7 x64 Home Premium (SP1)
Intel Pentium 4 CPU 3.00GHz
Kingstone 1GB
PSU 450W
XFX Geforce 7600GT 256MB DDR3


System is Three year old. i was used windows xp pro then, i installed windows 7 full retail version in january.Thank you in advance for any help you can provide.
View attachment 156162

View attachment 156163

Memory corruption caused by an as yet unknown driver

Please run memtest and driver verifier.


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

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.

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).

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.

 

[Eal2357]

I analyse the dump file with whocrashed and here are the results

Crash Dump

Crash dump file:        C:\Windows\Minidump\052211-15859-01.dmp
Date/time:              5/22/2011 4:41:54 PM GMT
Uptime:                 00:24:56
Machine:                
Bug check name:         MEMORY_MANAGEMENT
Bug check code:         0x1A
Bug check parm 1:       0x5003
Bug check parm 2:       0xFFFFF70001080000
Bug check parm 3:       0x23E3
Bug check parm 4:       0x3949000047CE
Probably caused by:     ntoskrnl.exe
Driver description:     NT Kernel & System
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that a severe memory management error occurred.

Comments:
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.

Kernel Stack

nt+0x80640
nt+0xE9F7C
0x0000001A
0x00005003
0xFFFFF70001080000
0x000023E3
0x3949000047CE
0xFFFFF8800482ECA0
0xFFFFFA80026136B0
nt+0x378084
0xFFFFFFFF00000000
0xFFFFFA8000000000
0xFFFFFA80026136B0
0x00000004
0xFFFFF8800482EAF0
0xFFFFF8800482EAB8
0xF300000036899867
0x00000080
0xFFFFFA80026138C8
0xFFFFFA8000000002

 

[Eal2357]

BSOD Problem

I get the BSOD when copying files to my pendrive or watching a video.

Basic System Specs:
Windows 7 x64 Home Premium (SP1)
Intel Pentium 4 CPU 3.00GHz
Kingstone 1GB
PSU 450W
XFX Geforce 7600GT 256MB DDR3


System is Three year old. i was used windows xp pro then, i installed windows 7 full retail version in january.Thank you in advance for any help you can provide.

View attachment 156306

View attachment 156307

I analyse the dump file with whocrashed and here are the results

Crash Dump:

Crash dump file:        C:\Windows\Minidump\052211-15859-01.dmp
Date/time:              5/22/2011 4:41:54 PM GMT
Uptime:                 00:24:56
Machine:                
Bug check name:         MEMORY_MANAGEMENT
Bug check code:         0x1A
Bug check parm 1:       0x5003
Bug check parm 2:       0xFFFFF70001080000
Bug check parm 3:       0x23E3
Bug check parm 4:       0x3949000047CE
Probably caused by:     ntoskrnl.exe
Driver description:     NT Kernel & System
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that a severe memory management error occurred.

Comments:
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.

Kernel Stack:

nt+0x80640
nt+0xE9F7C
0x0000001A
0x00005003
0xFFFFF70001080000
0x000023E3
0x3949000047CE
0xFFFFF8800482ECA0
0xFFFFFA80026136B0
nt+0x378084
0xFFFFFFFF00000000
0xFFFFFA8000000000
0xFFFFFA80026136B0
0x00000004
0xFFFFF8800482EAF0
0xFFFFF8800482EAB8
0xF300000036899867
0x00000080
0xFFFFFA80026138C8
0xFFFFFA8000000002

 

[zigzag3143]

The most recent was caused by memory management probably by an as yet un-named driver. Please run driver verifier to find out which.

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).

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.

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


Loading Dump File [C:\Windows\Minidump\052511-19796-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x8280e000 PsLoadedModuleList = 0x829574d0
Debug session time: Wed May 25 06:49:11.938 2011 (GMT-4)
System Uptime: 0 days 22:05:50.200
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
..................
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PROCESS_HAS_LOCKED_PAGES (76)
Caused by a driver not cleaning up correctly after an I/O.
Arguments:
Arg1: 00000000, Locked memory pages found in process being terminated.
Arg2: 861db030, Process address.
Arg3: 00000001, Humber of locked pages.
Arg4: 00000000, Pointer to driver stacks (if enabled) or 0 if not.
    Issue a !search over all of physical memory for the current process pointer.
    This will yield at least one MDL which points to it.  Then do another !search
    for each MDL found, this will yield the IRP(s) that point to it, revealing
    which driver is leaking the pages.
    Otherwise, set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
    Management\TrackLockedPages to a DWORD 1 value and reboot.  Then the system
    will save stack traces so the guilty driver can be easily identified.
    When you enable this flag, if the driver commits the error again you will
    see a different bugcheck - DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (0xCB) -
    which can identify the offending driver(s).

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


PROCESS_NAME:  audiodg.exe

DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x76

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82a81842 to 828ecf2c

STACK_TEXT:  
99973bbc 82a81842 00000076 00000000 861db030 nt!KeBugCheckEx+0x1e
99973bf0 82a8175a 852f5a50 861db018 00000000 nt!MmDeleteProcessAddressSpace+0x56
99973c24 82a30581 861db030 861db030 861db018 nt!PspProcessDelete+0x15d
99973c3c 82886d60 00000000 1317c7a3 86279000 nt!ObpRemoveObjectRoutine+0x59
99973c50 82886cd0 861db030 828abb1f 00000002 nt!ObfDereferenceObjectWithTag+0x88
99973c58 828abb1f 00000002 99973cc0 82a3b44d nt!ObfDereferenceObject+0xd
99973c64 82a3b44d 00000000 c000009a 82943580 nt!MmFreeAccessPfnBuffer+0x27
99973cc0 82a4f83e 00000000 8787e338 00000000 nt!PfpFlushBuffers+0x2ba
99973d50 82a16f64 82943580 b10f4556 00000000 nt!PfTLoggingWorker+0xaa
99973d90 828bf219 82a4f78e 82943580 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MmDeleteProcessAddressSpace+56
82a81842 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MmDeleteProcessAddressSpace+56

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fd753

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x76_audiodg.exe_nt!MmDeleteProcessAddressSpace+56

BUCKET_ID:  0x76_audiodg.exe_nt!MmDeleteProcessAddressSpace+56

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