[SOLVED] DELL VOSTRO 1500 Win7 Pro BSOD

stirelli · May 12, 2011

HI,

I've had a dell vostro 1500 for at least 3 years now and a for at least one month the BSOD began. I'm having one or two for week.
3 Months ago, I remove the 2gb original from dell, and install 4gb of mem and then I install Win7 Pro 64.
The thing is that the mems are perfectly compatible with the machine. I run the diagnostic from bios setup and check all fine.
In fact all problems started 2 months after installing the 4gb of mem.

I run the BSOD_Windows7_Vista_v2.64_jcgriff2_, but it kepps waiting for systeminfo for a lont time. Almost an hour. I had to close it, but I have the files from that process and the PERFMON html.

I am running the verifier since one hour now.
Any help would be great.

My System Info:
OS: Microsoft Windows 7 Professional 64
x64
Original OS from Dell: Windows Vista
OS Version: Full Retail
Age of system (hardware): 3 years
Age of OS installation: 4 months since now.
CPU: Intel Mobile Core 2 Duo T7250
Video Card: Mobile Intel 965 Express Chipset Family
Motherboard: 0NX907
System Manufacturer: Dell
Model: Vostro 1500

stirelli · May 13, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Can we move this thread to the Forum : BSOD, App Crashes And Hangs.

Sorry.

joeten · May 13, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Moved, it's no problem

stirelli · May 18, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Bumping the thread.

stirelli · Jun 5, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Bump #2

jcgriff2 · Jun 7, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

stirelli said:
I've had a dell vostro 1500 for at least 3 years now and a for at least one month the BSOD began. I'm having one or two for week.

3 Months ago, I remove the 2gb original from dell, and install 4gb of mem and then I install Win7 Pro 64.

Hi -

There was only 1 dump file from 12 May 2011 and results are inconclusive.

Turn virtual memory back on - set to system managed.

I suggest taking out new 4GB RAM and placing old 2 GB back in to see if the system remains stable. If so, try the 4 GB again.

Also, see if Driver Verifier can help here -

Driver Verifier - Driver Verifier - Windows 7 & Vista (BSOD-related)

Driver Verifier needs to run 24 hours minimum or until it BSODs your system, whichever is less. Then . . .

Provide full system info - Blue Screen of Death (BSOD) Posting Instructions - Windows 7 & Vista

Regards. . .

jcgriff2

`

BSOD SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051211-21356-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu May 12 08:52:12.056 2011 (GMT-4)
System Uptime: 0 days 0:03:02.866
Probably caused by : ntkrnlmp.exe ( nt!CmpFreeKeyControlBlock+123 )
BUGCHECK_STR:  0xc2_7
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc2_7_nt!CmpFreeKeyControlBlock+123
Bugcheck code 000000C2
Arguments 00000000`00000007 00000000`00001097 00000000`00000000 fffff8a0`03ec2010
BiosVersion = A05
BiosReleaseDate = 02/03/2008
SystemManufacturer = Dell Inc.
SystemProductName = Vostro 1500                     
MaxSpeed:     2000
CurrentSpeed: 1995

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  [/font]

stirelli · Jun 10, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Hello jcgriff

ray:

Thanks for your reply.

I will remove the sticks, but in the meantime I recently have one BSOD, with an STOP 0x0000000A and IRQL_NOT_LESS_OR_EQUAL.

I'm having the message "Waiting for Systeminfo" so I don't know how to make the dump file correctly.

I would really like to give you a full dump file but I can't get rid of that message in the process.

I wasn't having any BSOD for at least one and a half month. Yesterday I went to virtual memory managment like you said, and set it to system managed, today I have this BSOD again. Don't know if this has any relation. :4-dontkno

jcgriff2 said:
Hi -

There was only 1 dump file from 12 May 2011 and results are inconclusive.

Turn virtual memory back on - set to system managed.

I suggest taking out new 4GB RAM and placing old 2 GB back in to see if the system remains stable. If so, try the 4 GB again.

Also, see if Driver Verifier can help here -

Driver Verifier - Driver Verifier - Windows 7 & Vista (BSOD-related)

Driver Verifier needs to run 24 hours minimum or until it BSODs your system, whichever is less. Then . . .

Provide full system info - Blue Screen of Death (BSOD) Posting Instructions - Windows 7 & Vista

Regards. . .

jcgriff2

[/code]

stirelli · Jun 10, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Well, so I run driver verifier. Reboot, and I got a windows total freeze in the waiting message on windows startup. Reboot and freeze in exactly the same place. Didn't do any BSOD just frezze. I had to make a system restore.

Here is the minidump. Hope this can help.

jcgriff2 · Jun 10, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Hi -

RAM, video or other unknown hardware failure appears to be the problem.

The systeminfo message from the jcgriff2 BSOD app is related to Windows msinfo32.

Swap the RAM out - see what happens.

Regards. . .

jcgriff2

`

BSOD SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061011-22339-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jun 10 09:33:41.804 2011 (GMT-4)
System Uptime: 0 days 1:30:30.630
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3a2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!SURFACE::bDeleteSurface+3a2
Bugcheck code 0000000A
Arguments fffffa80`1c659010 00000000`00000002 00000000`00000001 fffff800`02b44036
BiosVersion = A05
BiosReleaseDate = 02/03/2008
SystemManufacturer = Dell Inc.
SystemProductName = Vostro 1500                     
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

  [/font]

stirelli · Jul 18, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

So I went back to the original 2gb of RAM, and I already had one BSOD and two total hangs in one day. Don't know if this is good or bad. :4-dontkno

The latest BSOD was an IRQ_NOT_LESS_OR_EQUAL.

I run a MemTest86+ diagnostic and went all fine.

Y run your app again and never ends,it keeps repeating the line "Waiting for SystemInfo". So I close the windows, and zip the unfinished process too.

I have a FUJITSU MHY2120BH HDD Drive, so according to carrona.org I use the SeaGate SeaTools. All tests were ok.

Can this be a driver problem instead of a hardware failure?

I attach the minidump from the BSOD.
The BSOD_Windows7_Vista_v2.64_jcgriff2 process, and the perfmon.

Any help would be very appreciate, I really need to fix this issue, since I use this computer to work.
Thanks.

jcgriff2 said:

Hi -

RAM, video or other unknown hardware failure appears to be the problem.

The systeminfo message from the jcgriff2 BSOD app is related to Windows msinfo32.

Swap the RAM out - see what happens.

Regards. . .

jcgriff2

`

BSOD SUMMARY

Code:

[FONT=lucida console]Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061011-22339-01.dmp][/FONT]
[FONT=lucida console]Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631[/FONT]
[FONT=lucida console]Debug session time: Fri Jun 10 09:33:41.804 2011 (GMT-4)[/FONT]
[FONT=lucida console]System Uptime: 0 days 1:30:30.630[/FONT]
[FONT=lucida console]Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3a2 )[/FONT]
[FONT=lucida console]DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT[/FONT]
[FONT=lucida console]BUGCHECK_STR:  0xA[/FONT]
[FONT=lucida console]PROCESS_NAME:  chrome.exe[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  X64_0xA_win32k!SURFACE::bDeleteSurface+3a2[/FONT]
[FONT=lucida console]Bugcheck code 0000000A[/FONT]
[FONT=lucida console]Arguments fffffa80`1c659010 00000000`00000002 00000000`00000001 fffff800`02b44036[/FONT]
[FONT=lucida console]BiosVersion = A05[/FONT]
[FONT=lucida console]BiosReleaseDate = 02/03/2008[/FONT]
[FONT=lucida console]SystemManufacturer = Dell Inc.[/FONT]
[FONT=lucida console]SystemProductName = Vostro 1500                     [/FONT]
[FONT=lucida console]MaxSpeed:     2000[/FONT]
[FONT=lucida console]CurrentSpeed: 1995[/FONT]
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

stirelli · Jul 18, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Well since I am very confuse about all this BSOD I start reading my own dump files, and I have got this information:

Code:

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c8cc25, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.
FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02c8cc25 498b08 mov rcx,qword ptr [r8]
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec4100
ffffffffffffffff 
ERROR_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: MsMpEng.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ce05d8 to fffff80002c94d00
STACK_TEXT: 
fffff880`0337c098 fffff800`02ce05d8 : 00000000`0000001e ffffffff`c0000005 fffff800`02c8cc25 00000000`00000000 : nt!KeBugCheckEx
fffff880`0337c0a0 fffff800`02c94382 : fffff880`0337c878 00000000`00000000 fffff880`0337c920 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`0337c740 fffff800`02c92c8a : fffff880`0b8f0039 fffff880`0b8ea004 fffff880`0b8b1000 fffff880`0b8c6023 : nt!KiExceptionDispatch+0xc2
fffff880`0337c920 fffff800`02c8cc25 : 00000000`00000000 fffff800`02ca329f 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`0337cab0 fffff800`02ca329f : 00000000`00000000 00000000`00000000 fffff700`01080000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16
fffff880`0337cac0 fffff800`02c92e2e : 00000000`00000001 00000000`0e1b1000 00000000`00000001 00000000`00000000 : nt!MmAccessFault+0x168f
fffff880`0337cc20 000007fe`fb842c0f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0545dd70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fb842c0f

Another one...

Code:

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa8014f39010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002d90036, address which referenced memory
Debugging Details:
------------------
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0b100
 fffffa8014f39010 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!MiReleaseConfirmedPageFileSpace+86
fffff800`02d90036 480fb328        btr     qword ptr [rax],rbp
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  conhost.exe
TRAP_FRAME:  fffff8800805fd90 -- (.trap 0xfffff8800805fd90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004f39010 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d90036 rsp=fffff8800805ff20 rbp=0000000080000000
 r8=fffff8800805ff50  r9=0000000fffffffff r10=fffffa8005f36ec8
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x86:
fffff800`02d90036 480fb328        btr     qword ptr [rax],rbp ds:3001:fffffa80`04f39010=c00211000000007f
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002cdb2a9 to fffff80002cdbd00
STACK_TEXT:  
fffff880`0805fc48 fffff800`02cdb2a9 : 00000000`0000000a fffffa80`14f39010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0805fc50 fffff800`02cd9f20 : 00000000`77296000 00000000`7726b000 00000000`000a4001 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0805fd90 fffff800`02d90036 : 000007fe`fec6c000 00000000`00000000 fffffa80`03558410 000007fe`fec61000 : nt!KiPageFault+0x260
fffff880`0805ff20 fffff800`02c8ba0b : 80000000`00000000 00000000`00000014 00000000`00000003 00000000`0000001c : nt!MiReleaseConfirmedPageFileSpace+0x86
fffff880`0805ffa0 fffff800`02cac9a4 : fffffa80`05f36ec8 00000000`00000001 00000000`00000000 fffffa80`0000001c : nt! ?? ::FNODOBFM::`string'+0x21b4a
fffff880`08060020 fffff800`02cad612 : fffff880`080603a0 fffffa80`05f36b30 fffffa80`05f36b30 00000000`00000001 : nt!MiDeleteAllHashMappings+0xe4
fffff880`08060060 fffff800`02fb120a : fffff8a0`040bfa50 fffff880`080603a0 00000000`00000000 fffffa80`034d0b60 : nt!MmCleanProcessAddressSpace+0xa2
fffff880`080600b0 fffff800`02f9651d : 00000000`00000000 fffff900`c0868501 000007ff`fffde000 fffffa80`067224a0 : nt!PspExitThread+0x56a
fffff880`080601b0 fffff800`02ccf47a : fffff880`08060208 fffff800`02cdaf93 fffffa80`034d0b60 fffff880`080602e0 : nt!PsExitSpecialApc+0x1d
fffff880`080601e0 fffff800`02ccf7c0 : 00000000`020af7c0 fffff880`08060260 fffff800`02f96490 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`08060260 fffff800`02cdb037 : fffffa80`034d0b60 00000000`00000000 00000000`00000020 fffffa80`01dcb610 : nt!KiInitiateUserApc+0x70
fffff880`080603a0 00000000`772a1206 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`020af710 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772a1206

This one is one of the first MiniDump I have attached here. Now it mess up with chrome.

Code:

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa801c659010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002b44036, address which referenced memory
Debugging Details:
------------------
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbf100
 fffffa801c659010 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!MiReleaseConfirmedPageFileSpace+86
fffff800`02b44036 480fb328        btr     qword ptr [rax],rbp
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  chrome.exe
TRAP_FRAME:  fffff880089a00a0 -- (.trap 0xfffff880089a00a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007619010 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b44036 rsp=fffff880089a0230 rbp=00000000a8200001
 r8=fffff880089a0260  r9=fffffa80055b7650 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x86:
fffff800`02b44036 480fb328        btr     qword ptr [rax],rbp ds:fffffa80`07619010=ffffffffffffff97
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002a8f2a9 to fffff80002a8fd00
STACK_TEXT:  
fffff880`0899ff58 fffff800`02a8f2a9 : 00000000`0000000a fffffa80`1c659010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0899ff60 fffff800`02a8df20 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`089a00a0 fffff800`02b44036 : fffffa80`01644180 00000000`00000000 fffffa80`075f1e50 fffffa80`01618a10 : nt!KiPageFault+0x260
fffff880`089a0230 fffff800`02afdcda : 00000000`00000130 fffff680`00025ff8 00000000`04c00000 a8400000`00000001 : nt!MiReleaseConfirmedPageFileSpace+0x86
fffff880`089a02b0 fffff800`02ac35d9 : fffff8a0`00000000 00000000`04e4afff fffffa80`00000000 6e100000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35eb6
fffff880`089a0470 fffff800`02da68b1 : fffffa80`03d398e0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`089a0590 fffff800`02da6cb3 : 00000000`00000000 00000000`04ae0000 fffffa80`00000001 fffff960`000f4800 : nt!MiUnmapViewOfSection+0x1b1
fffff880`089a0650 fffff800`02a8ef93 : fffff900`c1e9e938 00000000`00000000 fffffa80`055b7650 00000000`00000000 : nt!NtUnmapViewOfSection+0x5f
fffff880`089a06a0 fffff800`02a8b530 : fffff960`000f584e 00000000`00000001 00000000`00000000 fffff900`c2130010 : nt!KiSystemServiceCopyEnd+0x13
fffff880`089a0838 fffff960`000f584e : 00000000`00000001 00000000`00000000 fffff900`c2130010 00000000`00000001 : nt!KiServiceLinkage
fffff880`089a0840 fffff960`000fdae5 : 00000000`00000000 00000000`00000001 fffff900`c2130010 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x3a2
fffff880`089a0990 fffff960`000f50b0 : 00000000`00001534 00000000`00000000 fffff900`c20217e0 00000000`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`089a09f0 fffff960`000f47df : 00000000`00000000 00000000`00000001 fffffa80`0565d510 00000000`00000000 : win32k!GdiProcessCallout+0x200
fffff880`089a0a70 fffff800`02d65171 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0565d500 : win32k!W32pProcessCallout+0x6b
fffff880`089a0aa0 fffff800`02d4887c : 00000000`c0000005 00000000`00000001 fffffa80`055b7600 fffffa80`0412db60 : nt!PspExitThread+0x4d1
fffff880`089a0ba0 fffff800`02a8ef93 : fffffa80`055b7650 00000000`c0000005 fffffa80`0565d510 00000000`00000000 : nt!NtTerminateProcess+0x138
fffff880`089a0c20 00000000`76d715da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001fe238 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d715da

This is from my first post. Trying to free up the same allocation twice..

Code:

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: fffff8a003ec2010, Address of the block of pool being deallocated
Debugging Details:
------------------
GetUlongFromAddress: unable to read from fffff80002c72210
GetUlongFromAddress: unable to read from fffff80002c72210
POOL_ADDRESS:  fffff8a003ec2010 
BUGCHECK_STR:  0xc2_7
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80002bfebe9 to fffff80002ad4640
STACK_TEXT:  
fffff880`02feeb68 fffff800`02bfebe9 : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`00000000 : nt!KeBugCheckEx
fffff880`02feeb70 fffff800`02db9873 : fffff800`02cd1f00 fffff8a0`03eaa000 ffffffff`624e4d43 00000000`00000000 : nt!ExDeferredFreePool+0x1201
fffff880`02feec20 fffff800`02db846e : fffff8a0`03ec1380 00000000`bd81c6d8 fffff8a0`01d70010 00000000`00000000 : nt!CmpFreeKeyControlBlock+0x123
fffff880`02feec50 fffff800`02adea21 : fffff800`02c71658 fffffa80`036ddb60 00000000`00000000 fffffa80`036ddb60 : nt!CmpDelayDerefKCBWorker+0x33e
fffff880`02feecb0 fffff800`02d71cce : 00000000`00000000 fffffa80`036ddb60 00000000`00000080 fffffa80`036ca040 : nt!ExpWorkerThread+0x111
fffff880`02feed40 fffff800`02ac5fe6 : fffff880`009e7180 fffffa80`036ddb60 fffff880`009f1f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02feed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

Both BSOD are realted to a wrong memory access.
One of them with the Microsoft Windows Defender system, which I already uninstalled.

I run MemTest86+ twice, and Windows Memory Tool Diagnostic, and Segate Seatools.
I have swap my memory to the originals and all seems to be exactly the same memory access violation.

What can I do to get more information.

Every time I want to enable driver verifier, it freeze at windows startup and don't let me any dump to read.

Any help here please.

ray:

joeten · Jul 18, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Hi first you need to run memtest for at least 7 passes on each stick one at a time then swap the stick to the other slot and run again this helps to test both the sticks and the slots

stirelli · Jul 18, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Hi joeten. :wave:

Should I do that even if I know that I have already remove both sticks and put two differents dimms with exactly the same BSOD?

joeten said:
Hi first you need to run memtest for at least 7 passes on each stick one at a time then swap the stick to the other slot and run again this helps to test both the sticks and the slots

joeten · Jul 18, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Hi depends are you certain the replacements are known good working parts

stirelli · Jul 18, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Yes, when I purchase both sticks of 2gb each, I have been using the originals in another notebook for at least 6 months and never a problem working all day long with Win7, but in this case x86. Now I switched back to those.

I can't be 100% sure, but all seems to be a problem in this notebook.
Maybe bad x64 drivers. I always worked with x86 OS.

If you think I need to make the test I will do it.. but seems very strange.

joeten said:
Hi depends are you certain the replacements are known good working parts

joeten · Jul 18, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Hi then it may need the input from the analyst's they may be able to see if a driver is the issue

stirelli · Jul 19, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

I have made an amazing progress.
Finally I have found which drivers were making windows to hang at startup with driver verified enabled.

rapportke64.sys
rapportei64.sys
rapportpg64.sys

All of them belongs to Trusteer Rapport which is an online banking security software very known around the world.

The funny thing is this program in 104 oportunities, blocked every attempt from accessing to what it seems some very important part of the browser memory, and as a positive action. I'm not quiet sure but I don't think Windows like this very much.

With hope this could be related to my BSOD problems. Lets see.
In any case I will post back in a few days.

jcgriff2 · Jul 19, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Hi -

The 3 drivers you mentioned are all new -

Code:

[font=lucida console]
RapportKE64.sys Wed Jun 22 10:59:59 2011 (4E02036F)
RapportPG64.sys Wed Jun 22 11:00:06 2011 (4E020376)
RapportEI64.sys Wed Jun 22 11:00:18 2011 (4E020382)[/font]

http://sysnative.com/0x1/DriverReference.html#RapportPG64.sys
http://sysnative.com/0x1/DriverReference.html#RapportKE64.sys
http://sysnative.com/0x1/DriverReference.html#RapportEI64.sys

They could be conflicting with older 3rd party drivers, Vista SP2 OS drivers or hardware failure.

I checked Dell Support for driver updates, but see very few. Try the links below the driver listing as well.

Drivers & Downloads

Code:

[font=lucida console]
iaStor.sys      Thu Jun 04 21:53:40 2009 (4A287AA4) - Intel Storage

mcdbus.sys      Tue Feb 24 05:34:07 2009 (49A3CD1F)

igdkmd64.sys    Wed Sep 23 15:22:57 2009 (4ABA7591) - Intel chipset/ video

bcmwl664.sys    Tue Jul 07 20:45:04 2009 (4A53EC10) - Dell Wireless 1395 WLAN Mini-Card

b44amd64.sys    Tue Nov 21 07:23:06 2006 (4562EFAA) - Broadcom 440x 10/100

rixdpx64.sys    Mon Mar 26 06:48:23 2007 (4607A4F7) - Ricoh Memory Card Reader driver
rimmpx64.sys    Sun Mar 18 23:09:34 2007 (45FDFEEE) " "
rimspx64.sys    Tue Feb 27 02:10:37 2007 (45E3D96D) " "

stwrt64.sys     Fri Feb 15 17:37:25 2008 (47B61425) - IDT Audio codec

OEM02Dev.sys    Wed Oct 10 22:29:24 2007 (470D8A84) - Dell
OEM02Vfx.sys    Mon Mar 05 05:55:47 2007 (45EBF733) - Dell

[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\071711-32042-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 17 21:20:35.158 2011 (GMT-4)
System Uptime: 0 days 2:29:37.984
Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  conhost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86
Bugcheck code 0000000A
Arguments fffffa80`14f39010 00000000`00000002 00000000`00000001 fffff800`02d90036
BiosVersion = A06
BiosReleaseDate = 04/21/2008
SystemManufacturer = Dell Inc.
SystemProductName = Vostro 1500                     
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\071711-83054-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 17 12:52:40.226 2011 (GMT-4)
System Uptime: 0 days 2:52:31.037
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!ExpInterlockedPopEntrySListFault16+0
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02c8cc25 00000000`00000000 ffffffff`ffffffff
BiosVersion = A06
BiosReleaseDate = 04/21/2008
SystemManufacturer = Dell Inc.
SystemProductName = Vostro 1500                     
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

by [color=navy]jcgriff2     
             
         J. C. Griffith, Microsoft MVP[/color]   
             
           [url=https://mvp.support.microsoft.com/profile/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   


           [url=www.sysnative.com][color=#000033][u]www.sysnative.com[/u][/color][/url]
             
           [url=www.jcgriff2.com][color=#000055][u]www.jcgriff2.com[/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  [/font]

stirelli · Jul 22, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

I see. So the first BSODs are before Trusteer Soft.

Trusteer support contact me and told me that the issue could be related to Rapport Cerberus, the told me how to disabled it and that they are very interesting in investigate this problem.

I have updated all the drivers to the latest, remove a few I don't use like OEM02Dev.sys and OEM02Vfx.sys from the webcam, and disable those I couldn’t find like Broadcom 440x (very old).

The system now, without Trusteer, is very stable. I have been using Driver Verifier for at least 4hs now and 4hs more yesterday. Using internet, virtualization, movies, sounds, hibernating, and not less a 2hs stress test with AIDA64. Not even one reboot or freeze.

Still, all this tests, including Memtest86+, were made with the 2gb original from Dell. I will see the real thing when reinstall the 4gb I bought.

How long should I use DV(makes my system very slow), and go back to try the 4gb.

Thanks.

jcgriff2 · Jul 22, 2011

Re: DELL VOSTRO 1500 Win7 Pro BSOD

Given that Trusteer informed you of problems, it is the likely culprit.

Turn Driver Verifier off - from admin cmd/DOS screen - verifier /reset

Good Luck to you. Thanks for posting back.

Regards. . .

jcgriff2

`

[SOLVED] DELL VOSTRO 1500 Win7 Pro BSOD

Attachments

Attachments

Attachments

Attachments

Top Contributors this Month

Recommended Communities