Random BSOD - windows 7 64bit

Nagesh1112

Reputable
Sep 23, 2015
4
0
4,510
0
Hello all,

One of my user experiencing BSOD randomly on his laptop running windows 7 64bit.
i have updated all the drivers , BIOS. Run for chkdsk, sfc /scannow. Still the issue persist. There was no recent change in terms of software or hardware.

i have minidump for the crash. but i don't find a way to upload here. please help me out to resolve this issue.

here is system configuration and the crash dump analysis by whocrashed tool

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Inspiron 1525 , Dell Inc., 0U990C
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T5800 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4284526592 total

On Thu 24-09-2015 05:30:41 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x21 (0xFFFFFA8006648060, 0x2, 0x800018, 0x7ED2DE)
Error: QUOTA_UNDERFLOW
Bug check description: This indicates that quota charges have been mishandled by returning more quota to a particular block than was previously charged.
A third party driver was identified as the probable root cause of this system error.
Google query: QUOTA_UNDERFLOW



On Sat 12-09-2015 07:52:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091215-72602-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x0, 0xFFFFFA8004BD77C0)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 12-09-2015 07:02:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091215-72368-01.dmp
This was probably caused by the following module: pacer.sys (pacer+0x4625)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88002F39625, 0xFFFFF88008058D00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\pacer.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: QoS Packet Scheduler
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 10-09-2015 13:36:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091115-78608-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x18 (0xFFFFFA80036F7F30, 0xFFFFFA80044E2100, 0x1, 0x800000)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.



On Wed 09-09-2015 10:24:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090915-65364-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x19 (0x3, 0xFFFFFA80044E20D0, 0xFFFFFA80044E20D0, 0x0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.



On Sat 05-09-2015 09:15:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090515-83054-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x32E655)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002D8F655, 0xFFFFF88003324868, 0xFFFFF880033240C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 29-08-2015 14:45:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083115-151258-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xA (0x800048, 0x2, 0x1, 0xFFFFF80002AF367F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
something is corrupting your system memory.

you should run memtest86 and confim you physical machine is ok.
if it is, then boot windows run cmd.exe as an admin
then run
sfc.exe /scannow
and a malwarebytes scan.

if the above does not find any problem then look for a driver that is corrupting shared kernel memory.

make a restore point.
start cmd.exe as an admin then run
verifier.exe /standard /all
reboot your machine, windows will bugcheck if it finds a bad driver and it will name the bad driver in the next memory dump.

Note: you turn of verifier using the command
verifier.exe /reset
(be sure to turn off verifier after you are done testing)

put your actual new memory dump file on a server like microsoft onedrive, mark the files for public access and post a link.
 
data in memory, not necessarily bad physical RAM.
when you see a bugcheck, they often have a error code like 0xFFFFFFFFC0000005
the C0000005 portion of the number is the status code, it means a bad memory location was given to the driver.

IE the contents of the memory location was not what was expected.

then you have to figure out why it is wrong. could be bad RAM, bad BIOS memory timings, bugs in the device driver, bugs in the device driver that is stored in memory next to the driver that failed. IE one driver that over writes another drivers data. You get random bugchecks in this case because windows attempts to load the drivers in different order and locations in memory on each boot to avoid hacking. This means one bad driver can corrupt a different drivers data on each boot of the system. Some drivers don't check for corruption and your system can stay up much longer even though its data is being corrupted. Core windows components expect to be hacked and check for corruption and call a bugcheck to stop the process.






 

TRENDING THREADS