Windows 7 Unexpected windows 7 shutdown

Cris Gregory

New Member
May 22, 2013
Hi everyone. Please, my system suffered an unexpected shutdown 3times today. its a hp 630 icore 3 thats just a year old. i have run CHKDSK as well as SFC\ SCAN NOW and no errors popped up anywhere, but yet i still get the same BSOD and its shutsdown. This is the information i get after the system boots up from the unexpected shutdown.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.
Locale ID: 2057

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000050
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF88001947230
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:

here are my system specifications:
Time of this report: 5/22/2013, 16:33:11
Machine name: CRIS-HP
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
Language: English (Regional Setting: English)
System Manufacturer: Hewlett-Packard
System Model: HP 630 Notebook PC
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i3 CPU M 380 @ 2.53GHz (4 CPUs), ~2.5GHz
Memory: 4096MB RAM
Available OS Memory: 3894MB RAM
Page File: 2848MB used, 4937MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

PLEEEEEEEEEEEEEEEEEEEEASE, anm someone help me out in solving this problem. i have added the dump file located in c:\\windows\ minidump so someone can take a look at it and try to find the problem with my laptop. Thank you very much


Last edited:

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.

This bug check is usually caused by drivers that have used improper addresses.

If the first parameter has the same value as the fourth parameter, and the third parameter indicates an execute operation, this bug check was likely caused by a driver that was trying to execute code when the code itself was paged out. Possible causes for the page fault include the following:

  • The function was marked as pageable and was running at an elevated IRQL (which includes obtaining a lock).

  • The function call was made to a function in another driver, and that driver was unloaded.

  • The function was called by using a function pointer that was an invalid pointer.
To begin debugging, use a kernel debugger to get a stack trace.

If the problem is caused by the driver that you are developing, make sure that the function that was executing at the time of the bug check is not marked as pageable or does not call any other inline functions that could be paged out.

If the debug is still not fixed, Reinstall OS.

If you check the dates above Yazan you'll see that post is from 2013 which unfortunately no one bothered to answer.